Never gunna give you up b1!

in #eos6 years ago (edited)



Blockchain is a very interesting technology, everything you do on the blockchain leaves a permanent trace.  I have been investigating accounts related to the b1 account and found out some very interesting things.

The information here will show snippets of output from cleos, but you can follow along using a block explorer of your choice.

The b1 account

There is a special account on EOS which has only 2 letters, it is owned by the key that block one registered on the Ethereum network.  The key which is set to both owner and active for the b1 account is as follows:

EOS5cujNHGMYZZ2tgByyNEUaoPLFhZVmGXbZc9BLJeQkKZFqGYEiQ

This can be verified with a block explorer by searching for the b1 account.

Other accounts using that key as a permission

./cleos.sh get accounts EOS5cujNHGMYZZ2tgByyNEUaoPLFhZVmGXbZc9BLJeQkKZFqGYEiQ

{

  "account_names": [

    "b1",

    "rickrolledb1"

  ]

}

Thats interesting... The key holder of the b1 account is also the holder of rickrolledb1

Lets see which keys control that account.

./cleos.sh get account rickrolledb1

permissions: 

     owner     1:    1 EOS6ka7tgmPJGEAPnNsxxeSNQUwqLMu44gZhnHY8RtXwPPKGFadak

        active     1:    1 EOS5cujNHGMYZZ2tgByyNEUaoPLFhZVmGXbZc9BLJeQkKZFqGYEiQ

The key ending EiQ is the b1 key, but the owner key is:

EOS6ka7tgmPJGEAPnNsxxeSNQUwqLMu44gZhnHY8RtXwPPKGFadak

This is new, lets see which accounts it controls

./cleos.sh get accounts EOS6ka7tgmPJGEAPnNsxxeSNQUwqLMu44gZhnHY8RtXwPPKGFadak

{

  "account_names": [

    "eosinsiderio",

    "rickrolledb1",

    "yostealmyeos"

  ]

}

There are 2 new accounts here, all related to the original b1 account in some way

eosinsiderio

Very interesting site (http://eosinsider.io), claiming to provide inside information about EOS.

The DNS for this is covered by privacy protection so I will leave it there for now.

**eosinsiderio** has another key which has other interesting accounts, I will not delve deeply into them though

./cleos.sh get accounts EOS4zGGN7cE2a6rXTKdDVSacdSjVZsUjWK8yoeWU5SHTSQbfXrWPs

{

  "account_names": [

    "eosinsiderio",

    "eosinstacart",

    "eosresilient",

    "ha4tamrthage",

    "jollymonster",

    "tokenbalance"

  ]

}

yostealmyeos

Seems like an interesting account, probably a test for timelocks and/or account recovery.  My prediction is that at some point the active key will be circulated publically, Dan (or someone close to B1) are preparing to leave their wallet on the table ;)

This was previously announced here

https://steemit.com/eos/@eosinsider/steal-my-eos-an-experiment-on-the-eos-io-mainnet

Their private key has been published and people are invited to steal the tokens.

What I think happened here

The eosinsider account has created the rickrolled account and then assigned b1 as the active key, will block one engage with this account?

Sort:  

Somebody created an account using b1 public key as active on new account. This somebody could be anyone.

Update:
./cleos.sh get account rickrolledb1

permissions:

 owner     1:    1 EOS5cujNHGMYZZ2tgByyNEUaoPLFhZVmGXbZc9BLJeQkKZFqGYEiQ

    active     1:    1 EOS5cujNHGMYZZ2tgByyNEUaoPLFhZVmGXbZc9BLJeQkKZFqGYEiQ

Now b1 has complete control of this rickroll account if they want to assign it to someone else!

Congratulations @m-i-k-e! You have completed the following achievement on Steemit and have been rewarded with new badge(s) :

Award for the total payout received

Click on the badge to view your Board of Honor.
If you no longer want to receive notifications, reply to this comment with the word STOP

Do not miss the last post from @steemitboard:
SteemitBoard World Cup Contest - Home stretch to the finals. Do not miss them!


Participate in the SteemitBoard World Cup Contest!
Collect World Cup badges and win free SBD
Support the Gold Sponsors of the contest: @good-karma and @lukestokes


Do you like SteemitBoard's project? Then Vote for its witness and get one more award!