Skip to content
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

feat(QUI-115): UTXO support in SDK #62

Merged
merged 11 commits into from
Nov 30, 2024

Conversation

L8D
Copy link
Collaborator

@L8D L8D commented Nov 29, 2024

fix(cert): use serde_as to encode u64 as string in JSON

feat(cert): compute certificate hash without postcard

style(types): remove dead code

fix(tx): stop using serde tag+content fields

This is happening because postcard does not play friendly when serde
types have been decorated with the tag+content fields. When these fields
are present, postcard starts refusing to decode.

fix: use transaction hash hex when reporting transaction errors

fix: gracefully handle block proposal with block height = 0

fix(faucet): generate initial faucet output when server starts

feat(rpc): add send_raw_transaction for submitting encoded transactions

fix(tx): improve error messages and debuggability

feat(sdk): support UTXO-based interactions with SDK

feat(nft-minting-example): update example project with new SDK

Copy link
Collaborator Author

L8D commented Nov 29, 2024

This stack of pull requests is managed by Graphite. Learn more about stacking.

@L8D L8D changed the title fix(cert): use serde_as to encode u64 as string in JSON feat(QUI-115): UTXO support in SDK Nov 29, 2024
@L8D L8D requested a review from c-gamble November 29, 2024 22:06
@L8D L8D marked this pull request as ready for review November 29, 2024 22:07
@c-gamble c-gamble merged commit d47c9f2 into main Nov 30, 2024
3 checks passed
@c-gamble c-gamble deleted the tenorbiel/qui-115-utxo-support-in-sdk branch November 30, 2024 17:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants