Skip to content

Comments

multi: post client account id with bonds.#8

Closed
dnldd wants to merge 1 commit intobisoncraft:masterfrom
dnldd:client_account_id
Closed

multi: post client account id with bonds.#8
dnldd wants to merge 1 commit intobisoncraft:masterfrom
dnldd:client_account_id

Conversation

@dnldd
Copy link
Contributor

@dnldd dnldd commented Feb 11, 2026

This updates the bonds posting process to provide the account id of the client since the provided bonds will be validated against the client's provided identity.

This updates the bonds posting process to provide the account id of the client since the provided bonds will be validated against the
client's provided identity.
@dnldd dnldd force-pushed the client_account_id branch from b3c3061 to 09f6721 Compare February 11, 2026 00:07
Copy link
Contributor

@martonp martonp left a comment

Choose a reason for hiding this comment

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

Shouldn't the accountID just be the libp2p node ID?

@dnldd
Copy link
Contributor Author

dnldd commented Feb 12, 2026

Shouldn't the accountID just be the libp2p node ID?

It can be but that would be relying on the libp2p's standard which could change instead of enforcing our own. This BLAKE256 hash of the public key is what dcrdex uses for bonds currently. Makes sense to continue with it.

@martonp
Copy link
Contributor

martonp commented Feb 12, 2026

You don't need to send the hash to the tatanka node. The tatanka node can call stream.Conn().RemotePublicKey(), and then hash the public key on its own.

@dnldd
Copy link
Contributor Author

dnldd commented Feb 12, 2026

noted, will make the adjustments.

@dnldd
Copy link
Contributor Author

dnldd commented Feb 12, 2026

Closing this. will make the suggested change on the bond verifier PR instead.

@dnldd dnldd closed this Feb 12, 2026
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