You are viewing a single comment's thread from:

RE: Posting Authority Revoked.

in LeoFinance2 years ago

Of course this ignores the initial cost of creating a million accounts and then setting posting authority a trillion times. However, assuming such a thing is possible once an annoyance like that is up and running the attack becomes relatively free.

I think you ignored the bit that would cost a huge fortune, take a long time and be obvious if tried.

But I do agree: I would like to know which delegated account signed something I've also got hung up on trying to figure out which automated system did something for me. I'd love a front end or a block explorer to make it easy to see this, as far as I know it isn't done by any of them?

@mahdiyari @ausbitbank

Sort:  

@mahdiyari commented:

You can get the public key from the signature

Which is exactly the answer I was looking for.
Although an example of this would be quite nice.
Seeing as public keys are sortable a binary search would be O(log n).

Funny how being aggressively wrong always seems to yield the quickest results.

I always find it interesting when I pose these non-existent problems.
Always something to learn.

In case you miss it there's same example code available:

https://github.com/mahdiyari/hive-tx-js

const signature = hiveTx.Signature.from(string)
signature.getPublicKey(message)

const publicKey = signature.getPublicKey(digest).toString()
// STM8WWUYHMdHLgEHidYCztswzfZCViA16EqGkAxt7RG4dWwDpFtCF
// To find which account has this public key
const account = await hiveTx.call('condenser_api.get_key_references', 
        [["STM8WWUYHMdHLgEHidYCztswzfZCViA16EqGkAxt7RG4dWwDpFtCF"]])

Of course this is very black-box and doesn't show how we can actually extract the pubkey from the signature but whatever I assume it works on a practical level.

What is ur discord? Need to put u with our dev and figure out root cause