Skip to content

Conversation

@emmanueldenloye
Copy link
Contributor

No description provided.

-- ^ 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.

3 participants