-
Notifications
You must be signed in to change notification settings - Fork 15
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
[various] Payload updates, cleanup TODOs, coverage, documentation #45
Conversation
To be able to have multiple types of signers for items, we need a TransactionSigner, to keep track of both the address, and the underlying crypto signer needed. It's most basic implementation is the Account
Additionally, fix the fungible asset client
Additionally fix some fungible asset calls
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I bet we can improve handling of fungible_asset.json
otherwise good
const testEd25519PublicKey = "0xde19e5d1880cac87d57484ce9ed2e84cf0f9599f12e7cc3a52e4e7657a763f2c" | ||
const testEd25519Address = "0x978c213990c4833df71548df7ce49d54c759d6b6d932de22b24d56060b7af2aa" | ||
|
||
// These come from fungible_asset.json |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
embed the json into the binary so that it can be read and parsed?
https://pkg.go.dev/embed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This ideally would be built on a case by case basis, embedding in the binary could be interesting, but also less realistic.
Description
Test Plan
Related Links