-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JS client to send transactions to the sequencer #7
Milestone
Comments
szynwelski
added a commit
that referenced
this issue
May 19, 2023
Decision:
|
szynwelski
added a commit
that referenced
this issue
Jun 29, 2023
szynwelski
added a commit
that referenced
this issue
Jul 6, 2023
szynwelski
added a commit
that referenced
this issue
Jul 6, 2023
Centralized and decentralized sequencer client: warp-contracts/warp#472 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The client should allow the creation of a Cosmos transaction containing a given signed Arweave transaction. The signature of the Cosmos transaction should be equal to the signature of the Arweave transaction (see #8).
After creating a transaction, the client should send it to the sequencer network.
Client should be as light as possible because it will eventually be included in Warp Contracts SDK.
To be decided:
The text was updated successfully, but these errors were encountered: