I noticed something funky looking through my proxy lukeeosproxy account's history:

I certainly didn't delegate that bandwidth. That account doesn't even have that EOS to delegate in the first place.

I noticed similar entries it in my eos-voter wallet:

I was chatting with Hive account@greymass a bit and at first we thought it might be a bug.

At first glance, it looks like the action_trace shows an incorrect receiver value.

{
      "global_action_seq": 88004774,
      "account_action_seq": 59,
      "block_num": 7628456,
      "block_time": "2018-07-25T02:34:37.500",
      "action_trace": {
        "receipt": {
          "receiver": "lukeeosproxy",
          "act_digest": "c709154df23d67f1d21c60b416b4884870d4250bf75e9cfbef7b6baac8e80591",
          "global_sequence": 88004774,
          "recv_sequence": 31,
          "auth_sequence": [[
              "ha2tmobxgyge",
              36
            ]
          ],
          "code_sequence": 7,
          "abi_sequence": 8
        },
        "act": {
          "account": "eosio",
          "name": "delegatebw",
          "authorization": [{
              "actor": "ha2tmobxgyge",
              "permission": "active"
            }
          ],
          "data": {
            "from": "ha2tmobxgyge",
            "receiver": "ha2tmobxgyge",
            "stake_net_quantity": "0.0000 EOS",
            "stake_cpu_quantity": "20.0000 EOS",
            "transfer": 0
          },
          "hex_data": "a09867fd50998569a09867fd50998569000000000000000004454f5300000000400d03000000000004454f530000000000"
        },
        "elapsed": 21,
        "cpu_usage": 0,
        "console": "",
        "total_cpu_usage": 0,
        "trx_id": "5f90bcdc38bcb86be0b26be29468ca67313c9e2a438fb9119a1688df2393ffa5",
        "inline_traces": []
      }
    }

I thought this might be a bug, but then I noticed the account in question had proxied their vote to my EOS proxy account lukeeosproxy.

Now that makes sense because when an account which votes via a proxy changes their staked EOS amounts, that action will also impact the weight of the vote for their proxy. Instead of this being a bug with EOS, I think it may be a bug with how bloks.io and the voting tool are displaying this action when proxy accounts are involved. I checked eosflare.io, eospark.com, and myeoskit.com which seem to be fine, though the messages are a little confusing seeing someone else's bandwidth changes in my account history.

Instead of saying my account staked or unstaked an amount the account itself didn't have, the explorers should probably say something like:

"Your vote weight decreased because user X undelegated Y EOS from their account."

or

"Your vote weight increased because user X delegated Y EOS to their account."

Thanks to Hive account@anyx and Hive account@jesta for talking this through with me.

If you still haven't voted for an EOS block producer, please do so. If you're not sure who to vote for, set me as your proxy via lukeeosproxy. Otherwise, give out some votes for some solid technical block producers adding value to the ecosystem like eosdacserver and teamgreymass.

If you're wondering where to find out about different block explorers and tools you can use for EOS, check out this site which I found very useful:

http://allthingseos.com/

You can find, well, all things EOS related there. :)

---

Luke Stokes is a father, husband, programmer, STEEM witness, DAC launcher, and voluntaryist who wants to help create a world we all want to live in. Learn about cryptocurrency at UnderstandingBlockchainFreedom.com

_{I'm a Witness! Please vote for @lukestokes.mhth}