You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We don't currently have one of these. The TxService.SubmitTransaction endpoint accepts a Transaction type which is structured and does not contain binary data (aside from the signature):
AccountIdsender=4; // tx originator, should match signer inside Signature
GasOfferedgas_offered=5; // gas price and max gas offered
Amountamount=6; // amount of coin transfered in this tx by sender
uint64counter=7; // tx counter aka nonce
Signaturesignature=8; // sender signature on transaction
}
Per spacemeshos/SMIPS#23 it looks like we need an endpoint to receive signed, binary tx data. Note that the existing, old API does contain an endpoint that does this (SubmitTransaction).
I think that this is just an oversight on our part that we should correct. TxService.SubmitTransaction() should accept a byte[] and clients are expected to pass an XDR encoded transaction which includes the signature. Clients need to generate this blob based on the transactions syntax spec - similar to how Smapp and CLIwallet do this today.
We will need to update all transactions related api methods to support the new sm tx format - this is part of the reason I'm pushing for a spec via the smip asap.
We don't currently have one of these. The
TxService.SubmitTransaction
endpoint accepts aTransaction
type which is structured and does not contain binary data (aside from the signature):api/proto/spacemesh/v1/types.proto
Lines 105 to 116 in 279f08c
Per spacemeshos/SMIPS#23 it looks like we need an endpoint to receive signed, binary tx data. Note that the existing, old API does contain an endpoint that does this (
SubmitTransaction
).CC @avive
The text was updated successfully, but these errors were encountered: