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

Populate receive modal for accts with keyset-refs #648

Open
wants to merge 4 commits into
base: develop
Choose a base branch
from

Conversation

emmanueldenloye
Copy link
Contributor

No description provided.

@@ -24,6 +24,7 @@ data TxBuilder = TxBuilder
-- ^ Presence or absence of a keyset may be used to determine transfer vs
-- transfer-create. If the keyset is present and the account already exists
-- you could choose to do either a transfer or a transfer-create.
, _txBuilder_keysetRef :: Maybe KeySetName
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The TxBuilder type is very sensitive because it defines the serialization format that is used both by Chainweaver and by other parts of the ecosystem. We don't want keyset refs to be visible at this level, both for backwards compatibility reasons and because the low level details of keyset refs should be hidden from users of the TxBuilder. So I think we should back out the changes to this data type and make sure that Chainweaver resolves the keyset elsewhere, preserving the keyset interface.

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