RE: Posting Authority Revoked.

[mahdiyari]

You can't daisy chain the authorities. The authority is just like a public key attached to the account.
You can get the public key from the signature and see which public key or who signed the transaction. That's the role of signature.
If you have any example transaction I can tell which one of your auths broadcasted that transaction.

Edit: It seems authorities do daisy chain to some degree.

Comments

[fulltimegeek]

If you have any example transaction I can tell which one of your auths broadcasted that transaction.

Do you have any sample code for this?

[mahdiyari]

See https://github.com/mahdiyari/hive-tx-js
I added an example there

Block explorers can easily display the public key used for signing the transaction. hivehub.dev might be interested in adding that feature. @asgarth

CC @edicted @brianoflondon

[asgarth]

I thought about this a few times in the past. Thanks for sharing the code, will try to include it in an upcoming release 👍

[andablackwidow]

I'd advise to implement it in such a way that sig_digest of a transaction is taken from server (since a node already has packed version of transaction - this way you don't need to deal with differences between legacy and hf26 version of binary serialization), but the extraction of public key from signature happens on client side, preferably on demand only (that part of the process carries almost all the cost, if you do it on the server you just invite DoS attack).

[edicted]

You can get the public key from the signature.

Ah you see this is the unforeseen technicality that escaped me.
Thanks for playing along and setting the record straight.
I was thinking the signature was much more random than that.
Kinda how the block number is hidden in hex code on the first... eight digits of the block ID?
LoL I forget. 🤓