Ecoer Logo
VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS73.26%
Net Worth
5.087USD
STEEM
0.140STEEM
SBD
0.002SBD
Own SP
93.688SP

Detailed Balance

STEEM
balance
0.140STEEM
market_balance
0.000STEEM
savings_balance
0.000STEEM
reward_steem_balance
0.000STEEM
STEEM POWER
Own SP
93.688SP
Delegated Out
0.000SP
Delegation In
0.000SP
Effective Power
93.688SP
Reward SP (pending)
0.005SP
SBD
sbd_balance
0.002SBD
sbd_conversions
0.000SBD
sbd_market_balance
0.000SBD
savings_sbd_balance
0.000SBD
reward_sbd_balance
0.000SBD
{
  "balance": "0.140 STEEM",
  "savings_balance": "0.000 STEEM",
  "reward_steem_balance": "0.000 STEEM",
  "vesting_shares": "152566.778313 VESTS",
  "delegated_vesting_shares": "0.000000 VESTS",
  "received_vesting_shares": "0.000000 VESTS",
  "sbd_balance": "0.002 SBD",
  "savings_sbd_balance": "0.000 SBD",
  "reward_sbd_balance": "0.000 SBD",
  "conversions": []
}

Account Info

namegreymass
id26439
rank18,334
reputation9338685957189
created2016-07-17T18:58:12
recovery_accountsteem
proxyjesta
post_count36
comment_count0
lifetime_vote_count0
witnesses_voted_for0
last_post2020-03-13T18:49:09
last_root_post2019-08-16T19:09:24
last_vote_time2021-12-15T09:35:24
proxied_vsf_votes0, 0, 0, 0
can_vote1
voting_power9,799
delayed_votes0
balance0.140 STEEM
savings_balance0.000 STEEM
sbd_balance0.002 SBD
savings_sbd_balance0.000 SBD
vesting_shares152566.778313 VESTS
delegated_vesting_shares0.000000 VESTS
received_vesting_shares0.000000 VESTS
reward_vesting_balance9.673970 VESTS
vesting_balance0.000 STEEM
vesting_withdraw_rate0.000000 VESTS
next_vesting_withdrawal1969-12-31T23:59:59
withdrawn6773342147485
to_withdraw6773342147485
withdraw_routes0
savings_withdraw_requests0
last_account_recovery1970-01-01T00:00:00
reset_accountnull
last_owner_update1970-01-01T00:00:00
last_account_update2019-04-24T19:59:33
minedNo
sbd_seconds0
sbd_last_interest_payment2018-11-18T22:59:27
savings_sbd_last_interest_payment1970-01-01T00:00:00
{
  "active": {
    "account_auths": [],
    "key_auths": [
      [
        "STM4yHvuvqGCtU8BuYcambbE7A6B9TF8FNyS4cx5Q1U6gsv4cT3FW",
        1
      ]
    ],
    "weight_threshold": 1
  },
  "balance": "0.140 STEEM",
  "can_vote": true,
  "comment_count": 0,
  "created": "2016-07-17T18:58:12",
  "curation_rewards": 158386,
  "delegated_vesting_shares": "0.000000 VESTS",
  "downvote_manabar": {
    "current_mana": "38141694578",
    "last_update_time": 1639560924
  },
  "guest_bloggers": [],
  "id": 26439,
  "json_metadata": "{\"profile\":{\"website\":\"https://greymass.com\",\"profile_image\":\"https://pbs.twimg.com/profile_images/1121141392082964481/ccAzq3U1_400x400.png\"}}",
  "last_account_recovery": "1970-01-01T00:00:00",
  "last_account_update": "2019-04-24T19:59:33",
  "last_owner_update": "1970-01-01T00:00:00",
  "last_post": "2020-03-13T18:49:09",
  "last_root_post": "2019-08-16T19:09:24",
  "last_vote_time": "2021-12-15T09:35:24",
  "lifetime_vote_count": 0,
  "market_history": [],
  "memo_key": "STM6QcW4PukkhLmx3cTbppKf6Wnj7TbEAaWpGjwnGH5CRKfoWtLGd",
  "mined": false,
  "name": "greymass",
  "next_vesting_withdrawal": "1969-12-31T23:59:59",
  "other_history": [],
  "owner": {
    "account_auths": [],
    "key_auths": [
      [
        "STM5KfPR7QEF3AzWzKiqRpdZTuKxgsKHKRVbzsPSUB1nHxpukzCgD",
        1
      ]
    ],
    "weight_threshold": 1
  },
  "pending_claimed_accounts": 0,
  "post_bandwidth": 19964,
  "post_count": 36,
  "post_history": [],
  "posting": {
    "account_auths": [
      [
        "jesta",
        1
      ],
      [
        "paxmagnus",
        1
      ],
      [
        "streemian",
        1
      ]
    ],
    "key_auths": [
      [
        "STM6WGBtymZsu91xi2CBbCkSbF4ezHm47ELuP7fzFnGt4RAnjfRQE",
        1
      ],
      [
        "STM6edhNDj8W1XxRQUpLF8oq1fraJvg9X3zeGpw32drjEKKTACcoP",
        1
      ],
      [
        "STM6jcsejMKmH4DVBYeRgAjbRDwzKt8Bz8MXYVWnWn2kmeVxk3EPL",
        1
      ]
    ],
    "weight_threshold": 1
  },
  "posting_json_metadata": "{\"profile\":{\"website\":\"https://greymass.com\",\"profile_image\":\"https://pbs.twimg.com/profile_images/1121141392082964481/ccAzq3U1_400x400.png\"}}",
  "posting_rewards": 3326242,
  "proxied_vsf_votes": [
    0,
    0,
    0,
    0
  ],
  "proxy": "jesta",
  "received_vesting_shares": "0.000000 VESTS",
  "recovery_account": "steem",
  "reputation": "9338685957189",
  "reset_account": "null",
  "reward_sbd_balance": "0.000 SBD",
  "reward_steem_balance": "0.000 STEEM",
  "reward_vesting_balance": "9.673970 VESTS",
  "reward_vesting_steem": "0.005 STEEM",
  "savings_balance": "0.000 STEEM",
  "savings_sbd_balance": "0.000 SBD",
  "savings_sbd_last_interest_payment": "1970-01-01T00:00:00",
  "savings_sbd_seconds": "0",
  "savings_sbd_seconds_last_update": "1970-01-01T00:00:00",
  "savings_withdraw_requests": 0,
  "sbd_balance": "0.002 SBD",
  "sbd_last_interest_payment": "2018-11-18T22:59:27",
  "sbd_seconds": "0",
  "sbd_seconds_last_update": "2018-11-18T22:59:27",
  "tags_usage": [],
  "to_withdraw": "6773342147485",
  "transfer_history": [],
  "vesting_balance": "0.000 STEEM",
  "vesting_shares": "152566.778313 VESTS",
  "vesting_withdraw_rate": "0.000000 VESTS",
  "vote_history": [],
  "voting_manabar": {
    "current_mana": "149515442746",
    "last_update_time": 1639560924
  },
  "voting_power": 9799,
  "withdraw_routes": 0,
  "withdrawn": "6773342147485",
  "witness_votes": [],
  "witnesses_voted_for": 0,
  "rank": 18334
}

Withdraw Routes

IncomingOutgoing
Empty
Empty
{
  "incoming": [],
  "outgoing": []
}
From Date
To Date
greymassreceived 0.001 SP curation reward for @streemian / og-streemian---to-be-back
2021/12/22 09:31:48
comment authorstreemian
comment permlinkog-streemian---to-be-back
curatorgreymass
reward1.841657 VESTS
Transaction InfoBlock #60063111/Virtual Operation #539
View Raw JSON Data
{
  "block": 60063111,
  "op": [
    "curation_reward",
    {
      "comment_author": "streemian",
      "comment_permlink": "og-streemian---to-be-back",
      "curator": "greymass",
      "reward": "1.841657 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2021-12-22T09:31:48",
  "trx_id": "0000000000000000000000000000000000000000",
  "trx_in_block": 4294967295,
  "virtual_op": 539
}
2021/12/15 09:35:24
authorstreemian
permlinkog-streemian---to-be-back
votergreymass
weight10000 (100.00%)
Transaction InfoBlock #59864110/Trx 50d4c6e3a88be5ccb3f0c15e36263fbe3e3386bf
View Raw JSON Data
{
  "block": 59864110,
  "op": [
    "vote",
    {
      "author": "streemian",
      "permlink": "og-streemian---to-be-back",
      "voter": "greymass",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2021-12-15T09:35:24",
  "trx_id": "50d4c6e3a88be5ccb3f0c15e36263fbe3e3386bf",
  "trx_in_block": 9,
  "virtual_op": 0
}
2021/08/24 08:29:54
authorgreymass
permlinkintroducing-light-history-nodes-for-eos
votergiovannicic
weight0 (0.00%)
Transaction InfoBlock #56639406/Trx 0f190e2aad43e33ef2dbe0096cec31014a63fcd2
View Raw JSON Data
{
  "block": 56639406,
  "op": [
    "vote",
    {
      "author": "greymass",
      "permlink": "introducing-light-history-nodes-for-eos",
      "voter": "giovannicic",
      "weight": 0
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2021-08-24T08:29:54",
  "trx_id": "0f190e2aad43e33ef2dbe0096cec31014a63fcd2",
  "trx_in_block": 0,
  "virtual_op": 0
}
2021/08/24 08:06:18
authorgreymass
permlinkintroducing-light-history-nodes-for-eos
votergiovannicic
weight0 (0.00%)
Transaction InfoBlock #56638937/Trx 25efa1887b80a57973dc030591a9c7970ff55417
View Raw JSON Data
{
  "block": 56638937,
  "op": [
    "vote",
    {
      "author": "greymass",
      "permlink": "introducing-light-history-nodes-for-eos",
      "voter": "giovannicic",
      "weight": 0
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2021-08-24T08:06:18",
  "trx_id": "25efa1887b80a57973dc030591a9c7970ff55417",
  "trx_in_block": 5,
  "virtual_op": 0
}
greymassreceived 0.002 SP curation reward for @anyx / it-s-time-to-decentralize
2020/03/25 20:50:12
comment authoranyx
comment permlinkit-s-time-to-decentralize
curatorgreymass
reward3.915951 VESTS
Transaction InfoBlock #41968558/Virtual Operation #433
View Raw JSON Data
{
  "block": 41968558,
  "op": [
    "curation_reward",
    {
      "comment_author": "anyx",
      "comment_permlink": "it-s-time-to-decentralize",
      "curator": "greymass",
      "reward": "3.915951 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-03-25T20:50:12",
  "trx_id": "0000000000000000000000000000000000000000",
  "trx_in_block": 4294967295,
  "virtual_op": 433
}
greymassreceived 0.001 SP curation reward for @berniesanders / i-support-the-move-from-steem
2020/03/23 18:00:18
comment authorberniesanders
comment permlinki-support-the-move-from-steem
curatorgreymass
reward1.958180 VESTS
Transaction InfoBlock #41908360/Virtual Operation #507
View Raw JSON Data
{
  "block": 41908360,
  "op": [
    "curation_reward",
    {
      "comment_author": "berniesanders",
      "comment_permlink": "i-support-the-move-from-steem",
      "curator": "greymass",
      "reward": "1.958180 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-03-23T18:00:18",
  "trx_id": "0000000000000000000000000000000000000000",
  "trx_in_block": 4294967295,
  "virtual_op": 507
}
2020/03/23 17:31:33
comment authorblocktrades
comment permlinkwhy-i-won-t-be-compromising-with-justin-sun
curatorgreymass
reward1.958182 VESTS
Transaction InfoBlock #41907794/Virtual Operation #1410
View Raw JSON Data
{
  "block": 41907794,
  "op": [
    "curation_reward",
    {
      "comment_author": "blocktrades",
      "comment_permlink": "why-i-won-t-be-compromising-with-justin-sun",
      "curator": "greymass",
      "reward": "1.958182 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-03-23T17:31:33",
  "trx_id": "0000000000000000000000000000000000000000",
  "trx_in_block": 4294967295,
  "virtual_op": 1410
}
2020/03/18 21:16:45
authoranyx
permlinkit-s-time-to-decentralize
votergreymass
weight10000 (100.00%)
Transaction InfoBlock #41769963/Trx 1c1232d41b81839b01b4a4696b6f2e5c1f335f8e
View Raw JSON Data
{
  "block": 41769963,
  "op": [
    "vote",
    {
      "author": "anyx",
      "permlink": "it-s-time-to-decentralize",
      "voter": "greymass",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-03-18T21:16:45",
  "trx_id": "1c1232d41b81839b01b4a4696b6f2e5c1f335f8e",
  "trx_in_block": 26,
  "virtual_op": 0
}
2020/03/17 02:11:00
authorberniesanders
permlinki-support-the-move-from-steem
votergreymass
weight10000 (100.00%)
Transaction InfoBlock #41718325/Trx 3c8093789de7bbcbc8c6318c6fe0714fec138e44
View Raw JSON Data
{
  "block": 41718325,
  "op": [
    "vote",
    {
      "author": "berniesanders",
      "permlink": "i-support-the-move-from-steem",
      "voter": "greymass",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-03-17T02:11:00",
  "trx_id": "3c8093789de7bbcbc8c6318c6fe0714fec138e44",
  "trx_in_block": 11,
  "virtual_op": 0
}
2020/03/16 17:57:48
authorblocktrades
permlinkwhy-i-won-t-be-compromising-with-justin-sun
votergreymass
weight10000 (100.00%)
Transaction InfoBlock #41708480/Trx 1a96fbfe5e9852cbad87cb0ccf2c1134270de57a
View Raw JSON Data
{
  "block": 41708480,
  "op": [
    "vote",
    {
      "author": "blocktrades",
      "permlink": "why-i-won-t-be-compromising-with-justin-sun",
      "voter": "greymass",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-03-16T17:57:48",
  "trx_id": "1a96fbfe5e9852cbad87cb0ccf2c1134270de57a",
  "trx_in_block": 6,
  "virtual_op": 0
}
2020/03/16 10:20:42
authorsteemitboard
bodyCongratulations @greymass! You have completed the following achievement on the Steem blockchain and have been rewarded with new badge(s) : <table><tr><td><img src="https://steemitimages.com/60x60/http://steemitboard.com/img/notifications/firstcommented.png"></td><td>You got a First Reply</td></tr> </table> <sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@greymass) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=greymass)_</sub> <sub>_If you no longer want to receive notifications, reply to this comment with the word_ `STOP`</sub> ###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!
json metadata{"image":["https://steemitboard.com/img/notify.png"]}
parent authorgreymass
parent permlinkcontributions-overview-of-greymass-for-eosio-thus-far
permlinksteemitboard-notify-greymass-20200316t102041000z
title
Transaction InfoBlock #41699367/Trx 38807abf8756e74b5d6ab64d6dd3b8926828eac2
View Raw JSON Data
{
  "block": 41699367,
  "op": [
    "comment",
    {
      "author": "steemitboard",
      "body": "Congratulations @greymass! You have completed the following achievement on the Steem blockchain and have been rewarded with new badge(s) :\n\n<table><tr><td><img src=\"https://steemitimages.com/60x60/http://steemitboard.com/img/notifications/firstcommented.png\"></td><td>You got a First Reply</td></tr>\n</table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@greymass) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=greymass)_</sub>\n<sub>_If you no longer want to receive notifications, reply to this comment with the word_ `STOP`</sub>\n\n\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
      "json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}",
      "parent_author": "greymass",
      "parent_permlink": "contributions-overview-of-greymass-for-eosio-thus-far",
      "permlink": "steemitboard-notify-greymass-20200316t102041000z",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-03-16T10:20:42",
  "trx_id": "38807abf8756e74b5d6ab64d6dd3b8926828eac2",
  "trx_in_block": 4,
  "virtual_op": 0
}
2020/03/13 23:23:42
authorzoidsoft
bodyYes, I tried Anchor a couple of weeks ago but it won't recognize my Trezor Model T. Did you only support Trezor One?
json metadata{"app":"steemit/0.2"}
parent authorgreymass
parent permlinkq75axv
permlinkq75nng
title
Transaction InfoBlock #41628737/Trx b8a35d45e63f78a2d9ea3f2603b7e299425bc07e
View Raw JSON Data
{
  "block": 41628737,
  "op": [
    "comment",
    {
      "author": "zoidsoft",
      "body": "Yes, I tried Anchor a couple of weeks ago but it won't recognize my Trezor Model T. Did you only support Trezor One?",
      "json_metadata": "{\"app\":\"steemit/0.2\"}",
      "parent_author": "greymass",
      "parent_permlink": "q75axv",
      "permlink": "q75nng",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-03-13T23:23:42",
  "trx_id": "b8a35d45e63f78a2d9ea3f2603b7e299425bc07e",
  "trx_in_block": 0,
  "virtual_op": 0
}
zoidsoftupvoted (100.00%) @greymass / q75axv
2020/03/13 23:21:48
authorgreymass
permlinkq75axv
voterzoidsoft
weight10000 (100.00%)
Transaction InfoBlock #41628699/Trx f94c1d4c39fe28f84c5bae8bff45f54c00c7d060
View Raw JSON Data
{
  "block": 41628699,
  "op": [
    "vote",
    {
      "author": "greymass",
      "permlink": "q75axv",
      "voter": "zoidsoft",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-03-13T23:21:48",
  "trx_id": "f94c1d4c39fe28f84c5bae8bff45f54c00c7d060",
  "trx_in_block": 17,
  "virtual_op": 0
}
2020/03/13 18:49:09
authorgreymass
bodySorry for the late reply - our rebranded/replacement wallet for eos-voter (called Anchor) should resolve this issue. I think what happened is the USB connection library in eos-voter is out of date and all of our effort has gone into Anchor, which is now causing the older versions of eos-voter to not connect. The latest version is 1.0.0-RC6 and can be found on our github page: https://github.com/greymass/eos-voter/releases/tag/v1.0.0-rc6 It's a brand new interface with some familiar features. If you need more support, feel free to join us in our telegram channel: https://t.me/greymass
json metadata{"links":["https://github.com/greymass/eos-voter/releases/tag/v1.0.0-rc6","https://t.me/greymass"],"app":"steemit/0.2"}
parent authorzoidsoft
parent permlinkq68a0t
permlinkq75axv
title
Transaction InfoBlock #41623254/Trx ec304150567e687f7f46ae94ee7f916c06ed78e9
View Raw JSON Data
{
  "block": 41623254,
  "op": [
    "comment",
    {
      "author": "greymass",
      "body": "Sorry for the late reply - our rebranded/replacement wallet for eos-voter (called Anchor) should resolve this issue. I think what happened is the USB connection library in eos-voter is out of date and all of our effort has gone into Anchor, which is now causing the older versions of eos-voter to not connect.\n\nThe latest version is 1.0.0-RC6 and can be found on our github page:\n\nhttps://github.com/greymass/eos-voter/releases/tag/v1.0.0-rc6\n\nIt's a brand new interface with some familiar features. If you need more support, feel free to join us in our telegram channel: https://t.me/greymass",
      "json_metadata": "{\"links\":[\"https://github.com/greymass/eos-voter/releases/tag/v1.0.0-rc6\",\"https://t.me/greymass\"],\"app\":\"steemit/0.2\"}",
      "parent_author": "zoidsoft",
      "parent_permlink": "q68a0t",
      "permlink": "q75axv",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-03-13T18:49:09",
  "trx_id": "ec304150567e687f7f46ae94ee7f916c06ed78e9",
  "trx_in_block": 0,
  "virtual_op": 0
}
2020/02/24 22:48:30
authorzoidsoft
bodyDo you have an interface working for the Ledger Nano X yet? I get a spinning wheel that never ends when trying to connect a Nano X to Eos voter. ![Screen Shot 2020-02-24 at 5.47.47 PM.png](https://cdn.steemitimages.com/DQmRcpofJEehkLDCuxYmroUgAia8nkiYtqLfRcT1pqhvndE/Screen%20Shot%202020-02-24%20at%205.47.47%20PM.png) It never gets past the above condition.
json metadata{"image":["https://cdn.steemitimages.com/DQmRcpofJEehkLDCuxYmroUgAia8nkiYtqLfRcT1pqhvndE/Screen%20Shot%202020-02-24%20at%205.47.47%20PM.png"],"app":"steemit/0.2"}
parent authorgreymass
parent permlinkconverting-an-eos-account-to-use-a-ledger-with-eos-voter-0-6-x-greymass-wallet
permlinkq68a0t
title
Transaction InfoBlock #41111636/Trx c2859e544b1e4a6519d7db960f1482fc7255ab4c
View Raw JSON Data
{
  "block": 41111636,
  "op": [
    "comment",
    {
      "author": "zoidsoft",
      "body": "Do you have an interface working for the Ledger Nano X yet? I get a spinning wheel that never ends when trying to connect a Nano X to Eos voter.\n\n\n![Screen Shot 2020-02-24 at 5.47.47 PM.png](https://cdn.steemitimages.com/DQmRcpofJEehkLDCuxYmroUgAia8nkiYtqLfRcT1pqhvndE/Screen%20Shot%202020-02-24%20at%205.47.47%20PM.png)\n\nIt never gets past the above condition.",
      "json_metadata": "{\"image\":[\"https://cdn.steemitimages.com/DQmRcpofJEehkLDCuxYmroUgAia8nkiYtqLfRcT1pqhvndE/Screen%20Shot%202020-02-24%20at%205.47.47%20PM.png\"],\"app\":\"steemit/0.2\"}",
      "parent_author": "greymass",
      "parent_permlink": "converting-an-eos-account-to-use-a-ledger-with-eos-voter-0-6-x-greymass-wallet",
      "permlink": "q68a0t",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-02-24T22:48:30",
  "trx_id": "c2859e544b1e4a6519d7db960f1482fc7255ab4c",
  "trx_in_block": 10,
  "virtual_op": 0
}
2020/02/02 08:35:24
authorgreymass
body@@ -4903,16 +4903,643 @@ tform.%0A%0A +%3E **Statement Update in 2020** - The above statement was far too much of an optimistic stance when it was originally made. Greymass at the time of this update now works within a few select %22kickback systems%22 and contributes a small percentage of its block producer revenue to proxies who elect value-adding producers. Unfortunately. the EOS ecosystem today requires this of us in order to be within a paid position, and Greymass feels this path is the lesser of two evils. We understand the damage this behavior causes within these systems and will continue to push for the change to help solve the issues vote buying causes.%0A%0A Delegate
json metadata{"users":["jesta","anyx","steemcleaners","cheetah"],"image":["https://greymass.com/logo.png","http://anyx.ca/wp-content/uploads/2018/05/677686.jpeg","http://anyx.ca/wp-content/uploads/2018/05/profile-1.jpg"],"links":["https://greymass.com","https://github.com/greymass","https://twitter.com/greymass"],"format":"markdown","app":"steemit/0.1","tags":["blockproducer","eosio"]}
parent author
parent permlinkeos
permlinkannouncing-greymass-for-eos-block-production
titleAnnouncing Greymass for EOS Block Production
Transaction InfoBlock #40462411/Trx 77f8621bbde117653799a497569769314bf7b975
View Raw JSON Data
{
  "block": 40462411,
  "op": [
    "comment",
    {
      "author": "greymass",
      "body": "@@ -4903,16 +4903,643 @@\n tform.%0A%0A\n+%3E **Statement Update in 2020** - The above statement was far too much of an optimistic stance when it was originally made. Greymass at the time of this update now works within a few select %22kickback systems%22 and contributes a small percentage of its block producer revenue to proxies who elect value-adding producers. Unfortunately. the EOS ecosystem today requires this of us in order to be within a paid position, and Greymass feels this path is the lesser of two evils. We understand the damage this behavior causes within these systems and will continue to push for the change to help solve the issues vote buying causes.%0A%0A\n Delegate\n",
      "json_metadata": "{\"users\":[\"jesta\",\"anyx\",\"steemcleaners\",\"cheetah\"],\"image\":[\"https://greymass.com/logo.png\",\"http://anyx.ca/wp-content/uploads/2018/05/677686.jpeg\",\"http://anyx.ca/wp-content/uploads/2018/05/profile-1.jpg\"],\"links\":[\"https://greymass.com\",\"https://github.com/greymass\",\"https://twitter.com/greymass\"],\"format\":\"markdown\",\"app\":\"steemit/0.1\",\"tags\":[\"blockproducer\",\"eosio\"]}",
      "parent_author": "",
      "parent_permlink": "eos",
      "permlink": "announcing-greymass-for-eos-block-production",
      "title": "Announcing Greymass for EOS Block Production"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-02-02T08:35:24",
  "trx_id": "77f8621bbde117653799a497569769314bf7b975",
  "trx_in_block": 36,
  "virtual_op": 0
}
2019/12/15 07:41:27
authorgreymass
permlinkannouncing-our-wax-guild-candidacy
voterjimmyfotogallery
weight10000 (100.00%)
Transaction InfoBlock #39052827/Trx b5bcf29a2531443f0cd8f02db1468a78a38c33d6
View Raw JSON Data
{
  "block": 39052827,
  "op": [
    "vote",
    {
      "author": "greymass",
      "permlink": "announcing-our-wax-guild-candidacy",
      "voter": "jimmyfotogallery",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-12-15T07:41:27",
  "trx_id": "b5bcf29a2531443f0cd8f02db1468a78a38c33d6",
  "trx_in_block": 1,
  "virtual_op": 0
}
2019/11/15 02:04:48
authorgreymass
permlinkreprint-build-your-blog-or-website-on-the-blockchain
votermikewick77
weight10000 (100.00%)
Transaction InfoBlock #38183708/Trx c3d78670ce53e6505aa166c7f0c405ea413296e1
View Raw JSON Data
{
  "block": 38183708,
  "op": [
    "vote",
    {
      "author": "greymass",
      "permlink": "reprint-build-your-blog-or-website-on-the-blockchain",
      "voter": "mikewick77",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-11-15T02:04:48",
  "trx_id": "c3d78670ce53e6505aa166c7f0c405ea413296e1",
  "trx_in_block": 24,
  "virtual_op": 0
}
2019/10/13 17:16:00
authorgreymass
permlinkan-eos-smart-contract-for-block-producer-information
voterzver
weight10000 (100.00%)
Transaction InfoBlock #37253368/Trx 4b7dae6202056a02e2e22a9e82d4b0531d3e25db
View Raw JSON Data
{
  "block": 37253368,
  "op": [
    "vote",
    {
      "author": "greymass",
      "permlink": "an-eos-smart-contract-for-block-producer-information",
      "voter": "zver",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-10-13T17:16:00",
  "trx_id": "4b7dae6202056a02e2e22a9e82d4b0531d3e25db",
  "trx_in_block": 5,
  "virtual_op": 0
}
2019/09/23 06:56:00
authorgreymass
permlinkinflation-centralization-and-dpos
voterjele.meetup
weight10000 (100.00%)
Transaction InfoBlock #36666195/Trx 0e6c3e5783f429875a7c8d75d1e7e79724d4b5f0
View Raw JSON Data
{
  "block": 36666195,
  "op": [
    "vote",
    {
      "author": "greymass",
      "permlink": "inflation-centralization-and-dpos",
      "voter": "jele.meetup",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-09-23T06:56:00",
  "trx_id": "0e6c3e5783f429875a7c8d75d1e7e79724d4b5f0",
  "trx_in_block": 2,
  "virtual_op": 0
}
2019/09/23 06:52:30
authorgreymass
permlinkinflation-centralization-and-dpos
voterfotomeetup
weight10000 (100.00%)
Transaction InfoBlock #36666125/Trx 3027f9789649084c0d06f6f3405853f707595faf
View Raw JSON Data
{
  "block": 36666125,
  "op": [
    "vote",
    {
      "author": "greymass",
      "permlink": "inflation-centralization-and-dpos",
      "voter": "fotomeetup",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-09-23T06:52:30",
  "trx_id": "3027f9789649084c0d06f6f3405853f707595faf",
  "trx_in_block": 17,
  "virtual_op": 0
}
2019/09/23 06:43:21
authorjimmyfotogallery
bodyjesta, I vote for your team from Day 0 till now. So sad to see you guys fall out of the pay list. I am from China and understand the value of Chinese companies and Government offical. EOS will finally collapsed and centralied if the current situation keep going on.
json metadata{"tags":["eos"],"app":"steemit/0.1"}
parent authorgreymass
parent permlinkcontributions-overview-of-greymass-for-eosio-thus-far
permlinkpy9uo9
title
Transaction InfoBlock #36665942/Trx 4ec869068e965c8ac52a1d4af750fac1e329ba71
View Raw JSON Data
{
  "block": 36665942,
  "op": [
    "comment",
    {
      "author": "jimmyfotogallery",
      "body": "jesta, I vote for your team from Day 0 till now. So sad to see you guys fall out of the pay list. I am from China and understand the value of Chinese companies and Government offical. EOS will finally collapsed and centralied if the current situation keep going on.",
      "json_metadata": "{\"tags\":[\"eos\"],\"app\":\"steemit/0.1\"}",
      "parent_author": "greymass",
      "parent_permlink": "contributions-overview-of-greymass-for-eosio-thus-far",
      "permlink": "py9uo9",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-09-23T06:43:21",
  "trx_id": "4ec869068e965c8ac52a1d4af750fac1e329ba71",
  "trx_in_block": 16,
  "virtual_op": 0
}
dtubesent 0.001 STEEM to @greymass- "DTube Coin Round #1 is live! Visit https://token.d.tube for more information"
2019/09/20 20:52:30
amount0.001 STEEM
fromdtube
memoDTube Coin Round #1 is live! Visit https://token.d.tube for more information
togreymass
Transaction InfoBlock #36596667/Trx a872875a4517316b75efb28698097e7d383eb58f
View Raw JSON Data
{
  "block": 36596667,
  "op": [
    "transfer",
    {
      "amount": "0.001 STEEM",
      "from": "dtube",
      "memo": "DTube Coin Round #1 is live! Visit https://token.d.tube for more information",
      "to": "greymass"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-09-20T20:52:30",
  "trx_id": "a872875a4517316b75efb28698097e7d383eb58f",
  "trx_in_block": 0,
  "virtual_op": 0
}
dtubesent 0.001 STEEM to @greymass- "Final call to claim your DTube account! It takes only 5 minutes. Go now to https://d.tube"
2019/09/03 17:50:09
amount0.001 STEEM
fromdtube
memoFinal call to claim your DTube account! It takes only 5 minutes. Go now to https://d.tube
togreymass
Transaction InfoBlock #36105105/Trx 28f5059216b4dbd9d46a1dc6ac1756b376c0fd1d
View Raw JSON Data
{
  "block": 36105105,
  "op": [
    "transfer",
    {
      "amount": "0.001 STEEM",
      "from": "dtube",
      "memo": "Final call to claim your DTube account! It takes only 5 minutes. Go now to https://d.tube",
      "to": "greymass"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-09-03T17:50:09",
  "trx_id": "28f5059216b4dbd9d46a1dc6ac1756b376c0fd1d",
  "trx_in_block": 2,
  "virtual_op": 0
}
2019/08/19 15:08:27
authorgreymass
permlinkcontributions-overview-of-greymass-for-eosio-thus-far
voterjertrasoim
weight-1000 (-10.00%)
Transaction InfoBlock #35691921/Trx 0f8d6d03e912af509ea7a65a16bf1b704f042207
View Raw JSON Data
{
  "block": 35691921,
  "op": [
    "vote",
    {
      "author": "greymass",
      "permlink": "contributions-overview-of-greymass-for-eosio-thus-far",
      "voter": "jertrasoim",
      "weight": -1000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-08-19T15:08:27",
  "trx_id": "0f8d6d03e912af509ea7a65a16bf1b704f042207",
  "trx_in_block": 2,
  "virtual_op": 0
}
2019/08/17 16:37:27
authorgreymass
permlinkcontributions-overview-of-greymass-for-eosio-thus-far
votergrenai
weight-1000 (-10.00%)
Transaction InfoBlock #35636209/Trx cf6469cd68f48ef316727b4444b9bfbd3fb802e6
View Raw JSON Data
{
  "block": 35636209,
  "op": [
    "vote",
    {
      "author": "greymass",
      "permlink": "contributions-overview-of-greymass-for-eosio-thus-far",
      "voter": "grenai",
      "weight": -1000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-08-17T16:37:27",
  "trx_id": "cf6469cd68f48ef316727b4444b9bfbd3fb802e6",
  "trx_in_block": 18,
  "virtual_op": 0
}
2019/08/17 05:08:06
authorpnc
body@greymass team have been doing great work for the EOSIO community since the beginning. I do support their work and encourage everyone to vote for them. They not only support EOS Mainnet, but also EOSIO sister chains.
json metadata{"tags":["eos"],"app":"esteem/2.2.0-surfer","format":"markdown+html","community":"esteem.app"}
parent authorgreymass
parent permlinkcontributions-overview-of-greymass-for-eosio-thus-far
permlinkre-greymass-2019817t186145z
title
Transaction InfoBlock #35622445/Trx 99c61b22daaadf27b841c29128282c9c754da9e6
View Raw JSON Data
{
  "block": 35622445,
  "op": [
    "comment",
    {
      "author": "pnc",
      "body": "@greymass team have been doing great work for the EOSIO community since the beginning. I do support their work and encourage everyone to vote for them. They not only support EOS Mainnet, but also EOSIO sister chains.",
      "json_metadata": "{\"tags\":[\"eos\"],\"app\":\"esteem/2.2.0-surfer\",\"format\":\"markdown+html\",\"community\":\"esteem.app\"}",
      "parent_author": "greymass",
      "parent_permlink": "contributions-overview-of-greymass-for-eosio-thus-far",
      "permlink": "re-greymass-2019817t186145z",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-08-17T05:08:06",
  "trx_id": "99c61b22daaadf27b841c29128282c9c754da9e6",
  "trx_in_block": 12,
  "virtual_op": 0
}
2019/08/17 05:05:06
authorgreymass
permlinkcontributions-overview-of-greymass-for-eosio-thus-far
voterpnc
weight10000 (100.00%)
Transaction InfoBlock #35622385/Trx 429c7b766b396b76b5d2d7a9f425a250fa9ccc8a
View Raw JSON Data
{
  "block": 35622385,
  "op": [
    "vote",
    {
      "author": "greymass",
      "permlink": "contributions-overview-of-greymass-for-eosio-thus-far",
      "voter": "pnc",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-08-17T05:05:06",
  "trx_id": "429c7b766b396b76b5d2d7a9f425a250fa9ccc8a",
  "trx_in_block": 20,
  "virtual_op": 0
}
2019/08/17 03:29:00
authorgreymass
permlinkcontributions-overview-of-greymass-for-eosio-thus-far
voterv4vapid
weight1000 (10.00%)
Transaction InfoBlock #35620465/Trx f5f8df77753e74af695cd113d10865740ea4d856
View Raw JSON Data
{
  "block": 35620465,
  "op": [
    "vote",
    {
      "author": "greymass",
      "permlink": "contributions-overview-of-greymass-for-eosio-thus-far",
      "voter": "v4vapid",
      "weight": 1000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-08-17T03:29:00",
  "trx_id": "f5f8df77753e74af695cd113d10865740ea4d856",
  "trx_in_block": 12,
  "virtual_op": 0
}
2019/08/17 03:00:06
authorgreymass
permlinkcontributions-overview-of-greymass-for-eosio-thus-far
votermjhomb
weight10000 (100.00%)
Transaction InfoBlock #35619888/Trx ca178df2e1a7fec54b0e612bf18dcdb4fe6712ee
View Raw JSON Data
{
  "block": 35619888,
  "op": [
    "vote",
    {
      "author": "greymass",
      "permlink": "contributions-overview-of-greymass-for-eosio-thus-far",
      "voter": "mjhomb",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-08-17T03:00:06",
  "trx_id": "ca178df2e1a7fec54b0e612bf18dcdb4fe6712ee",
  "trx_in_block": 21,
  "virtual_op": 0
}
2019/08/16 19:34:42
authorgreymass
permlinkcontributions-overview-of-greymass-for-eosio-thus-far
voterwarofcraft
weight2000 (20.00%)
Transaction InfoBlock #35610993/Trx 65c61229072ec55aa9d58900d9d475d7c9ac70f2
View Raw JSON Data
{
  "block": 35610993,
  "op": [
    "vote",
    {
      "author": "greymass",
      "permlink": "contributions-overview-of-greymass-for-eosio-thus-far",
      "voter": "warofcraft",
      "weight": 2000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-08-16T19:34:42",
  "trx_id": "65c61229072ec55aa9d58900d9d475d7c9ac70f2",
  "trx_in_block": 4,
  "virtual_op": 0
}
2019/08/16 19:12:12
authorgreymass
permlinkcontributions-overview-of-greymass-for-eosio-thus-far
voterwhatsup
weight1900 (19.00%)
Transaction InfoBlock #35610543/Trx 13771b319bd4720922ca91af5c6d5d4e119095af
View Raw JSON Data
{
  "block": 35610543,
  "op": [
    "vote",
    {
      "author": "greymass",
      "permlink": "contributions-overview-of-greymass-for-eosio-thus-far",
      "voter": "whatsup",
      "weight": 1900
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-08-16T19:12:12",
  "trx_id": "13771b319bd4720922ca91af5c6d5d4e119095af",
  "trx_in_block": 7,
  "virtual_op": 0
}
2019/08/16 19:09:24
allow curation rewardstrue
allow votestrue
authorgreymass
extensions[]
max accepted payout0.000 SBD
percent steem dollars10000
permlinkcontributions-overview-of-greymass-for-eosio-thus-far
Transaction InfoBlock #35610487/Trx 08231b758f28e4fe511ccab40237f2194e3efe5f
View Raw JSON Data
{
  "block": 35610487,
  "op": [
    "comment_options",
    {
      "allow_curation_rewards": true,
      "allow_votes": true,
      "author": "greymass",
      "extensions": [],
      "max_accepted_payout": "0.000 SBD",
      "percent_steem_dollars": 10000,
      "permlink": "contributions-overview-of-greymass-for-eosio-thus-far"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-08-16T19:09:24",
  "trx_id": "08231b758f28e4fe511ccab40237f2194e3efe5f",
  "trx_in_block": 14,
  "virtual_op": 0
}
2019/08/16 19:09:24
authorgreymass
bodyOKEx, a digital asset exchange many of you are familiar with, recently launched a block producer voting program for their clients. This initiative will allow the OKEx clients, who hold EOS within their exchange, to participate in the block producer elections on-going on EOS. [https://www.okex.com/pages/pro/eos-race](https://www.okex.com/pages/pro/eos-race) All OKEx users are eligible to vote every 12 hours until the 20th of August. Through this program OKEx asked each block producer to submit information about themselves, their achievements within the space, and how they contribute to the success of the EOS ecosystem. Today we'd like to publicly share what we came up with for our submission as to why EOS stakeholders should consider voting for Greymass (`teamgreymass`). We have struggled recently in BP rankings, dropping from our all time high in the top 21 last year, now down into the mid-50s. _Every vote matters_, so we appreciate your time in considering us and your support should you choose to vote for Greymass as a block producer on the EOS network. Thank you! _The remainder of this post will be the Greymass information, in the format requested by OKEx, highlighting the data we feel is important._ --- ### Greymass Contribution Summary **Server Locations** - North America - Michigan (United States) - Full server rack of Greymass-owned infrastructure - ~$80,000 USD invested in high-end hardware - Beauharnois (Canada) - Dedicated Server Rentals - Europe - Falkenstein (Germany) - Dedicated Servers Rentals **Core Team Location** - North America (with additional team members in Europe and Asia) **Your achievements in blockchain education, social impact and community development (Please specify events/examples and indicate the size of community)** - [Greymass Newsletter](https://greymass.substack.com/) - a bi-weekly newsletter covering the EOSIO ecosystem. 600 subscribers. - Telegram Communities we operate: - [eos-voter](https://t.me/eoswalletgreymass) (Greymass Wallet) channel of 1100 members - [TeamGreymass](https://t.me/teamgreymass) community chat of 210 members - Regular participation (as attendants and speakers) at international EOSIO community events. - Participated as a Judge in EOSIO Hackathon (20+ participants, 100s in attendance) - Participated in 2019 EOS Governance Panel at the 2019 BP Summit. **Your capabilities/advantages in blockchain technology (Please specify events/example)** - The Greymass team has over 3 years of experience governing and operating DPoS software (starting in 2016). Our team is (or has been) involved in governance for EOS, Steem, Decent, WAX, Insights, Muse, and many other blockchains. We publicly make our stances known on current issues, recently with: - [Retiring the eosio.savings account](https://blog.greymass.com/eos/@greymass/greymass-stance-on-the-retiresaving-proposal) - [Evolving the eosio.token contract](https://blog.greymass.com/eos/@greymass/greymass-support-of-the-tokenauction-referendum-proposal) - [Establishing a Worker Candidate System](https://blog.greymass.com/eos/@greymass/a-simple-system-to-support-blockchain-workers-in-dpos) - Members of the Greymass team have been involved in the blockchain space since 2013, with a large amount of R&D being done across dozens of blockchains.The team is comprised of experienced software developers, research scientists, and systems administrators ranging from a variety of technology-based industries. This knowledge is used to help evaluate solutions to potential problems within the EOSIO ecosystem, such as: - [Proposing alternatives to the current RAM implementation](https://blog.greymass.com/eos/@greymass/leasing-eos-ram-without-forceful-memory-frees) - [Studying the centralizing forces caused by Inflation](https://blog.greymass.com/eos/@greymass/inflation-centralization-and-dpos) - [Considering the effects of competition within resource billing on EOS](https://blog.greymass.com/eos/@greymass/performance-and-transaction-billing-on-eos-a-cooperative-effort-not-a-competitive-one) - Greymass has specialized DPoS systems administrators that operate one of the most used [publicly available EOS API clusters](https://blog.greymass.com/eosio/@greymass/the-value-of-public-apis-and-a-look-inside-one-of-the-largest-greymass) in the ecosystem (via [https://eos.greymass.com](https://eos.greymass.com)), serving between 200-350 million API requests per day and powering many popular dApps. - Single HTTPS endpoint with intelligent routing based on geography and request type, which forwards individual requests to specialized/optimized hardware suited for each task. - Geographically load balanced servers spread across North America, Europe, and soon in south-east Asia. - Support for all EOSIO v1 API methods, including the native full history API and additional calls via [eosio-api-ext](https://github.com/greymass/eosio-api-ext). - Serves as a testbed for our research and development towards API and EOSIO scaling solutions. **Developed user tools and related contributions** - We created [eos-voter](https://github.com/greymass/eos-voter), which was [one of the first](https://blog.greymass.com/eos/@greymass/announcing-eos-voter-an-eos-block-producer-voting-tool-and-light-wallet) EOSIO desktop wallets to launch during the EOS mainnet genesis, with over 142,000 downloads, and are currently working on the next evolution of this wallet called [Anchor](https://blog.greymass.com/eos/@greymass/the-future-of-the-greymass-wallet-beta-version-available-now). - Built and implemented [Light History](https://steemit.com/eos/@greymass/introducing-light-history-nodes-for-eos) ([github](https://github.com/greymass/eos/tree/hapi-limited)), a solution that allows EOS node operators to maintain partial history on a server at a fraction of the cost of operating under full history. Many block producers and independant node operators now either run this as their history solution or as part of a larger multi-layered history solution. - Created the EOSIO Signing Request protocol (specification [EEP-7](https://github.com/greymass/EEPs/blob/eep-x/EEPS/eep-7.md)) and associated tooling to foster the creation of a new type of dApp ecosystem. This signing protocol allows requests to be transported natively through http handlers within a device, shareable by QR codes, or sent as plain text through any communication medium. To facilitate this we have created the following: - eosio-signing-transport library/sdk for app integration ([github](https://github.com/greymass/eosio-signing-transport), [npm](https://www.npmjs.com/package/eosio-uri)) - [eosio.to](https://github.com/greymass/eosio.to) - a HTTP alternative to display and share signing requests ([example](https://eosio.to/gWNgZGRkAIFXBqEFopc6760yugsVYWCA0ZIwBgwwNmycGBer1nsKpBQA)) - a [GUI for creating/editing Signing Requests](https://github.com/greymass/eosio-uri-builder) ([example](https://greymass.github.io/eosio-uri-builder/gWNgZGRkAIFXBqEFopc6760yugsVYWCA0ZIwBgwwNmycGBer1nsKpBQA)) - integrated signing request protocol into the [Anchor 0.9.0 beta](https://github.com/greymass/eos-voter/releases/tag/v0.9.0-anchor) - Greymass was one of the organizations involved in the creation of the Referendum system deployed on EOS (the [eosio.forum](https://bloks.io/account/eosio.forum) contract). - We proposed the [3-pieces that make up the referendum system](https://steemit.com/eos/@greymass/the-3-pieces-of-the-eos-referendum-system). - We helped create the specification which the smart contract was built upon. - The referendum system was integrated into eos-voter as of [0.5.3](https://github.com/greymass/eos-voter/releases/tag/v0.5.3). - Built additional EOSIO API endpoints via [eosio-api-ext](https://github.com/greymass/eosio-api-ext) to add additional functionality to optimize API calls. - Established the [Producer JSON Smart Contract](https://github.com/greymass/producerjson) for on-chain BP.json information. - Deployed an [Account Setup Smart Contract](https://github.com/greymass/smart_account_creator) to allow for easy account creation. **Examples of how you foster the diversity of EOS and blockchains (e.g. diversity of your company)** - Greymass consists of a diverse set of members from all over the globe. While we are headquartered in one area for legal purposes, we think of ourselves as a team without borders or boundaries. - Every initiative Greymass takes on is built to run on any EOSIO-based blockchain, as we try not to specifically develop software/tools/prototypes for any individual blockchain. - Each end user product we tackle has support for multiple languages to further extend the reach of EOSIO products. An example of this is that eos-voter currently offers crowd-sourced support for multiple languages to help on-board users which speak all languages. - Greymass seeks to provide global access to all EOSIO blockchains we participate in through geographically diverse offerings of P2P, API, and other data services. **Your expectations for OKEx in the governance and development of EOS** Our expectations of OKEx are that they take on the responsibilities we believe all block producers must share, which is to: - make decisions off what is best for the blockchain over what is best for their organization. - participate in global conversations around the operations, health, and evolution of the blockchain and its ecosystem. - participate in community debates around governance of the blockchain, making positions and decisions widely known. - invested in the long term success of the blockchain. - be available to the community to collect feedback and to determine the will of stakeholders. - be available to audit and test new EOSIO code and smart contracts upgrades. - participate in both technical and non-technical upgrades to the chain itself. Beyond that is all value-add, in which we hope OKEx uses their specialities to help foster growth and innovation within the EOSIO space. <center>![https://greymass-cdn.s3.amazonaws.com/greymass-500x500.png](https://greymass-cdn.s3.amazonaws.com/greymass-500x500.png)</center>
json metadata{"tags":["eos"],"image":["https://greymass-cdn.s3.amazonaws.com/greymass-500x500.png"],"links":["https://www.okex.com/pages/pro/eos-race","https://greymass.substack.com/","https://t.me/eoswalletgreymass","https://t.me/teamgreymass","https://blog.greymass.com/eos/@greymass/greymass-stance-on-the-retiresaving-proposal","https://blog.greymass.com/eos/@greymass/greymass-support-of-the-tokenauction-referendum-proposal","https://blog.greymass.com/eos/@greymass/a-simple-system-to-support-blockchain-workers-in-dpos","https://blog.greymass.com/eos/@greymass/leasing-eos-ram-without-forceful-memory-frees","https://blog.greymass.com/eos/@greymass/inflation-centralization-and-dpos","https://blog.greymass.com/eos/@greymass/performance-and-transaction-billing-on-eos-a-cooperative-effort-not-a-competitive-one","https://blog.greymass.com/eosio/@greymass/the-value-of-public-apis-and-a-look-inside-one-of-the-largest-greymass","https://eos.greymass.com","https://github.com/greymass/eosio-api-ext","https://github.com/greymass/eos-voter","https://blog.greymass.com/eos/@greymass/announcing-eos-voter-an-eos-block-producer-voting-tool-and-light-wallet","https://blog.greymass.com/eos/@greymass/the-future-of-the-greymass-wallet-beta-version-available-now","https://steemit.com/eos/@greymass/introducing-light-history-nodes-for-eos","https://github.com/greymass/eos/tree/hapi-limited","https://github.com/greymass/EEPs/blob/eep-x/EEPS/eep-7.md","https://github.com/greymass/eosio-signing-transport","https://www.npmjs.com/package/eosio-uri","https://github.com/greymass/eosio.to","https://eosio.to/gWNgZGRkAIFXBqEFopc6760yugsVYWCA0ZIwBgwwNmycGBer1nsKpBQA","https://github.com/greymass/eosio-uri-builder","https://greymass.github.io/eosio-uri-builder/gWNgZGRkAIFXBqEFopc6760yugsVYWCA0ZIwBgwwNmycGBer1nsKpBQA","https://github.com/greymass/eos-voter/releases/tag/v0.9.0-anchor","https://bloks.io/account/eosio.forum","https://steemit.com/eos/@greymass/the-3-pieces-of-the-eos-referendum-system","https://github.com/greymass/eos-voter/releases/tag/v0.5.3","https://github.com/greymass/producerjson","https://github.com/greymass/smart_account_creator"],"app":"steemit/0.1","format":"markdown"}
parent author
parent permlinkeos
permlinkcontributions-overview-of-greymass-for-eosio-thus-far
titleContributions overview of Greymass for EOSIO, thus far.
Transaction InfoBlock #35610487/Trx 08231b758f28e4fe511ccab40237f2194e3efe5f
View Raw JSON Data
{
  "block": 35610487,
  "op": [
    "comment",
    {
      "author": "greymass",
      "body": "OKEx, a digital asset exchange many of you are familiar with, recently launched a block producer voting program for their clients. This initiative will allow the OKEx clients, who hold EOS within their exchange, to participate in the block producer elections on-going on EOS.\n\n[https://www.okex.com/pages/pro/eos-race](https://www.okex.com/pages/pro/eos-race)\n\nAll OKEx users are eligible to vote every 12 hours until the 20th of August.\n\nThrough this program OKEx asked each block producer to submit information about themselves, their achievements within the space, and how they contribute to the success of the EOS ecosystem. Today we'd like to publicly share what we came up with for our submission as to why EOS stakeholders should consider voting for Greymass (`teamgreymass`).\n\nWe have struggled recently in BP rankings, dropping from our all time high in the top 21 last year, now down into the mid-50s. _Every vote matters_, so we appreciate your time in considering us and your support should you choose to vote for Greymass as a block producer on the EOS network. Thank you!\n\n_The remainder of this post will be the Greymass information, in the format requested by OKEx, highlighting the data we feel is important._\n\n---\n\n### Greymass Contribution Summary\n\n**Server Locations**\n\n- North America\n    - Michigan (United States)\n        - Full server rack of Greymass-owned infrastructure \n            - ~$80,000 USD invested in high-end hardware\n    - Beauharnois (Canada)\n        - Dedicated Server Rentals\n- Europe\n    - Falkenstein (Germany)\n        - Dedicated Servers Rentals\n\n**Core Team Location**\n\n- North America (with additional team members in Europe and Asia)\n\n**Your achievements in blockchain education, social impact and community development (Please specify events/examples and indicate the size of community)**\n\n- [Greymass Newsletter](https://greymass.substack.com/) - a bi-weekly newsletter covering the EOSIO ecosystem. 600 subscribers. \n- Telegram Communities we operate:\n    - [eos-voter](https://t.me/eoswalletgreymass) (Greymass Wallet) channel of 1100 members \n    - [TeamGreymass](https://t.me/teamgreymass) community chat of 210 members\n- Regular participation (as attendants and speakers) at international EOSIO community events. \n    - Participated as a Judge in EOSIO Hackathon (20+ participants, 100s in attendance)\n    - Participated in 2019 EOS Governance Panel at the 2019 BP Summit.\n\n**Your capabilities/advantages in blockchain technology (Please specify events/example)**\n\n- The Greymass team has over 3 years of experience governing and operating DPoS software (starting in 2016). Our team is (or has been) involved in governance for EOS, Steem, Decent, WAX, Insights, Muse, and many other blockchains. We publicly make our stances known on current issues, recently with:\n    - [Retiring the eosio.savings account](https://blog.greymass.com/eos/@greymass/greymass-stance-on-the-retiresaving-proposal)\n    - [Evolving the eosio.token contract](https://blog.greymass.com/eos/@greymass/greymass-support-of-the-tokenauction-referendum-proposal)\n    - [Establishing a Worker Candidate System](https://blog.greymass.com/eos/@greymass/a-simple-system-to-support-blockchain-workers-in-dpos)\n- Members of the Greymass team have been involved in the blockchain space since 2013, with a large amount of R&D being done across dozens of blockchains.The team is comprised of experienced software developers, research scientists, and systems administrators ranging from a variety of technology-based industries. This knowledge is used to help evaluate solutions to potential problems within the EOSIO ecosystem, such as:\n    - [Proposing alternatives to the current RAM implementation](https://blog.greymass.com/eos/@greymass/leasing-eos-ram-without-forceful-memory-frees)\n    - [Studying the centralizing forces caused by Inflation](https://blog.greymass.com/eos/@greymass/inflation-centralization-and-dpos)\n    - [Considering the effects of competition within resource billing on EOS](https://blog.greymass.com/eos/@greymass/performance-and-transaction-billing-on-eos-a-cooperative-effort-not-a-competitive-one)\n- Greymass has specialized DPoS systems administrators that operate one of the most used [publicly available EOS API clusters](https://blog.greymass.com/eosio/@greymass/the-value-of-public-apis-and-a-look-inside-one-of-the-largest-greymass) in the ecosystem (via [https://eos.greymass.com](https://eos.greymass.com)), serving between 200-350 million API requests per day and powering many popular dApps. \n    - Single HTTPS endpoint with intelligent routing based on geography and request  type, which forwards individual requests to specialized/optimized hardware suited for each task.\n    - Geographically load balanced servers spread across North America, Europe, and soon in south-east Asia.\n    - Support for all EOSIO v1 API methods, including the native full history API and additional calls via [eosio-api-ext](https://github.com/greymass/eosio-api-ext).\n    - Serves as a testbed for our research and development towards API and EOSIO scaling solutions.\n\n**Developed user tools and related contributions**\n\n- We created [eos-voter](https://github.com/greymass/eos-voter), which was [one of the first](https://blog.greymass.com/eos/@greymass/announcing-eos-voter-an-eos-block-producer-voting-tool-and-light-wallet) EOSIO desktop wallets to launch during the EOS mainnet genesis, with over 142,000 downloads, and are currently working on the next evolution of this wallet called [Anchor](https://blog.greymass.com/eos/@greymass/the-future-of-the-greymass-wallet-beta-version-available-now).\n- Built and implemented [Light History](https://steemit.com/eos/@greymass/introducing-light-history-nodes-for-eos) ([github](https://github.com/greymass/eos/tree/hapi-limited)), a solution that allows EOS node operators to maintain partial history on a server at a fraction of the cost of operating under full history. Many block producers and independant node operators now either run this as their history solution or as part of a larger multi-layered history solution.\n- Created the EOSIO Signing Request protocol (specification [EEP-7](https://github.com/greymass/EEPs/blob/eep-x/EEPS/eep-7.md)) and associated tooling to foster the creation of a new type of dApp ecosystem. This signing protocol allows requests to be transported natively through http handlers within a device, shareable by QR codes, or sent as plain text through any communication medium. To facilitate this we have created the following:\n    - eosio-signing-transport library/sdk for app integration ([github](https://github.com/greymass/eosio-signing-transport), [npm](https://www.npmjs.com/package/eosio-uri))\n    - [eosio.to](https://github.com/greymass/eosio.to) - a HTTP alternative to display and share signing requests ([example](https://eosio.to/gWNgZGRkAIFXBqEFopc6760yugsVYWCA0ZIwBgwwNmycGBer1nsKpBQA))\n    - a [GUI for creating/editing Signing Requests](https://github.com/greymass/eosio-uri-builder) ([example](https://greymass.github.io/eosio-uri-builder/gWNgZGRkAIFXBqEFopc6760yugsVYWCA0ZIwBgwwNmycGBer1nsKpBQA))\n    - integrated signing request protocol into the [Anchor 0.9.0 beta](https://github.com/greymass/eos-voter/releases/tag/v0.9.0-anchor)\n- Greymass was one of the organizations involved in the creation of the Referendum system deployed on EOS (the [eosio.forum](https://bloks.io/account/eosio.forum) contract).\n    - We proposed the [3-pieces that make up the referendum system](https://steemit.com/eos/@greymass/the-3-pieces-of-the-eos-referendum-system).\n    - We helped create the specification which the smart contract was built upon.\n    - The referendum system was integrated into eos-voter as of [0.5.3](https://github.com/greymass/eos-voter/releases/tag/v0.5.3).\n- Built additional EOSIO API endpoints via [eosio-api-ext](https://github.com/greymass/eosio-api-ext) to add additional functionality to optimize API calls.\n- Established the [Producer JSON Smart Contract](https://github.com/greymass/producerjson) for on-chain BP.json information.\n- Deployed an [Account Setup Smart Contract](https://github.com/greymass/smart_account_creator) to allow for easy account creation. \n\n**Examples of how you foster the diversity of EOS and blockchains (e.g. diversity of your company)**\n\n- Greymass consists of a diverse set of members from all over the globe. While we are headquartered in one area for legal purposes, we think of ourselves as a team without borders or boundaries. \n- Every initiative Greymass takes on is built to run on any EOSIO-based blockchain, as we try not to specifically develop software/tools/prototypes for any individual blockchain. \n- Each end user product we tackle has support for multiple languages to further extend the reach of EOSIO products. An example of this is that eos-voter currently offers crowd-sourced support for multiple languages to help on-board users which speak all languages.\n- Greymass seeks to provide global access to all EOSIO blockchains we participate in through geographically diverse offerings of P2P, API, and other data services.\n\n**Your expectations for OKEx in the governance and development of EOS**\n\nOur expectations of OKEx are that they take on the responsibilities we believe all block producers must share, which is to:\n\n- make decisions off what is best for the blockchain over what is best for their organization.\n- participate in global conversations around the operations, health, and evolution of the blockchain and its ecosystem.\n- participate in community debates around governance of the blockchain, making positions and decisions widely known.\n- invested in the long term success of the blockchain.\n- be available to the community to collect feedback and to determine the will of stakeholders.\n- be available to audit and test new EOSIO code and smart contracts upgrades.\n- participate in both technical and non-technical upgrades to the chain itself.\n\nBeyond that is all value-add, in which we hope OKEx uses their specialities to help foster growth and innovation within the EOSIO space.\n\n<center>![https://greymass-cdn.s3.amazonaws.com/greymass-500x500.png](https://greymass-cdn.s3.amazonaws.com/greymass-500x500.png)</center>",
      "json_metadata": "{\"tags\":[\"eos\"],\"image\":[\"https://greymass-cdn.s3.amazonaws.com/greymass-500x500.png\"],\"links\":[\"https://www.okex.com/pages/pro/eos-race\",\"https://greymass.substack.com/\",\"https://t.me/eoswalletgreymass\",\"https://t.me/teamgreymass\",\"https://blog.greymass.com/eos/@greymass/greymass-stance-on-the-retiresaving-proposal\",\"https://blog.greymass.com/eos/@greymass/greymass-support-of-the-tokenauction-referendum-proposal\",\"https://blog.greymass.com/eos/@greymass/a-simple-system-to-support-blockchain-workers-in-dpos\",\"https://blog.greymass.com/eos/@greymass/leasing-eos-ram-without-forceful-memory-frees\",\"https://blog.greymass.com/eos/@greymass/inflation-centralization-and-dpos\",\"https://blog.greymass.com/eos/@greymass/performance-and-transaction-billing-on-eos-a-cooperative-effort-not-a-competitive-one\",\"https://blog.greymass.com/eosio/@greymass/the-value-of-public-apis-and-a-look-inside-one-of-the-largest-greymass\",\"https://eos.greymass.com\",\"https://github.com/greymass/eosio-api-ext\",\"https://github.com/greymass/eos-voter\",\"https://blog.greymass.com/eos/@greymass/announcing-eos-voter-an-eos-block-producer-voting-tool-and-light-wallet\",\"https://blog.greymass.com/eos/@greymass/the-future-of-the-greymass-wallet-beta-version-available-now\",\"https://steemit.com/eos/@greymass/introducing-light-history-nodes-for-eos\",\"https://github.com/greymass/eos/tree/hapi-limited\",\"https://github.com/greymass/EEPs/blob/eep-x/EEPS/eep-7.md\",\"https://github.com/greymass/eosio-signing-transport\",\"https://www.npmjs.com/package/eosio-uri\",\"https://github.com/greymass/eosio.to\",\"https://eosio.to/gWNgZGRkAIFXBqEFopc6760yugsVYWCA0ZIwBgwwNmycGBer1nsKpBQA\",\"https://github.com/greymass/eosio-uri-builder\",\"https://greymass.github.io/eosio-uri-builder/gWNgZGRkAIFXBqEFopc6760yugsVYWCA0ZIwBgwwNmycGBer1nsKpBQA\",\"https://github.com/greymass/eos-voter/releases/tag/v0.9.0-anchor\",\"https://bloks.io/account/eosio.forum\",\"https://steemit.com/eos/@greymass/the-3-pieces-of-the-eos-referendum-system\",\"https://github.com/greymass/eos-voter/releases/tag/v0.5.3\",\"https://github.com/greymass/producerjson\",\"https://github.com/greymass/smart_account_creator\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
      "parent_author": "",
      "parent_permlink": "eos",
      "permlink": "contributions-overview-of-greymass-for-eosio-thus-far",
      "title": "Contributions overview of Greymass for EOSIO, thus far."
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-08-16T19:09:24",
  "trx_id": "08231b758f28e4fe511ccab40237f2194e3efe5f",
  "trx_in_block": 14,
  "virtual_op": 0
}
2019/07/17 20:12:42
authorsteemitboard
bodyCongratulations @greymass! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@greymass/birthday3.png</td><td>Happy Birthday! - You are on the Steem blockchain for 3 years!</td></tr></table> <sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@greymass) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=greymass)_</sub> ###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!
json metadata{"image":["https://steemitboard.com/img/notify.png"]}
parent authorgreymass
parent permlinkannouncing-our-wax-guild-candidacy
permlinksteemitboard-notify-greymass-20190717t201241000z
title
Transaction InfoBlock #34750382/Trx ce91b8e2a34f8ed134cf4bdcd66b1b70a2015799
View Raw JSON Data
{
  "block": 34750382,
  "op": [
    "comment",
    {
      "author": "steemitboard",
      "body": "Congratulations @greymass! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@greymass/birthday3.png</td><td>Happy Birthday! - You are on the Steem blockchain for 3 years!</td></tr></table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@greymass) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=greymass)_</sub>\n\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
      "json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}",
      "parent_author": "greymass",
      "parent_permlink": "announcing-our-wax-guild-candidacy",
      "permlink": "steemitboard-notify-greymass-20190717t201241000z",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-07-17T20:12:42",
  "trx_id": "ce91b8e2a34f8ed134cf4bdcd66b1b70a2015799",
  "trx_in_block": 2,
  "virtual_op": 0
}
2019/07/16 07:55:03
authorgreymass
permlinkannouncing-our-wax-guild-candidacy
votermjhomb
weight10000 (100.00%)
Transaction InfoBlock #34706870/Trx 139e483c06bac581c022e4113ad17553ac32661f
View Raw JSON Data
{
  "block": 34706870,
  "op": [
    "vote",
    {
      "author": "greymass",
      "permlink": "announcing-our-wax-guild-candidacy",
      "voter": "mjhomb",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-07-16T07:55:03",
  "trx_id": "139e483c06bac581c022e4113ad17553ac32661f",
  "trx_in_block": 17,
  "virtual_op": 0
}
pncreplied to @greymass / puplep
2019/07/16 00:30:24
authorpnc
bodyI support and will vote for @greymass candidature as Wax blockchain Guild. They have been active building and supporting many projects and communities in the DPoS space.
json metadata{"tags":["undefined"],"users":["greymass"],"app":"steemit/0.1"}
parent authorgreymass
parent permlinkannouncing-our-wax-guild-candidacy
permlinkpuplep
title
Transaction InfoBlock #34698000/Trx 1cdc990ea6784af7d417d39d85b1a5ff6e65a351
View Raw JSON Data
{
  "block": 34698000,
  "op": [
    "comment",
    {
      "author": "pnc",
      "body": "I support and will vote for @greymass candidature as  Wax blockchain Guild. They have been active building and supporting many projects and communities in the DPoS space.",
      "json_metadata": "{\"tags\":[\"undefined\"],\"users\":[\"greymass\"],\"app\":\"steemit/0.1\"}",
      "parent_author": "greymass",
      "parent_permlink": "announcing-our-wax-guild-candidacy",
      "permlink": "puplep",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-07-16T00:30:24",
  "trx_id": "1cdc990ea6784af7d417d39d85b1a5ff6e65a351",
  "trx_in_block": 34,
  "virtual_op": 0
}
2019/07/16 00:06:12
authorgreymass
permlinkannouncing-our-wax-guild-candidacy
voterv4vapid
weight2500 (25.00%)
Transaction InfoBlock #34697517/Trx 7fcfed0fd905aaea4e56490e4567c88abacf1eb4
View Raw JSON Data
{
  "block": 34697517,
  "op": [
    "vote",
    {
      "author": "greymass",
      "permlink": "announcing-our-wax-guild-candidacy",
      "voter": "v4vapid",
      "weight": 2500
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-07-16T00:06:12",
  "trx_id": "7fcfed0fd905aaea4e56490e4567c88abacf1eb4",
  "trx_in_block": 18,
  "virtual_op": 0
}
2019/07/15 22:06:33
authorgreymass
permlinkannouncing-our-wax-guild-candidacy
voterdmwh
weight10000 (100.00%)
Transaction InfoBlock #34695126/Trx bc4dff72f06f8060c2f4d0d55f502421982634a1
View Raw JSON Data
{
  "block": 34695126,
  "op": [
    "vote",
    {
      "author": "greymass",
      "permlink": "announcing-our-wax-guild-candidacy",
      "voter": "dmwh",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-07-15T22:06:33",
  "trx_id": "bc4dff72f06f8060c2f4d0d55f502421982634a1",
  "trx_in_block": 1,
  "virtual_op": 0
}
2019/07/15 22:06:24
authordmwh
bodyGreymass rocks! I would definitely vote for you as a BP (Guild) but I don't plan to invest in WAX. Keep up the good work!
json metadata{"tags":["eosio"],"app":"steempeak/1.14.6"}
parent authorgreymass
parent permlinkannouncing-our-wax-guild-candidacy
permlinkre-greymass-pupeno
title
Transaction InfoBlock #34695123/Trx 03c04e06b1cc9494fccc75eb338bc12f0b0ec9bf
View Raw JSON Data
{
  "block": 34695123,
  "op": [
    "comment",
    {
      "author": "dmwh",
      "body": "Greymass rocks!  I would definitely vote for you as a BP (Guild) but I don't plan to invest in WAX.\n\nKeep up the good work!",
      "json_metadata": "{\"tags\":[\"eosio\"],\"app\":\"steempeak/1.14.6\"}",
      "parent_author": "greymass",
      "parent_permlink": "announcing-our-wax-guild-candidacy",
      "permlink": "re-greymass-pupeno",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-07-15T22:06:24",
  "trx_id": "03c04e06b1cc9494fccc75eb338bc12f0b0ec9bf",
  "trx_in_block": 38,
  "virtual_op": 0
}
2019/07/15 21:59:06
authorgreymass
permlinkannouncing-our-wax-guild-candidacy
voterzedpal
weight10000 (100.00%)
Transaction InfoBlock #34694977/Trx 0bd8b6ed6a0634f687968940c54be411fc6e14f7
View Raw JSON Data
{
  "block": 34694977,
  "op": [
    "vote",
    {
      "author": "greymass",
      "permlink": "announcing-our-wax-guild-candidacy",
      "voter": "zedpal",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-07-15T21:59:06",
  "trx_id": "0bd8b6ed6a0634f687968940c54be411fc6e14f7",
  "trx_in_block": 0,
  "virtual_op": 0
}
2019/07/15 21:22:33
allow curation rewardstrue
allow votestrue
authorgreymass
extensions[]
max accepted payout0.000 SBD
percent steem dollars10000
permlinkannouncing-our-wax-guild-candidacy
Transaction InfoBlock #34694246/Trx 12f615b11e0c920a2187d1ed494760df9f945e14
View Raw JSON Data
{
  "block": 34694246,
  "op": [
    "comment_options",
    {
      "allow_curation_rewards": true,
      "allow_votes": true,
      "author": "greymass",
      "extensions": [],
      "max_accepted_payout": "0.000 SBD",
      "percent_steem_dollars": 10000,
      "permlink": "announcing-our-wax-guild-candidacy"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-07-15T21:22:33",
  "trx_id": "12f615b11e0c920a2187d1ed494760df9f945e14",
  "trx_in_block": 13,
  "virtual_op": 0
}
2019/07/15 21:22:33
authorgreymass
body![Wax x Greymass.png](https://cdn.steemitimages.com/DQmPjHszxq7LRvAJf4fNatwBH3F9tEc3X5sPw5ZhWRARWTC/Wax%20x%20Greymass.png) ## **Intro** Greymass is an organization built to facilitate the growth of distributed ledger technologies and the infrastructure that powers them. Our work includes acting as network validators, active participation in network governance, and building of infrastructure tools and services to power the network and the applications built on top of it. Our team has experience working on a number of different blockchains and distributed systems, and we have particular expertise in EOSIO software. We’re excited to bring our suite of products and services to the WAX ecosystem. ## **Company Info:** **Website**: Greymass.com **Headquarters**: Vancouver, Canada **Candidate Name**: Team Greymass ( [teamgreymass](https://wax.bloks.io/account/teamgreymass) ) **Location of Servers**: Vancouver (CA), Michigan (USA) **Server Types**: Greymass-owned Bare Metal ## **Socials** * [Twitter](https://twitter.com/greymass) * [Telegram](https://t.me/teamgreymass) * [Github](https://github.com/greymass) * [Reddit](https://www.reddit.com/user/greymass/) * [Steem](https://steemit.com/@greymass) ## **Team** **Aaron Cox, Full Stack & Blockchain Developer** Aaron is a veteran web developer with over 20 years experience, specializing in publishing platforms, social/community engines, and data mining. Aaron has released all his efforts open-source, merged his past experiences with new Blockchain protocols, and has previously worked on developing a crowd-sourced review platform and as the lead web developer for a number of tech companies, such as NCSOFT. Aaron is incredibly fascinated by the impact Blockchain technologies will have on the Internet itself. Since devoting himself full-time to exploring this tech he has built a number of apps including wallets like Vessel, a number of block explorers, and prototypes for end users platforms such as chainBB and Reprint. Aaron is currently a top elected delegate as @jesta on the Steem, Decent, Muse, and Karma blockchains. **Scott Sallinen, Research Scientist** Scott is a Computer Engineering Ph.D. Candidate at the University of British Columbia, with research areas of High Performance Computing and Distributed Systems, Graph Processing, Machine Learning, and Blockchain technologies. Scott has published multiple peer-reviewed papers within these domains in top-tier research conferences such as Supercomputing, and has previously worked in the research divisions of Fortune 500 companies such as Intel and Facebook. Scott has a passion for the application of Blockchain technologies in the real world. He has built and led the Steemcleaners and Cheetah projects on the Steem blockchain for several years, in an effort to address and reduce fraud and phishing on the social media platform. Scott also represents a top elected delegate as @anyx on the Steem blockchain. **Daniel Fugere, Web App Developer** Daniel is an entrepreneur and software engineer who develops applications that aim to improve the lives of others. At age 19, he started his first web company, through which he developed a health service application for residents of Quebec. He has since continued creating different web applications that have the ultimate goal of making individuals more aware of the issues around them, as well as build positive relationships with people in their communities. Over the last couple of years, he has worked as a web engineer and has done back-end as well as front-end programming for projects at big companies such as Pixar, Autodesk and Riot Games. A blockchain enthusiast and avid learner of everything crypto, Daniel has been involved with Greymass since its first steps, helping develop and engineer the nitty-gritty workings of the eos-voter app (recently rebranded to Anchor). **Johan Nordberg, Software Engineer** Johan is a prolific developer with a broad range of experience and a passion for open-source — he has released a multitude of open-source projects, many of which are widely used. He founded his first company at age 23 after releasing one of the first iPhone apps in the AppStore. Besides iOS development, his specialties are security research, systems design and web development. Johan is a strong advocate for the Open Web and believes that blockchain technology has the potential to fundamentally change the world for the better. At Greymass he will be focusing on building our upcoming dApps-platform. **Myles Snider, Business Development Partner** Myles Snider is the newest addition to the team, recently joining Greymass as a partner. Myles has been involved in the EOS ecosystem since long before mainnet launch. He previously lead research at Multicoin Capital, where he published a number of EOS-focused investment reports. He also created The Stablecoin Index, a tool to track and compare various stablecoin projects.Later, he founded a mainnet block producer called Aurora EOS before eventually joining Greymass. Myles has written extensively about EOS economics and governance, and he’ll continue to do so in his new role here. He’ll also focus on interfacing with the community and helping bring more awareness to Greymass’s core product offerings. Myles also hosts an EOS-focused podcast called EOS Voter and writes a bi-weekly newsletter about the EOSIO ecosystem. **Nicholas Hamer, Visual Designer** Nicholas Hamer is a Sr Designer at Blizzard. With a diverse background in Graphic Design and a Bachelor of Fine Arts in Illustration from the Ringling College of Art and Design, he has a strong sense of composition with the ability to be versatile and think creatively. Having worked on music videos, web sites, video games advertising campaigns, feature films, and television shows, he has gained extensive experience successfully working with applied design, UX, compositing, and motion graphics through the use of programs such as Adobe Photoshop, Illustrator, After Effects, InDesign, Maya, Nuke, and Cinema 4d; A combination of skills that assist him in his ‘out of the box’ thinking and helps to provide a fresh creative perspective to any of his project. ## **Infrastructure** Our infrastructure is ever expanding and evolving, and we operate many dedicated servers to provide a variety of services. We customize all of our hardware specifically for each application to ensure the absolute best performance. To facilitate this, we have a multi-year lease with a Tier 3 data center which provides us with power redundancy, multiple independent internet connections, within a facility that is physically secured to prevent unauthorized access. Our fleet of dedicated servers is comprised of components which provide the maximum throughput for each specific task. Currently we leverage high single-core clock speed processors, high volumes of RAM, and the fastest hard drives on the market. As an example, our most recent acquisition, which is being built to serve as a full history node for the EOS Mainnet, has the following specifications: CPU: * Intel Xeon Gold 6244 (Cascade Lake Gen2, 8 cores @ 4.4 GHz) RAM: * 768 GB DDR4 ECC Storage: * 3D Xpoint (Optane) PCIE: 1.5 TB x4 * 3D Xpoint (Optane) M.2: 380 GB x3 * SATA SSD: 4 TB x4 This server will be coming online very soon to add further redundancy to the full history nodes we already operate for the EOS blockchain. ## **Scaling Infrastructure** The approach we take on scaling EOSIO based blockchains is iterative - in that we continually are researching, testing, and deploying some of the newest hardware to keep pace with the growth of each blockchain we operate. As each chain grows, our infrastructure grows with it, with older generations of hardware being recycled back into the system with new purpose. Beyond scaling hardware to meet demands, we also build custom software solutions on top of that hardware to help extend its lifespan. Utilizing various methods of data compression, caching, and actual software optimization - we are able to provide some of the fastest and most scalable solutions found anywhere within the EOSIO ecosystem. We are proud to operate some of the fastest block production nodes on any network, as well as some of the most trafficked and fastest public API services. Finally, the last piece of our infrastructure is the usage of select cloud platforms to provide a more globally distributed network. All mission critical resources are operated on our own servers within our specifically designed network, but we operate less critical services through multiple dedicated servers within the cloud. These servers ultimately rely on our data center for portions of their data, but are able to serve the majority of responses responses much faster when they are physically located closer to the end user. A significant portion of the Greymass budget is allocated to hardware and networking expenses. Within our last year of operations, we have invested around $100k (USD) into building and scaling our infrastructure. ## **Thoughts on Governance** We believe that validators on EOSIO networks have two core responsibilities— providing reliable and secure chain infrastructure, and participating in network governance. Validators (whether BPs, guilds, or other forms) serve as the elected representatives of the community, and they are tasked with guiding the evolution of the network and creating value in line with the desires of the token holders, who are the collective owners of the network. We believe that block producers should be proactive in offering leadership and opinions on important governance issues, and we also believe that they should utilize tools like referendum wherever available to more accurately gauge community sentiment. ## **Thoughts on Transparency and Accountability** As our [code of conduct](https://greymass.com/code_of_conduct) makes clear, we hold ourselves to an extremely high standard when it comes to transparency, accountability, and community trust. We believe in high levels of transparency not just in our actions within the community, but also with our products and services. All of our code is open-source, and security audits are welcome. ## Thoughts on Security The sovereignty, privacy, and security of blockchain is one of our top priorities; both in terms of the operations of the network (as a block producer) and for the end-user (in developing a wallet and APIs). The blockchain itself must be operated by professionals who understand these concepts and the impact of their own actions. The actual block production itself must be performed in an unbiased and secure manner, with proper redundancy and management of it’s security. For each network we participate in, we operate this service on physically secured servers with restricted access and the highest levels of key management. On the end-user side, we also put serious consideration into how best to secure their assets and maintain privacy. We have developed and released a secure open-source wallet for anyone to use with any EOSIO-based blockchain and continually seek ways to improve it. This wallet has specifically been designed to operate with only a single connection to the specified blockchain, using only native APIs and no external calls to help ensure privacy with its use. To that end we also operate a number of public “no-log” API servers, which anyone can use to access the network without the fear of any sort of invasion of privacy. ## **Community Benefit Projects** [Anchor Wallet](https://blog.greymass.com/eos/@greymass/the-future-of-the-greymass-wallet-beta-version-available-now) Anchor Wallet (previously called eos-voter) is an EOSIO desktop wallet that allows users to safely and easily take advantage of the full suite of features of the EOSIO software. We have integrated WAX as a native option so that WAX users are able to safely and easily do things like send and receive tokens, manage resources, participate in governance, and much more. **Native History APIs** / [Light History](https://blog.greymass.com/eos/@greymass/introducing-light-history-nodes-for-eos) At Greymass, APIs are one of our specialties. Not only are we one of the few block producers running native history APIs on the EOS mainnet, but we also developed the light history solution used by a number of other BPs today. If elected, we plan to bring both of these infrastructure solutions to the WAX blockchain. **DApp Middleware and Infrastructure** We’re currently working on a dApp middleware and infrastructure layer that will include a number of important projects. The first is our [EEP7 signing protocol](https://github.com/greymass/EEPs/blob/eep-x/EEPS/eep-7.md) , a new protocol that allows for easy communication between applications and signature providers, with the ability to request specific transaction templates. In the future, we’ll continue to work on projects that make using the blockchain more easy and secure for both developers and end users. Each of these projects will be generalizable to EOSIO and can be easily made to support WAX. More of our projects can be seen on our [Github page](https://github.com/greymass) . Thank you for your support! We look forward to being a part of the WAX ecosystem!
json metadata{"tags":["eosio","wax","greymass","bp","guild"],"users":["jesta","anyx"],"image":["https://cdn.steemitimages.com/DQmPjHszxq7LRvAJf4fNatwBH3F9tEc3X5sPw5ZhWRARWTC/Wax%20x%20Greymass.png"],"links":["https://wax.bloks.io/account/teamgreymass","https://twitter.com/greymass","https://t.me/teamgreymass","https://github.com/greymass","https://www.reddit.com/user/greymass/","https://steemit.com/@greymass","https://greymass.com/code_of_conduct","https://blog.greymass.com/eos/@greymass/the-future-of-the-greymass-wallet-beta-version-available-now","https://blog.greymass.com/eos/@greymass/introducing-light-history-nodes-for-eos","https://github.com/greymass/EEPs/blob/eep-x/EEPS/eep-7.md"],"app":"steemit/0.1","format":"markdown"}
parent author
parent permlinkeosio
permlinkannouncing-our-wax-guild-candidacy
titleAnnouncing our WAX Guild Candidacy
Transaction InfoBlock #34694246/Trx 12f615b11e0c920a2187d1ed494760df9f945e14
View Raw JSON Data
{
  "block": 34694246,
  "op": [
    "comment",
    {
      "author": "greymass",
      "body": "![Wax x Greymass.png](https://cdn.steemitimages.com/DQmPjHszxq7LRvAJf4fNatwBH3F9tEc3X5sPw5ZhWRARWTC/Wax%20x%20Greymass.png)\n\n\n## **Intro**\n\nGreymass is an organization built to facilitate the growth of distributed ledger technologies and the infrastructure that powers them. Our work includes acting as network validators, active participation in network governance, and building of infrastructure tools and services to power the network and the applications built on top of it. Our team has experience working on a number of different blockchains and distributed systems, and we have particular expertise in EOSIO software. We’re excited to bring our suite of products and services to the WAX ecosystem.\n\n## **Company Info:**\n\n**Website**: Greymass.com\n**Headquarters**: Vancouver, Canada\n**Candidate Name**: Team Greymass ( [teamgreymass](https://wax.bloks.io/account/teamgreymass) )\n**Location of Servers**: Vancouver (CA), Michigan (USA)\n**Server Types**: Greymass-owned Bare Metal\n\n## **Socials**\n\n*  [Twitter](https://twitter.com/greymass) \n*  [Telegram](https://t.me/teamgreymass) \n*  [Github](https://github.com/greymass) \n*  [Reddit](https://www.reddit.com/user/greymass/) \n*  [Steem](https://steemit.com/@greymass) \n\n\n## **Team**\n\n**Aaron Cox, Full Stack & Blockchain Developer**\n\nAaron is a veteran web developer with over 20 years experience, specializing in publishing platforms, social/community engines, and data mining. Aaron has released all his efforts open-source, merged his past experiences with new Blockchain protocols, and has previously worked on developing a crowd-sourced review platform and as the lead web developer for a number of tech companies, such as NCSOFT.\n\nAaron is incredibly fascinated by the impact Blockchain technologies will have on the Internet itself. Since devoting himself full-time to exploring this tech he has built a number of apps including wallets like Vessel, a number of block explorers, and prototypes for end users platforms such as chainBB and Reprint. Aaron is currently a top elected delegate as @jesta on the Steem, Decent, Muse, and Karma blockchains.\n\n**Scott Sallinen, Research Scientist**\n\nScott is a Computer Engineering Ph.D. Candidate at the University of British Columbia, with research areas of High Performance Computing and Distributed Systems, Graph Processing, Machine Learning, and Blockchain technologies. Scott has published multiple peer-reviewed papers within these domains in top-tier research conferences such as Supercomputing, and has previously worked in the research divisions of Fortune 500 companies such as Intel and Facebook.\n\nScott has a passion for the application of Blockchain technologies in the real world. He has built and led the Steemcleaners and Cheetah projects on the Steem blockchain for several years, in an effort to address and reduce fraud and phishing on the social media platform. Scott also represents a top elected delegate as @anyx on the Steem blockchain.\n\n**Daniel Fugere, Web App Developer**\n\nDaniel is an entrepreneur and software engineer who develops applications that aim to improve the lives of others. At age 19, he started his first web company, through which he developed a health service application for residents of Quebec. He has since continued creating different web applications that have the ultimate goal of making individuals more aware of the issues around them, as well as build positive relationships with people in their communities.\n\nOver the last couple of years, he has worked as a web engineer and has done back-end as well as front-end programming for projects at big companies such as Pixar, Autodesk and Riot Games. A blockchain enthusiast and avid learner of everything crypto, Daniel has been involved with Greymass since its first steps, helping develop and engineer the nitty-gritty workings of the eos-voter app (recently rebranded to Anchor).\n\n**Johan Nordberg, Software Engineer**\n\nJohan is a prolific developer with a broad range of experience and a passion for open-source — he has released a multitude of open-source projects, many of which are widely used. He founded his first company at age 23 after releasing one of the first iPhone apps in the AppStore. Besides iOS development, his specialties are security research, systems design and web development.\n\nJohan is a strong advocate for the Open Web and believes that blockchain technology has the potential to fundamentally change the world for the better. At Greymass he will be focusing on building our upcoming dApps-platform.\n\n**Myles Snider, Business Development Partner**\n\nMyles Snider is the newest addition to the team, recently joining Greymass as a partner. Myles has been involved in the EOS ecosystem since long before mainnet launch. He previously lead research at Multicoin Capital, where he published a number of EOS-focused investment reports. He also created The Stablecoin Index, a tool to track and compare various stablecoin projects.Later, he founded a mainnet block producer called Aurora EOS before eventually joining Greymass.\n\nMyles has written extensively about EOS economics and governance, and he’ll continue to do so in his new role here. He’ll also focus on interfacing with the community and helping bring more awareness to Greymass’s core product offerings. Myles also hosts an EOS-focused podcast called EOS Voter and writes a bi-weekly newsletter about the EOSIO ecosystem.\n\n**Nicholas Hamer, Visual Designer**\n\nNicholas Hamer is a Sr Designer at Blizzard. With a diverse background in Graphic Design and a Bachelor of Fine Arts in Illustration from the Ringling College of Art and Design, he has a strong sense of composition with the ability to be versatile and think creatively. Having worked on music videos, web sites, video games advertising campaigns, feature films, and television shows, he has gained extensive experience successfully working with applied design, UX, compositing, and motion graphics through the use of programs such as Adobe Photoshop, Illustrator, After Effects, InDesign, Maya, Nuke, and Cinema 4d; A combination of skills that assist him in his ‘out of the box’ thinking and helps to provide a fresh creative perspective to any of his project.\n\n## **Infrastructure**\n\nOur infrastructure is ever expanding and evolving, and we operate many dedicated servers to provide a variety of services. We customize all of our hardware specifically for each application to ensure the absolute best performance.\n\nTo facilitate this, we have a multi-year lease with a Tier 3 data center which provides us with power redundancy, multiple independent internet connections, within a facility that is physically secured to prevent unauthorized access.\n\nOur fleet of dedicated servers is comprised of components which provide the maximum throughput for each specific task. Currently we leverage high single-core clock speed processors, high volumes of RAM, and the fastest hard drives on the market. As an example, our most recent acquisition, which is being built to serve as a full history node for the EOS Mainnet, has the following specifications:\n\n\nCPU:\n* Intel Xeon Gold 6244 (Cascade Lake Gen2, 8 cores @ 4.4 GHz)\n\nRAM:\n* 768 GB DDR4 ECC\n\nStorage:\n* 3D Xpoint (Optane) PCIE: 1.5 TB x4\n* 3D Xpoint (Optane) M.2: 380 GB x3\n* SATA SSD: 4 TB x4\n\n\nThis server will be coming online very soon to add further redundancy to the full history nodes we already operate for the EOS blockchain.\n\n## **Scaling Infrastructure**\n\nThe approach we take on scaling EOSIO based blockchains is iterative - in that we continually are researching, testing, and deploying some of the newest hardware to keep pace with the growth of each blockchain we operate. As each chain grows, our infrastructure grows with it, with older generations of hardware being recycled back into the system with new purpose.\n\nBeyond scaling hardware to meet demands, we also build custom software solutions on top of that hardware to help extend its lifespan. Utilizing various methods of data compression, caching, and actual software optimization - we are able to provide some of the fastest and most scalable solutions found anywhere within the EOSIO ecosystem. We are proud to operate some of the fastest block production nodes on any network, as well as some of the most trafficked and fastest public API services.\n\nFinally, the last piece of our infrastructure is the usage of select cloud platforms to provide a more globally distributed network. All mission critical resources are operated on our own servers within our specifically designed network, but we operate less critical services through multiple dedicated servers within the cloud. These servers ultimately rely on our data center for portions of their data, but are able to serve the majority of responses responses much faster when they are physically located closer to the end user.\n\nA significant portion of the Greymass budget is allocated to hardware and networking expenses. Within our last year of operations, we have invested around $100k (USD) into building and scaling our infrastructure.\n\n## **Thoughts on Governance**\n\nWe believe that validators on EOSIO networks have two core responsibilities— providing reliable and secure chain infrastructure, and participating in network governance. Validators (whether BPs, guilds, or other forms) serve as the elected representatives of the community, and they are tasked with guiding the evolution of the network and creating value in line with the desires of the token holders, who are the collective owners of the network. We believe that block producers should be proactive in offering leadership and opinions on important governance issues, and we also believe that they should utilize tools like referendum wherever available to more accurately gauge community sentiment.\n\n## **Thoughts on Transparency and Accountability**\n\nAs our  [code of conduct](https://greymass.com/code_of_conduct)  makes clear, we hold ourselves to an extremely high standard when it comes to transparency, accountability, and community trust. We believe in high levels of transparency not just in our actions within the community, but also with our products and services. All of our code is open-source, and security audits are welcome.\n\n## Thoughts on Security \n\nThe sovereignty, privacy, and security of blockchain is one of our top priorities; both in terms of the operations of the network (as a block producer) and for the end-user (in developing a wallet and APIs).\n\nThe blockchain itself must be operated by professionals who understand these concepts and the impact of their own actions. The actual block production itself must be performed in an unbiased and secure manner, with proper redundancy and management of it’s security. For each network we participate in, we operate this service on physically secured servers with restricted access and the highest levels of key management.\n\nOn the end-user side, we also put serious consideration into how best to secure their assets and maintain privacy. We have developed and released a secure open-source wallet for anyone to use with any EOSIO-based blockchain and continually seek ways to improve it. This wallet has specifically been designed to operate with only a single connection to the specified blockchain, using only native APIs and no external calls to help ensure privacy with its use. To that end we also operate a number of public “no-log” API servers, which anyone can use to access the network without the fear of any sort of invasion of privacy.\n\n\n## **Community Benefit Projects**\n\n\n[Anchor Wallet](https://blog.greymass.com/eos/@greymass/the-future-of-the-greymass-wallet-beta-version-available-now)\n\nAnchor Wallet (previously called eos-voter) is an EOSIO desktop wallet that allows users to safely and easily take advantage of the full suite of features of the EOSIO software. We have integrated WAX as a native option so that WAX users are able to safely and easily do things like send and receive tokens, manage resources, participate in governance, and much more.\n\n**Native History APIs** /  [Light History](https://blog.greymass.com/eos/@greymass/introducing-light-history-nodes-for-eos) \n\nAt Greymass, APIs are one of our specialties. Not only are we one of the few block producers running native history APIs on the EOS mainnet, but we also developed the light history solution used by a number of other BPs today. If elected, we plan to bring both of these infrastructure solutions to the WAX blockchain.\n\n**DApp Middleware and Infrastructure**\n\nWe’re currently working on a dApp middleware and infrastructure layer that will include a number of important projects. The first is our  [EEP7 signing protocol](https://github.com/greymass/EEPs/blob/eep-x/EEPS/eep-7.md) , a new protocol that allows for easy communication between applications and signature providers, with the ability to request specific transaction templates. In the future, we’ll continue to work on projects that make using the blockchain more easy and secure for both developers and end users. Each of these projects will be generalizable to EOSIO and can be easily made to support WAX.\n\nMore of our projects can be seen on our  [Github page](https://github.com/greymass) .\n\nThank you for your support! We look forward to being a part of the WAX ecosystem!",
      "json_metadata": "{\"tags\":[\"eosio\",\"wax\",\"greymass\",\"bp\",\"guild\"],\"users\":[\"jesta\",\"anyx\"],\"image\":[\"https://cdn.steemitimages.com/DQmPjHszxq7LRvAJf4fNatwBH3F9tEc3X5sPw5ZhWRARWTC/Wax%20x%20Greymass.png\"],\"links\":[\"https://wax.bloks.io/account/teamgreymass\",\"https://twitter.com/greymass\",\"https://t.me/teamgreymass\",\"https://github.com/greymass\",\"https://www.reddit.com/user/greymass/\",\"https://steemit.com/@greymass\",\"https://greymass.com/code_of_conduct\",\"https://blog.greymass.com/eos/@greymass/the-future-of-the-greymass-wallet-beta-version-available-now\",\"https://blog.greymass.com/eos/@greymass/introducing-light-history-nodes-for-eos\",\"https://github.com/greymass/EEPs/blob/eep-x/EEPS/eep-7.md\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
      "parent_author": "",
      "parent_permlink": "eosio",
      "permlink": "announcing-our-wax-guild-candidacy",
      "title": "Announcing our WAX Guild Candidacy"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-07-15T21:22:33",
  "trx_id": "12f615b11e0c920a2187d1ed494760df9f945e14",
  "trx_in_block": 13,
  "virtual_op": 0
}
greymassdeleted a comment or post
2019/07/15 21:12:21
authorgreymass
permlinkannouncing-our-wax-guild-candidacy
Transaction InfoBlock #34694042/Trx e1c8729eaab93a98947ae8425878b338de87a00f
View Raw JSON Data
{
  "block": 34694042,
  "op": [
    "delete_comment",
    {
      "author": "greymass",
      "permlink": "announcing-our-wax-guild-candidacy"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-07-15T21:12:21",
  "trx_id": "e1c8729eaab93a98947ae8425878b338de87a00f",
  "trx_in_block": 11,
  "virtual_op": 0
}
2019/07/15 21:11:30
authorgreymass
body![Wax x Greymass.png](https://cdn.steemitimages.com/DQmPjHszxq7LRvAJf4fNatwBH3F9tEc3X5sPw5ZhWRARWTC/Wax%20x%20Greymass.png) ## **Intro** Greymass is an organization built to facilitate the growth of distributed ledger technologies and the infrastructure that powers them. Our work includes acting as network validators, active participation in network governance, and building of infrastructure tools and services to power the network and the applications built on top of it. Our team has experience working on a number of different blockchains and distributed systems, and we have particular expertise in EOSIO software. We’re excited to bring our suite of products and services to the WAX ecosystem. ## **Company Info:** **Website**: Greymass.com **Headquarters**: Vancouver, Canada **Candidate Name**: Team Greymass ( [teamgreymass](https://wax.bloks.io/account/teamgreymass) ) **Location of Servers**: Vancouver (CA), Michigan (USA) **Server Types**: Greymass-owned Bare Metal ## **Socials** * [Twitter](https://twitter.com/greymass) * [Telegram](https://t.me/teamgreymass) * [Github](https://github.com/greymass) * [Reddit](https://www.reddit.com/user/greymass/) * [Steem](https://steemit.com/@greymass) ## **Team** **Aaron Cox, Full Stack & Blockchain Developer** Aaron is a veteran web developer with over 20 years experience, specializing in publishing platforms, social/community engines, and data mining. Aaron has released all his efforts open-source, merged his past experiences with new Blockchain protocols, and has previously worked on developing a crowd-sourced review platform and as the lead web developer for a number of tech companies, such as NCSOFT. Aaron is incredibly fascinated by the impact Blockchain technologies will have on the Internet itself. Since devoting himself full-time to exploring this tech he has built a number of apps including wallets like Vessel, a number of block explorers, and prototypes for end users platforms such as chainBB and Reprint. Aaron is currently a top elected delegate as @jesta on the Steem, Decent, Muse, and Karma blockchains. **Scott Sallinen, Research Scientist** Scott is a Computer Engineering Ph.D. Candidate at the University of British Columbia, with research areas of High Performance Computing and Distributed Systems, Graph Processing, Machine Learning, and Blockchain technologies. Scott has published multiple peer-reviewed papers within these domains in top-tier research conferences such as Supercomputing, and has previously worked in the research divisions of Fortune 500 companies such as Intel and Facebook. Scott has a passion for the application of Blockchain technologies in the real world. He has built and led the Steemcleaners and Cheetah projects on the Steem blockchain for several years, in an effort to address and reduce fraud and phishing on the social media platform. Scott also represents a top elected delegate as @anyx on the Steem blockchain. **Daniel Fugere, Web App Developer** Daniel is an entrepreneur and software engineer who develops applications that aim to improve the lives of others. At age 19, he started his first web company, through which he developed a health service application for residents of Quebec. He has since continued creating different web applications that have the ultimate goal of making individuals more aware of the issues around them, as well as build positive relationships with people in their communities. Over the last couple of years, he has worked as a web engineer and has done back-end as well as front-end programming for projects at big companies such as Pixar, Autodesk and Riot Games. A blockchain enthusiast and avid learner of everything crypto, Daniel has been involved with Greymass since its first steps, helping develop and engineer the nitty-gritty workings of the eos-voter app (recently rebranded to Anchor). **Johan Nordberg, Software Engineer** Johan is a prolific developer with a broad range of experience and a passion for open-source — he has released a multitude of open-source projects, many of which are widely used. He founded his first company at age 23 after releasing one of the first iPhone apps in the AppStore. Besides iOS development, his specialties are security research, systems design and web development. Johan is a strong advocate for the Open Web and believes that blockchain technology has the potential to fundamentally change the world for the better. At Greymass he will be focusing on building our upcoming dApps-platform. **Myles Snider, Business Development Partner** Myles Snider is the newest addition to the team, recently joining Greymass as a partner. Myles has been involved in the EOS ecosystem since long before mainnet launch. He previously lead research at Multicoin Capital, where he published a number of EOS-focused investment reports. He also created The Stablecoin Index, a tool to track and compare various stablecoin projects.Later, he founded a mainnet block producer called Aurora EOS before eventually joining Greymass. Myles has written extensively about EOS economics and governance, and he’ll continue to do so in his new role here. He’ll also focus on interfacing with the community and helping bring more awareness to Greymass’s core product offerings. Myles also hosts an EOS-focused podcast called EOS Voter and writes a bi-weekly newsletter about the EOSIO ecosystem. **Nicholas Hamer, Visual Designer** Nicholas Hamer is a Sr Designer at Blizzard. With a diverse background in Graphic Design and a Bachelor of Fine Arts in Illustration from the Ringling College of Art and Design, he has a strong sense of composition with the ability to be versatile and think creatively. Having worked on music videos, web sites, video games advertising campaigns, feature films, and television shows, he has gained extensive experience successfully working with applied design, UX, compositing, and motion graphics through the use of programs such as Adobe Photoshop, Illustrator, After Effects, InDesign, Maya, Nuke, and Cinema 4d; A combination of skills that assist him in his ‘out of the box’ thinking and helps to provide a fresh creative perspective to any of his project. ## **Infrastructure** Our infrastructure is ever expanding and evolving, and we operate many dedicated servers to provide a variety of services. We customize all of our hardware specifically for each application to ensure the absolute best performance. To facilitate this, we have a multi-year lease with a Tier 3 data center which provides us with power redundancy, multiple independent internet connections, within a facility that is physically secured to prevent unauthorized access. Our fleet of dedicated servers is comprised of components which provide the maximum throughput for each specific task. Currently we leverage high single-core clock speed processors, high volumes of RAM, and the fastest hard drives on the market. As an example, our most recent acquisition, which is being built to serve as a full history node for the EOS Mainnet, has the following specifications: CPU: * Intel Xeon Gold 6244 (Cascade Lake Gen2, 8 cores @ 4.4 GHz) RAM: * 768 GB DDR4 ECC Storage: * 3D Xpoint (Optane) PCIE: 1.5 TB x4 * 3D Xpoint (Optane) M.2: 380 GB x3 * SATA SSD: 4 TB x4 This server will be coming online very soon to add further redundancy to the full history nodes we already operate for the EOS blockchain. ## **Scaling Infrastructure** The approach we take on scaling EOSIO based blockchains is iterative - in that we continually are researching, testing, and deploying some of the newest hardware to keep pace with the growth of each blockchain we operate. As each chain grows, our infrastructure grows with it, with older generations of hardware being recycled back into the system with new purpose. Beyond scaling hardware to meet demands, we also build custom software solutions on top of that hardware to help extend its lifespan. Utilizing various methods of data compression, caching, and actual software optimization - we are able to provide some of the fastest and most scalable solutions found anywhere within the EOSIO ecosystem. We are proud to operate some of the fastest block production nodes on any network, as well as some of the most trafficked and fastest public API services. Finally, the last piece of our infrastructure is the usage of select cloud platforms to provide a more globally distributed network. All mission critical resources are operated on our own servers within our specifically designed network, but we operate less critical services through multiple dedicated servers within the cloud. These servers ultimately rely on our data center for portions of their data, but are able to serve the majority of responses responses much faster when they are physically located closer to the end user. A significant portion of the Greymass budget is allocated to hardware and networking expenses. Within our last year of operations, we have invested around $100k (USD) into building and scaling our infrastructure. ## **Thoughts on Governance** We believe that validators on EOSIO networks have two core responsibilities— providing reliable and secure chain infrastructure, and participating in network governance. Validators (whether BPs, guilds, or other forms) serve as the elected representatives of the community, and they are tasked with guiding the evolution of the network and creating value in line with the desires of the token holders, who are the collective owners of the network. We believe that block producers should be proactive in offering leadership and opinions on important governance issues, and we also believe that they should utilize tools like referendum wherever available to more accurately gauge community sentiment. ## **Thoughts on Transparency and Accountability** As our [code of conduct](https://greymass.com/code_of_conduct) makes clear, we hold ourselves to an extremely high standard when it comes to transparency, accountability, and community trust. We believe in high levels of transparency not just in our actions within the community, but also with our products and services. All of our code is open-source, and security audits are welcome. ## Thoughts on Security The sovereignty, privacy, and security of blockchain is one of our top priorities; both in terms of the operations of the network (as a block producer) and for the end-user (in developing a wallet and APIs). The blockchain itself must be operated by professionals who understand these concepts and the impact of their own actions. The actual block production itself must be performed in an unbiased and secure manner, with proper redundancy and management of it’s security. For each network we participate in, we operate this service on physically secured servers with restricted access and the highest levels of key management. On the end-user side, we also put serious consideration into how best to secure their assets and maintain privacy. We have developed and released a secure open-source wallet for anyone to use with any EOSIO-based blockchain and continually seek ways to improve it. This wallet has specifically been designed to operate with only a single connection to the specified blockchain, using only native APIs and no external calls to help ensure privacy with its use. To that end we also operate a number of public “no-log” API servers, which anyone can use to access the network without the fear of any sort of invasion of privacy. ## **Community Benefit Projects** [Anchor Wallet](https://blog.greymass.com/eos/@greymass/the-future-of-the-greymass-wallet-beta-version-available-now) Anchor Wallet (previously called eos-voter) is an EOSIO desktop wallet that allows users to safely and easily take advantage of the full suite of features of the EOSIO software. We have integrated WAX as a native option so that WAX users are able to safely and easily do things like send and receive tokens, manage resources, participate in governance, and much more. **Native History APIs** / [Light History](https://blog.greymass.com/eos/@greymass/introducing-light-history-nodes-for-eos) At Greymass, APIs are one of our specialties. Not only are we one of the few block producers running native history APIs on the EOS mainnet, but we also developed the light history solution used by a number of other BPs today. If elected, we plan to bring both of these infrastructure solutions to the WAX blockchain. **DApp Middleware and Infrastructure** We’re currently working on a dApp middleware and infrastructure layer that will include a number of important projects. The first is our [EEP7 signing protocol](https://github.com/greymass/EEPs/blob/eep-x/EEPS/eep-7.md) , a new protocol that allows for easy communication between applications and signature providers, with the ability to request specific transaction templates. In the future, we’ll continue to work on projects that make using the blockchain more easy and secure for both developers and end users. Each of these projects will be generalizable to EOSIO and can be easily made to support WAX. More of our projects can be seen on our [Github page](https://github.com/greymass) . Thank you for your support! We look forward to being a part of the WAX ecosystem!
json metadata{"tags":["greymass","wax","eosio","guild","bp"],"users":["jesta","anyx"],"image":["https://cdn.steemitimages.com/DQmPjHszxq7LRvAJf4fNatwBH3F9tEc3X5sPw5ZhWRARWTC/Wax%20x%20Greymass.png"],"links":["https://wax.bloks.io/account/teamgreymass","https://twitter.com/greymass","https://t.me/teamgreymass","https://github.com/greymass","https://www.reddit.com/user/greymass/","https://steemit.com/@greymass","https://greymass.com/code_of_conduct","https://blog.greymass.com/eos/@greymass/the-future-of-the-greymass-wallet-beta-version-available-now","https://blog.greymass.com/eos/@greymass/introducing-light-history-nodes-for-eos","https://github.com/greymass/EEPs/blob/eep-x/EEPS/eep-7.md"],"app":"steemit/0.1","format":"markdown"}
parent author
parent permlinkgreymass
permlinkannouncing-our-wax-guild-candidacy
titleAnnouncing our WAX Guild Candidacy
Transaction InfoBlock #34694025/Trx 1cfba6c318ad2f6477e25016e3ce1666a44a5887
View Raw JSON Data
{
  "block": 34694025,
  "op": [
    "comment",
    {
      "author": "greymass",
      "body": "![Wax x Greymass.png](https://cdn.steemitimages.com/DQmPjHszxq7LRvAJf4fNatwBH3F9tEc3X5sPw5ZhWRARWTC/Wax%20x%20Greymass.png)\n\n\n## **Intro**\n\nGreymass is an organization built to facilitate the growth of distributed ledger technologies and the infrastructure that powers them. Our work includes acting as network validators, active participation in network governance, and building of infrastructure tools and services to power the network and the applications built on top of it. Our team has experience working on a number of different blockchains and distributed systems, and we have particular expertise in EOSIO software. We’re excited to bring our suite of products and services to the WAX ecosystem.\n\n## **Company Info:**\n\n**Website**: Greymass.com\n**Headquarters**: Vancouver, Canada\n**Candidate Name**: Team Greymass ( [teamgreymass](https://wax.bloks.io/account/teamgreymass) )\n**Location of Servers**: Vancouver (CA), Michigan (USA)\n**Server Types**: Greymass-owned Bare Metal\n\n## **Socials**\n\n*  [Twitter](https://twitter.com/greymass) \n*  [Telegram](https://t.me/teamgreymass) \n*  [Github](https://github.com/greymass) \n*  [Reddit](https://www.reddit.com/user/greymass/) \n*  [Steem](https://steemit.com/@greymass) \n\n\n## **Team**\n\n**Aaron Cox, Full Stack & Blockchain Developer**\n\nAaron is a veteran web developer with over 20 years experience, specializing in publishing platforms, social/community engines, and data mining. Aaron has released all his efforts open-source, merged his past experiences with new Blockchain protocols, and has previously worked on developing a crowd-sourced review platform and as the lead web developer for a number of tech companies, such as NCSOFT.\n\nAaron is incredibly fascinated by the impact Blockchain technologies will have on the Internet itself. Since devoting himself full-time to exploring this tech he has built a number of apps including wallets like Vessel, a number of block explorers, and prototypes for end users platforms such as chainBB and Reprint. Aaron is currently a top elected delegate as @jesta on the Steem, Decent, Muse, and Karma blockchains.\n\n**Scott Sallinen, Research Scientist**\n\nScott is a Computer Engineering Ph.D. Candidate at the University of British Columbia, with research areas of High Performance Computing and Distributed Systems, Graph Processing, Machine Learning, and Blockchain technologies. Scott has published multiple peer-reviewed papers within these domains in top-tier research conferences such as Supercomputing, and has previously worked in the research divisions of Fortune 500 companies such as Intel and Facebook.\n\nScott has a passion for the application of Blockchain technologies in the real world. He has built and led the Steemcleaners and Cheetah projects on the Steem blockchain for several years, in an effort to address and reduce fraud and phishing on the social media platform. Scott also represents a top elected delegate as @anyx on the Steem blockchain.\n\n**Daniel Fugere, Web App Developer**\n\nDaniel is an entrepreneur and software engineer who develops applications that aim to improve the lives of others. At age 19, he started his first web company, through which he developed a health service application for residents of Quebec. He has since continued creating different web applications that have the ultimate goal of making individuals more aware of the issues around them, as well as build positive relationships with people in their communities.\n\nOver the last couple of years, he has worked as a web engineer and has done back-end as well as front-end programming for projects at big companies such as Pixar, Autodesk and Riot Games. A blockchain enthusiast and avid learner of everything crypto, Daniel has been involved with Greymass since its first steps, helping develop and engineer the nitty-gritty workings of the eos-voter app (recently rebranded to Anchor).\n\n**Johan Nordberg, Software Engineer**\n\nJohan is a prolific developer with a broad range of experience and a passion for open-source — he has released a multitude of open-source projects, many of which are widely used. He founded his first company at age 23 after releasing one of the first iPhone apps in the AppStore. Besides iOS development, his specialties are security research, systems design and web development.\n\nJohan is a strong advocate for the Open Web and believes that blockchain technology has the potential to fundamentally change the world for the better. At Greymass he will be focusing on building our upcoming dApps-platform.\n\n**Myles Snider, Business Development Partner**\n\nMyles Snider is the newest addition to the team, recently joining Greymass as a partner. Myles has been involved in the EOS ecosystem since long before mainnet launch. He previously lead research at Multicoin Capital, where he published a number of EOS-focused investment reports. He also created The Stablecoin Index, a tool to track and compare various stablecoin projects.Later, he founded a mainnet block producer called Aurora EOS before eventually joining Greymass.\n\nMyles has written extensively about EOS economics and governance, and he’ll continue to do so in his new role here. He’ll also focus on interfacing with the community and helping bring more awareness to Greymass’s core product offerings. Myles also hosts an EOS-focused podcast called EOS Voter and writes a bi-weekly newsletter about the EOSIO ecosystem.\n\n**Nicholas Hamer, Visual Designer**\n\nNicholas Hamer is a Sr Designer at Blizzard. With a diverse background in Graphic Design and a Bachelor of Fine Arts in Illustration from the Ringling College of Art and Design, he has a strong sense of composition with the ability to be versatile and think creatively. Having worked on music videos, web sites, video games advertising campaigns, feature films, and television shows, he has gained extensive experience successfully working with applied design, UX, compositing, and motion graphics through the use of programs such as Adobe Photoshop, Illustrator, After Effects, InDesign, Maya, Nuke, and Cinema 4d; A combination of skills that assist him in his ‘out of the box’ thinking and helps to provide a fresh creative perspective to any of his project.\n\n## **Infrastructure**\n\nOur infrastructure is ever expanding and evolving, and we operate many dedicated servers to provide a variety of services. We customize all of our hardware specifically for each application to ensure the absolute best performance.\n\nTo facilitate this, we have a multi-year lease with a Tier 3 data center which provides us with power redundancy, multiple independent internet connections, within a facility that is physically secured to prevent unauthorized access.\n\nOur fleet of dedicated servers is comprised of components which provide the maximum throughput for each specific task. Currently we leverage high single-core clock speed processors, high volumes of RAM, and the fastest hard drives on the market. As an example, our most recent acquisition, which is being built to serve as a full history node for the EOS Mainnet, has the following specifications:\n\n\nCPU:\n* Intel Xeon Gold 6244 (Cascade Lake Gen2, 8 cores @ 4.4 GHz)\n\nRAM:\n* 768 GB DDR4 ECC\n\nStorage:\n* 3D Xpoint (Optane) PCIE: 1.5 TB x4\n* 3D Xpoint (Optane) M.2: 380 GB x3\n* SATA SSD: 4 TB x4\n\n\nThis server will be coming online very soon to add further redundancy to the full history nodes we already operate for the EOS blockchain.\n\n## **Scaling Infrastructure**\n\nThe approach we take on scaling EOSIO based blockchains is iterative - in that we continually are researching, testing, and deploying some of the newest hardware to keep pace with the growth of each blockchain we operate. As each chain grows, our infrastructure grows with it, with older generations of hardware being recycled back into the system with new purpose.\n\nBeyond scaling hardware to meet demands, we also build custom software solutions on top of that hardware to help extend its lifespan. Utilizing various methods of data compression, caching, and actual software optimization - we are able to provide some of the fastest and most scalable solutions found anywhere within the EOSIO ecosystem. We are proud to operate some of the fastest block production nodes on any network, as well as some of the most trafficked and fastest public API services.\n\nFinally, the last piece of our infrastructure is the usage of select cloud platforms to provide a more globally distributed network. All mission critical resources are operated on our own servers within our specifically designed network, but we operate less critical services through multiple dedicated servers within the cloud. These servers ultimately rely on our data center for portions of their data, but are able to serve the majority of responses responses much faster when they are physically located closer to the end user.\n\nA significant portion of the Greymass budget is allocated to hardware and networking expenses. Within our last year of operations, we have invested around $100k (USD) into building and scaling our infrastructure.\n\n## **Thoughts on Governance**\n\nWe believe that validators on EOSIO networks have two core responsibilities— providing reliable and secure chain infrastructure, and participating in network governance. Validators (whether BPs, guilds, or other forms) serve as the elected representatives of the community, and they are tasked with guiding the evolution of the network and creating value in line with the desires of the token holders, who are the collective owners of the network. We believe that block producers should be proactive in offering leadership and opinions on important governance issues, and we also believe that they should utilize tools like referendum wherever available to more accurately gauge community sentiment.\n\n## **Thoughts on Transparency and Accountability**\n\nAs our  [code of conduct](https://greymass.com/code_of_conduct)  makes clear, we hold ourselves to an extremely high standard when it comes to transparency, accountability, and community trust. We believe in high levels of transparency not just in our actions within the community, but also with our products and services. All of our code is open-source, and security audits are welcome.\n\n## Thoughts on Security \n\nThe sovereignty, privacy, and security of blockchain is one of our top priorities; both in terms of the operations of the network (as a block producer) and for the end-user (in developing a wallet and APIs).\n\nThe blockchain itself must be operated by professionals who understand these concepts and the impact of their own actions. The actual block production itself must be performed in an unbiased and secure manner, with proper redundancy and management of it’s security. For each network we participate in, we operate this service on physically secured servers with restricted access and the highest levels of key management.\n\nOn the end-user side, we also put serious consideration into how best to secure their assets and maintain privacy. We have developed and released a secure open-source wallet for anyone to use with any EOSIO-based blockchain and continually seek ways to improve it. This wallet has specifically been designed to operate with only a single connection to the specified blockchain, using only native APIs and no external calls to help ensure privacy with its use. To that end we also operate a number of public “no-log” API servers, which anyone can use to access the network without the fear of any sort of invasion of privacy.\n\n\n## **Community Benefit Projects**\n\n\n[Anchor Wallet](https://blog.greymass.com/eos/@greymass/the-future-of-the-greymass-wallet-beta-version-available-now)\n\nAnchor Wallet (previously called eos-voter) is an EOSIO desktop wallet that allows users to safely and easily take advantage of the full suite of features of the EOSIO software. We have integrated WAX as a native option so that WAX users are able to safely and easily do things like send and receive tokens, manage resources, participate in governance, and much more.\n\n**Native History APIs** /  [Light History](https://blog.greymass.com/eos/@greymass/introducing-light-history-nodes-for-eos) \n\nAt Greymass, APIs are one of our specialties. Not only are we one of the few block producers running native history APIs on the EOS mainnet, but we also developed the light history solution used by a number of other BPs today. If elected, we plan to bring both of these infrastructure solutions to the WAX blockchain.\n\n**DApp Middleware and Infrastructure**\n\nWe’re currently working on a dApp middleware and infrastructure layer that will include a number of important projects. The first is our  [EEP7 signing protocol](https://github.com/greymass/EEPs/blob/eep-x/EEPS/eep-7.md) , a new protocol that allows for easy communication between applications and signature providers, with the ability to request specific transaction templates. In the future, we’ll continue to work on projects that make using the blockchain more easy and secure for both developers and end users. Each of these projects will be generalizable to EOSIO and can be easily made to support WAX.\n\nMore of our projects can be seen on our  [Github page](https://github.com/greymass) .\n\nThank you for your support! We look forward to being a part of the WAX ecosystem!",
      "json_metadata": "{\"tags\":[\"greymass\",\"wax\",\"eosio\",\"guild\",\"bp\"],\"users\":[\"jesta\",\"anyx\"],\"image\":[\"https://cdn.steemitimages.com/DQmPjHszxq7LRvAJf4fNatwBH3F9tEc3X5sPw5ZhWRARWTC/Wax%20x%20Greymass.png\"],\"links\":[\"https://wax.bloks.io/account/teamgreymass\",\"https://twitter.com/greymass\",\"https://t.me/teamgreymass\",\"https://github.com/greymass\",\"https://www.reddit.com/user/greymass/\",\"https://steemit.com/@greymass\",\"https://greymass.com/code_of_conduct\",\"https://blog.greymass.com/eos/@greymass/the-future-of-the-greymass-wallet-beta-version-available-now\",\"https://blog.greymass.com/eos/@greymass/introducing-light-history-nodes-for-eos\",\"https://github.com/greymass/EEPs/blob/eep-x/EEPS/eep-7.md\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
      "parent_author": "",
      "parent_permlink": "greymass",
      "permlink": "announcing-our-wax-guild-candidacy",
      "title": "Announcing our WAX Guild Candidacy"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-07-15T21:11:30",
  "trx_id": "1cfba6c318ad2f6477e25016e3ce1666a44a5887",
  "trx_in_block": 38,
  "virtual_op": 0
}
2019/07/10 07:22:06
authorgreymass
permlinkconverting-an-eos-account-to-use-a-ledger-with-eos-voter-0-6-x-greymass-wallet
voterflowingman
weight10000 (100.00%)
Transaction InfoBlock #34533607/Trx e227f9e29a4f6fe63b1c1da13f17aa5c00520177
View Raw JSON Data
{
  "block": 34533607,
  "op": [
    "vote",
    {
      "author": "greymass",
      "permlink": "converting-an-eos-account-to-use-a-ledger-with-eos-voter-0-6-x-greymass-wallet",
      "voter": "flowingman",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-07-10T07:22:06",
  "trx_id": "e227f9e29a4f6fe63b1c1da13f17aa5c00520177",
  "trx_in_block": 34,
  "virtual_op": 0
}
2019/07/10 07:22:00
authorflowingman
bodySuper article - thank you! If I want to do the reverse and move the account name to a hot wallet - assume I create new key pair then change permissions for that account to the new public key?
json metadata{"tags":["eos"],"app":"steemit/0.1"}
parent authorgreymass
parent permlinkconverting-an-eos-account-to-use-a-ledger-with-eos-voter-0-6-x-greymass-wallet
permlinkpuf0go
title
Transaction InfoBlock #34533605/Trx ee7326bb05c05f3aa9a4bf30bfee77127bb941fd
View Raw JSON Data
{
  "block": 34533605,
  "op": [
    "comment",
    {
      "author": "flowingman",
      "body": "Super article - thank you!\nIf I want to do the reverse and move the account name to a hot wallet - assume I create new key pair then change permissions for that account to the new public key?",
      "json_metadata": "{\"tags\":[\"eos\"],\"app\":\"steemit/0.1\"}",
      "parent_author": "greymass",
      "parent_permlink": "converting-an-eos-account-to-use-a-ledger-with-eos-voter-0-6-x-greymass-wallet",
      "permlink": "puf0go",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-07-10T07:22:00",
  "trx_id": "ee7326bb05c05f3aa9a4bf30bfee77127bb941fd",
  "trx_in_block": 35,
  "virtual_op": 0
}
2019/06/02 17:35:30
authorgreymass
permlinkgreymass-team-update-first-half-of-2019
votermaxocoin
weight10000 (100.00%)
Transaction InfoBlock #33453037/Trx 61dc3e5f5bb7a65c423328ae34a0c3814e77b86e
View Raw JSON Data
{
  "block": 33453037,
  "op": [
    "vote",
    {
      "author": "greymass",
      "permlink": "greymass-team-update-first-half-of-2019",
      "voter": "maxocoin",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-06-02T17:35:30",
  "trx_id": "61dc3e5f5bb7a65c423328ae34a0c3814e77b86e",
  "trx_in_block": 5,
  "virtual_op": 0
}
2019/05/31 00:56:21
authorgreymass
permlinkgreymass-team-update-first-half-of-2019
voterpnc
weight10000 (100.00%)
Transaction InfoBlock #33375536/Trx b5e9585ca585f827fa9c041f874340a13976f43c
View Raw JSON Data
{
  "block": 33375536,
  "op": [
    "vote",
    {
      "author": "greymass",
      "permlink": "greymass-team-update-first-half-of-2019",
      "voter": "pnc",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-05-31T00:56:21",
  "trx_id": "b5e9585ca585f827fa9c041f874340a13976f43c",
  "trx_in_block": 15,
  "virtual_op": 0
}
2019/05/30 17:54:24
authorgreymass
permlinkgreymass-team-update-first-half-of-2019
voterjesta
weight10000 (100.00%)
Transaction InfoBlock #33367107/Trx a0c6168496b1e0a9051d0cf05697c8ac1901382a
View Raw JSON Data
{
  "block": 33367107,
  "op": [
    "vote",
    {
      "author": "greymass",
      "permlink": "greymass-team-update-first-half-of-2019",
      "voter": "jesta",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-05-30T17:54:24",
  "trx_id": "a0c6168496b1e0a9051d0cf05697c8ac1901382a",
  "trx_in_block": 9,
  "virtual_op": 0
}
2019/05/30 17:18:18
authorgreymass
permlinkgreymass-team-update-first-half-of-2019
voterpinoy
weight1000 (10.00%)
Transaction InfoBlock #33366386/Trx f2f2873f813859888f6e351c9920bf4c121c4827
View Raw JSON Data
{
  "block": 33366386,
  "op": [
    "vote",
    {
      "author": "greymass",
      "permlink": "greymass-team-update-first-half-of-2019",
      "voter": "pinoy",
      "weight": 1000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-05-30T17:18:18",
  "trx_id": "f2f2873f813859888f6e351c9920bf4c121c4827",
  "trx_in_block": 4,
  "virtual_op": 0
}
2019/05/30 17:03:03
authorgreymass
permlinkgreymass-team-update-first-half-of-2019
voteryehey
weight1000 (10.00%)
Transaction InfoBlock #33366081/Trx 2880bc2bbbcc188fb03ecd69996a12f133d1dbc2
View Raw JSON Data
{
  "block": 33366081,
  "op": [
    "vote",
    {
      "author": "greymass",
      "permlink": "greymass-team-update-first-half-of-2019",
      "voter": "yehey",
      "weight": 1000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-05-30T17:03:03",
  "trx_id": "2880bc2bbbcc188fb03ecd69996a12f133d1dbc2",
  "trx_in_block": 0,
  "virtual_op": 0
}
2019/05/30 16:58:51
authorgreymass
permlinkgreymass-team-update-first-half-of-2019
voterzedpal
weight10000 (100.00%)
Transaction InfoBlock #33365997/Trx 5f8e07f69d42a7dbbfa57adadbc7c0dce3dfa85c
View Raw JSON Data
{
  "block": 33365997,
  "op": [
    "vote",
    {
      "author": "greymass",
      "permlink": "greymass-team-update-first-half-of-2019",
      "voter": "zedpal",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-05-30T16:58:51",
  "trx_id": "5f8e07f69d42a7dbbfa57adadbc7c0dce3dfa85c",
  "trx_in_block": 24,
  "virtual_op": 0
}
2019/05/30 16:51:48
authorgreymass
body@@ -210,16 +210,17 @@ *really* + awesome @@ -367,24 +367,24 @@ progress. %0A - %0AWe continue @@ -8622,16 +8622,17 @@ e *many* + new tool @@ -16979,17 +16979,18 @@ O chains -, + %E2%80%94 plus th @@ -17030,25 +17030,26 @@ blockchains -, + %E2%80%94 and we%E2%80%99ll c
json metadata{"tags":["eos","greymass","bp","update","mainnet"],"image":["https://cdn.steemitimages.com/DQmdHGd58epVm1og1dQS3kdTVYT57tEHE8Qt9AzYDsdXfYg/Anchor1.png","https://cdn.steemitimages.com/DQmaR9SS3kzSMRSSzKpg5ef75U2XotYNi88Tgtb53nYNrr8/anchorwallet.png","https://cdn.steemitimages.com/DQmRhhTDp99d6CvE9hvSC9ViwyqLNBKRfaATvrG1V3ZbEeQ/anchorgov.png","https://cdn.steemitimages.com/DQmZkoNejs79vg3jrTQWtkDo8oSRGd4B5ttuakAVtprWbEN/anchortools.png","https://cdn.steemitimages.com/DQmXYg6xE6TgWo3bXJRfstwKqdmyWwSZNJVpFGBCHNbEXuk/URI.png","https://i.imgur.com/wLI79sx.png"],"links":["https://twitter.com/greymass","https://t.me/teamgreymass","https://www.auroraeos.com/blog/the-next-chapter-of-aurora-eos/","https://multicoin.capital/","https://stablecoinindex.com/","https://www.auroraeos.com/","https://www.auroraeos.com/blog/","https://eosvoter.transistor.fm/","https://eosupdate.substack.com/","https://github.com/greymass/eos-voter","https://blog.greymass.com/eos/@greymass/the-future-of-the-greymass-wallet-beta-version-available-now","https://github.com/greymass/eos-voter/releases/tag/v0.9.0-anchor","https://t.me/anchorwallet","https://t.me/anchordevs","https://github.com/greymass/EEPs/blob/eep-x/EEPS/eep-7.md","https://eosio.to/gWNgZGRkWLKvhPGVQSgDCCwwugsUgQAYLQRjAIGCm_OuXYwMIDUA","https://blog.greymass.com/eos/@greymass/introducing-light-history-nodes-for-eos","https://eostitan.com/producers?name=teamgreymass","https://eostitan.com/","https://eosauthority.com/approval/","https://eosauthority.com/","https://blog.greymass.com/eos/@greymass/greymass-support-of-the-tokenauction-referendum-proposal","https://blog.greymass.com/eos/@greymass/greymass-stance-on-the-retiresaving-proposal","https://blog.greymass.com/eos/@greymass/inflation-centralization-and-dpos","https://blog.greymass.com/eos/@greymass/a-simple-system-to-support-blockchain-workers-in-dpos"],"app":"steemit/0.1","format":"markdown"}
parent author
parent permlinkeos
permlinkgreymass-team-update-first-half-of-2019
titleGreymass Team Update - First Half of 2019
Transaction InfoBlock #33365856/Trx c4053148357008a962004ca9921ed487393fdb7e
View Raw JSON Data
{
  "block": 33365856,
  "op": [
    "comment",
    {
      "author": "greymass",
      "body": "@@ -210,16 +210,17 @@\n *really*\n+ \n awesome \n@@ -367,24 +367,24 @@\n  progress. %0A\n-\n %0AWe continue\n@@ -8622,16 +8622,17 @@\n e *many*\n+ \n new tool\n@@ -16979,17 +16979,18 @@\n O chains\n-,\n+ %E2%80%94\n  plus th\n@@ -17030,25 +17030,26 @@\n  blockchains\n-,\n+ %E2%80%94\n  and we%E2%80%99ll c\n",
      "json_metadata": "{\"tags\":[\"eos\",\"greymass\",\"bp\",\"update\",\"mainnet\"],\"image\":[\"https://cdn.steemitimages.com/DQmdHGd58epVm1og1dQS3kdTVYT57tEHE8Qt9AzYDsdXfYg/Anchor1.png\",\"https://cdn.steemitimages.com/DQmaR9SS3kzSMRSSzKpg5ef75U2XotYNi88Tgtb53nYNrr8/anchorwallet.png\",\"https://cdn.steemitimages.com/DQmRhhTDp99d6CvE9hvSC9ViwyqLNBKRfaATvrG1V3ZbEeQ/anchorgov.png\",\"https://cdn.steemitimages.com/DQmZkoNejs79vg3jrTQWtkDo8oSRGd4B5ttuakAVtprWbEN/anchortools.png\",\"https://cdn.steemitimages.com/DQmXYg6xE6TgWo3bXJRfstwKqdmyWwSZNJVpFGBCHNbEXuk/URI.png\",\"https://i.imgur.com/wLI79sx.png\"],\"links\":[\"https://twitter.com/greymass\",\"https://t.me/teamgreymass\",\"https://www.auroraeos.com/blog/the-next-chapter-of-aurora-eos/\",\"https://multicoin.capital/\",\"https://stablecoinindex.com/\",\"https://www.auroraeos.com/\",\"https://www.auroraeos.com/blog/\",\"https://eosvoter.transistor.fm/\",\"https://eosupdate.substack.com/\",\"https://github.com/greymass/eos-voter\",\"https://blog.greymass.com/eos/@greymass/the-future-of-the-greymass-wallet-beta-version-available-now\",\"https://github.com/greymass/eos-voter/releases/tag/v0.9.0-anchor\",\"https://t.me/anchorwallet\",\"https://t.me/anchordevs\",\"https://github.com/greymass/EEPs/blob/eep-x/EEPS/eep-7.md\",\"https://eosio.to/gWNgZGRkWLKvhPGVQSgDCCwwugsUgQAYLQRjAIGCm_OuXYwMIDUA\",\"https://blog.greymass.com/eos/@greymass/introducing-light-history-nodes-for-eos\",\"https://eostitan.com/producers?name=teamgreymass\",\"https://eostitan.com/\",\"https://eosauthority.com/approval/\",\"https://eosauthority.com/\",\"https://blog.greymass.com/eos/@greymass/greymass-support-of-the-tokenauction-referendum-proposal\",\"https://blog.greymass.com/eos/@greymass/greymass-stance-on-the-retiresaving-proposal\",\"https://blog.greymass.com/eos/@greymass/inflation-centralization-and-dpos\",\"https://blog.greymass.com/eos/@greymass/a-simple-system-to-support-blockchain-workers-in-dpos\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
      "parent_author": "",
      "parent_permlink": "eos",
      "permlink": "greymass-team-update-first-half-of-2019",
      "title": "Greymass Team Update - First Half of 2019"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-05-30T16:51:48",
  "trx_id": "c4053148357008a962004ca9921ed487393fdb7e",
  "trx_in_block": 26,
  "virtual_op": 0
}
2019/05/30 16:41:39
authorgreymass
permlinkgreymass-team-update-first-half-of-2019
voteraicu
weight6560 (65.60%)
Transaction InfoBlock #33365653/Trx c84ce71c398116d27ebf1d392f9d196394685e39
View Raw JSON Data
{
  "block": 33365653,
  "op": [
    "vote",
    {
      "author": "greymass",
      "permlink": "greymass-team-update-first-half-of-2019",
      "voter": "aicu",
      "weight": 6560
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-05-30T16:41:39",
  "trx_id": "c84ce71c398116d27ebf1d392f9d196394685e39",
  "trx_in_block": 3,
  "virtual_op": 0
}
2019/05/30 16:40:42
authorgreymass
permlinkgreymass-team-update-first-half-of-2019
voterinertia
weight10000 (100.00%)
Transaction InfoBlock #33365634/Trx 762256258124170c92c6dc657a058ef5ad855f0e
View Raw JSON Data
{
  "block": 33365634,
  "op": [
    "vote",
    {
      "author": "greymass",
      "permlink": "greymass-team-update-first-half-of-2019",
      "voter": "inertia",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-05-30T16:40:42",
  "trx_id": "762256258124170c92c6dc657a058ef5ad855f0e",
  "trx_in_block": 4,
  "virtual_op": 0
}
2019/05/30 16:32:48
authorgreymass
body@@ -1,155 +1,4 @@ -!%5Btwitter-assets_Twitter-Avatar.jpg%5D(https://cdn.steemitimages.com/DQmX17HMGDMzFHzABCcU7QnnqRtTLEDeUiktJYkw1ijSHo6/twitter-assets_Twitter-Avatar.jpg)%0A%0A # In @@ -17822,12 +17822,77 @@ reymass Team +%0A%0A%3Ccenter%3E%0A!%5BGreymass%5D(https://i.imgur.com/wLI79sx.png)%0A%3C/center%3E
json metadata{"tags":["eos","greymass","bp","update","mainnet"],"image":["https://cdn.steemitimages.com/DQmdHGd58epVm1og1dQS3kdTVYT57tEHE8Qt9AzYDsdXfYg/Anchor1.png","https://cdn.steemitimages.com/DQmaR9SS3kzSMRSSzKpg5ef75U2XotYNi88Tgtb53nYNrr8/anchorwallet.png","https://cdn.steemitimages.com/DQmRhhTDp99d6CvE9hvSC9ViwyqLNBKRfaATvrG1V3ZbEeQ/anchorgov.png","https://cdn.steemitimages.com/DQmZkoNejs79vg3jrTQWtkDo8oSRGd4B5ttuakAVtprWbEN/anchortools.png","https://cdn.steemitimages.com/DQmXYg6xE6TgWo3bXJRfstwKqdmyWwSZNJVpFGBCHNbEXuk/URI.png","https://i.imgur.com/wLI79sx.png"],"links":["https://twitter.com/greymass","https://t.me/teamgreymass","https://www.auroraeos.com/blog/the-next-chapter-of-aurora-eos/","https://multicoin.capital/","https://stablecoinindex.com/","https://www.auroraeos.com/","https://www.auroraeos.com/blog/","https://eosvoter.transistor.fm/","https://eosupdate.substack.com/","https://github.com/greymass/eos-voter","https://blog.greymass.com/eos/@greymass/the-future-of-the-greymass-wallet-beta-version-available-now","https://github.com/greymass/eos-voter/releases/tag/v0.9.0-anchor","https://t.me/anchorwallet","https://t.me/anchordevs","https://github.com/greymass/EEPs/blob/eep-x/EEPS/eep-7.md","https://eosio.to/gWNgZGRkWLKvhPGVQSgDCCwwugsUgQAYLQRjAIGCm_OuXYwMIDUA","https://blog.greymass.com/eos/@greymass/introducing-light-history-nodes-for-eos","https://eostitan.com/producers?name=teamgreymass","https://eostitan.com/","https://eosauthority.com/approval/","https://eosauthority.com/","https://blog.greymass.com/eos/@greymass/greymass-support-of-the-tokenauction-referendum-proposal","https://blog.greymass.com/eos/@greymass/greymass-stance-on-the-retiresaving-proposal","https://blog.greymass.com/eos/@greymass/inflation-centralization-and-dpos","https://blog.greymass.com/eos/@greymass/a-simple-system-to-support-blockchain-workers-in-dpos"],"app":"steemit/0.1","format":"markdown"}
parent author
parent permlinkeos
permlinkgreymass-team-update-first-half-of-2019
titleGreymass Team Update - First Half of 2019
Transaction InfoBlock #33365476/Trx 5834029f0f47ef1d6c256ebb92e4670fcae84db1
View Raw JSON Data
{
  "block": 33365476,
  "op": [
    "comment",
    {
      "author": "greymass",
      "body": "@@ -1,155 +1,4 @@\n-!%5Btwitter-assets_Twitter-Avatar.jpg%5D(https://cdn.steemitimages.com/DQmX17HMGDMzFHzABCcU7QnnqRtTLEDeUiktJYkw1ijSHo6/twitter-assets_Twitter-Avatar.jpg)%0A%0A\n # In\n@@ -17822,12 +17822,77 @@\n reymass Team\n+%0A%0A%3Ccenter%3E%0A!%5BGreymass%5D(https://i.imgur.com/wLI79sx.png)%0A%3C/center%3E\n",
      "json_metadata": "{\"tags\":[\"eos\",\"greymass\",\"bp\",\"update\",\"mainnet\"],\"image\":[\"https://cdn.steemitimages.com/DQmdHGd58epVm1og1dQS3kdTVYT57tEHE8Qt9AzYDsdXfYg/Anchor1.png\",\"https://cdn.steemitimages.com/DQmaR9SS3kzSMRSSzKpg5ef75U2XotYNi88Tgtb53nYNrr8/anchorwallet.png\",\"https://cdn.steemitimages.com/DQmRhhTDp99d6CvE9hvSC9ViwyqLNBKRfaATvrG1V3ZbEeQ/anchorgov.png\",\"https://cdn.steemitimages.com/DQmZkoNejs79vg3jrTQWtkDo8oSRGd4B5ttuakAVtprWbEN/anchortools.png\",\"https://cdn.steemitimages.com/DQmXYg6xE6TgWo3bXJRfstwKqdmyWwSZNJVpFGBCHNbEXuk/URI.png\",\"https://i.imgur.com/wLI79sx.png\"],\"links\":[\"https://twitter.com/greymass\",\"https://t.me/teamgreymass\",\"https://www.auroraeos.com/blog/the-next-chapter-of-aurora-eos/\",\"https://multicoin.capital/\",\"https://stablecoinindex.com/\",\"https://www.auroraeos.com/\",\"https://www.auroraeos.com/blog/\",\"https://eosvoter.transistor.fm/\",\"https://eosupdate.substack.com/\",\"https://github.com/greymass/eos-voter\",\"https://blog.greymass.com/eos/@greymass/the-future-of-the-greymass-wallet-beta-version-available-now\",\"https://github.com/greymass/eos-voter/releases/tag/v0.9.0-anchor\",\"https://t.me/anchorwallet\",\"https://t.me/anchordevs\",\"https://github.com/greymass/EEPs/blob/eep-x/EEPS/eep-7.md\",\"https://eosio.to/gWNgZGRkWLKvhPGVQSgDCCwwugsUgQAYLQRjAIGCm_OuXYwMIDUA\",\"https://blog.greymass.com/eos/@greymass/introducing-light-history-nodes-for-eos\",\"https://eostitan.com/producers?name=teamgreymass\",\"https://eostitan.com/\",\"https://eosauthority.com/approval/\",\"https://eosauthority.com/\",\"https://blog.greymass.com/eos/@greymass/greymass-support-of-the-tokenauction-referendum-proposal\",\"https://blog.greymass.com/eos/@greymass/greymass-stance-on-the-retiresaving-proposal\",\"https://blog.greymass.com/eos/@greymass/inflation-centralization-and-dpos\",\"https://blog.greymass.com/eos/@greymass/a-simple-system-to-support-blockchain-workers-in-dpos\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
      "parent_author": "",
      "parent_permlink": "eos",
      "permlink": "greymass-team-update-first-half-of-2019",
      "title": "Greymass Team Update - First Half of 2019"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-05-30T16:32:48",
  "trx_id": "5834029f0f47ef1d6c256ebb92e4670fcae84db1",
  "trx_in_block": 13,
  "virtual_op": 0
}
2019/05/30 16:27:18
allow curation rewardstrue
allow votestrue
authorgreymass
extensions[]
max accepted payout0.000 SBD
percent steem dollars10000
permlinkgreymass-team-update-first-half-of-2019
Transaction InfoBlock #33365366/Trx 0e7243a0ba5231921c37ffc9ac3e1cfa93a6ae35
View Raw JSON Data
{
  "block": 33365366,
  "op": [
    "comment_options",
    {
      "allow_curation_rewards": true,
      "allow_votes": true,
      "author": "greymass",
      "extensions": [],
      "max_accepted_payout": "0.000 SBD",
      "percent_steem_dollars": 10000,
      "permlink": "greymass-team-update-first-half-of-2019"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-05-30T16:27:18",
  "trx_id": "0e7243a0ba5231921c37ffc9ac3e1cfa93a6ae35",
  "trx_in_block": 16,
  "virtual_op": 0
}
2019/05/30 16:27:18
authorgreymass
body![twitter-assets_Twitter-Avatar.jpg](https://cdn.steemitimages.com/DQmX17HMGDMzFHzABCcU7QnnqRtTLEDeUiktJYkw1ijSHo6/twitter-assets_Twitter-Avatar.jpg) # Intro 2019 has been an exciting year for the entire EOS community. It’s hard to believe that we’re already approaching one full year since mainnet launch! We’ve been heads-down in work mode on a number of *really*awesome projects that we’re excited to share with you. In this post, we wanted to take some time to offer the community a major update on our recent progress. We continue to focus primarily on two core offerings— world class block producer/network infrastructure and active participation in network governance. We believe these to be the two primary responsibilities of a block producer, so we continue to sharpen our focus to improve in these areas as much as possible. On the infrastructure side, we continue to build tools that improve the security, user experience, and efficiency of the network and the applications that run on top of it — our wallet, APIs, signing protocol project, and producer hardware are all built with these goals in mind. On the governance side, we continue to do our best to serve as stewards of the network, guiding its evolution in line with the will of the token holder community and doing our best to maximize the network’s value. We’ve been active participants in network governance, making sure to both vote on-chain and to engage with the community on important topics in discussion forums of all kinds. We are constantly looking to improve, and we love hearing from voters and the EOS community at large! Please feel free to reach out on [Twitter](https://twitter.com/greymass) or [Telegram](https://t.me/teamgreymass) if you’d like to share your thoughts! Now, let’s get into some detail on what we’ve been up to! # Team First and foremost, we’d like to announce some major additions to our team. While many in the community know Aaron Cox (aka jesta) and Scott Sallinen (aka anyx) as the faces of Greymass, fewer know about the rest of the supporting team and associates— Daniel Fugere, Johan Nordberg, and (more recently) Myles Snider. **Daniel Fugere** Daniel is an entrepreneur and software engineer who develops applications that aim to improve the lives of others. At age 19, he started his first web company, through which he developed a health service application for residents of Quebec. He has since continued creating different web applications that have the ultimate goal of making individuals more aware of the issues around them, as well as build positive relationships with people in their communities. Over the last couple of years, he has worked as a web engineer and has done back-end as well as front-end programming for projects at big companies such as Pixar, Autodesk and Riot Games. A blockchain enthusiast and avid learner of everything crypto, Daniel has been involved with Greymass since its first steps, helping develop and engineer the nitty-gritty workings of the eos-voter app. He is also an avid promoter of lifelong health – in 2014, he rode his bicycle across Canada and raised close to C$12,000 for the Canadian Pain Coalition and Quebec Chronic Pain Association. He is also a finisher of the Ironman 70.3 race. At Greymass, Daniel focuses primarily on development of our new Anchor wallet (previously eos-voter). **Johan Nordberg** Johan is a prolific developer with a broad range of experience and a passion for open-source — he has released a multitude of open-source projects, many of which are widely used. He founded his first company at age 23 after releasing one of the first iPhone apps in the AppStore. Besides iOS development, his specialties are security research, systems design and web development. Johan is a strong advocate for the Open Web and believes that blockchain technology has the potential to fundamentally change the world for the better. At Greymass he will be focusing on building our upcoming dApps-platform. **Myles Snider** Myles Snider is the newest addition to the team, [recently joining](https://www.auroraeos.com/blog/the-next-chapter-of-aurora-eos/) Greymass as a partner. Myles has been involved in the EOS ecosystem since long before mainnet launch. He previously lead research at [Multicoin Capital](https://multicoin.capital/) , where he published a number of EOS-focused investment reports. He also created [The Stablecoin Index](https://stablecoinindex.com/) , a tool to track and compare various stablecoin projects. Later, he founded a mainnet block producer called [Aurora EOS](https://www.auroraeos.com/) before eventually joining Greymass. Myles has [written extensively](https://www.auroraeos.com/blog/) about EOS economics and governance, and he’ll continue to do so in his new role here. He’ll also focus on interfacing with the community and helping bring more awareness to Greymass’s core product offerings. Myles also hosts an EOS-focused podcast called [EOS Voter](https://eosvoter.transistor.fm/) and writes a bi-weekly [newsletter](https://eosupdate.substack.com/) about the EOSIO ecosystem. # Greymass Projects **Anchor — Our eos-voter Rebrand** Many of you are likely familiar with [eos-voter](https://github.com/greymass/eos-voter) , our desktop wallet (sometimes simply called the “Greymass Wallet”). Our goal since the inception of this project has been simple— to offer a highly secure, user-friendly desktop wallet that allows users to access the full set of features of EOSIO software. We’re really excited to soon debut the 1.0 version of our redesigned, re-branded, and much-improved successor to eos-voter, which we’re calling *Anchor*. For even more details on the Anchor wallet, check our our [latest blog post](https://blog.greymass.com/eos/@greymass/the-future-of-the-greymass-wallet-beta-version-available-now) where we introduce the project. You can download the beta version of the wallet [here](https://github.com/greymass/eos-voter/releases/tag/v0.9.0-anchor) (note: this Anchor installation will not overwrite or interact with your eos-voter installation, so no need to worry about the beta causing problems with your main wallet!). If you have questions or feedback, feel free to join one of our two new Telegram channels— the [main wallet channel](https://t.me/anchorwallet) , or the [developer channel](https://t.me/anchordevs) . eos-voter has been our flagship product since network launch, and we’ve been hard at work building out Anchor into something that’s even better. We’ve created a new look, feel, and branding for the wallet, and we’ve added a ton of new features. We’ll be launching with support for EOS, BOS, Meet.One, BEOS, Telos, and Insights Network. We plan to continue to support other EOSIO chains, and we’ll continue to add new tools and features to allow users to take advantage of everything that each of these chains has to offer, all through a secure and intuitive interface. We’re still making some final additions and improvements to Anchor, but you can expect the 1.0 version to be released very soon! Below are some screenshots and short descriptions of some of the major components of Anchor. The new “Account(s) Overview” section allows users to easily manage multiple accounts across different EOSIO chains. You’ll have easy access to information about your accounts, the tokens you hold, your network resources, and your governance decisions. ![Anchor1.png](https://cdn.steemitimages.com/DQmdHGd58epVm1og1dQS3kdTVYT57tEHE8Qt9AzYDsdXfYg/Anchor1.png) The new wallet UI allows users to quickly and easily perform the most common actions— token transfers, resource management, and token leasing through REX. You can easily switch between accounts, depending on which action you’d like to take with each. ![anchorwallet.png](https://cdn.steemitimages.com/DQmaR9SS3kzSMRSSzKpg5ef75U2XotYNi88Tgtb53nYNrr8/anchorwallet.png) The new governance section builds towards the same goal we had with eos-voter— to allow token holders to easily and actively participate in network governance. This section will allow you to vote for BPs, delegate your vote to a proxy, and vote in stake-weighted on-chain referenda. As governance evolves for various EOSIO chains, we will continue to add to this section. ![anchorgov.png](https://cdn.steemitimages.com/DQmRhhTDp99d6CvE9hvSC9ViwyqLNBKRfaATvrG1V3ZbEeQ/anchorgov.png) Our new “Tools” section currently serves as a miscellaneous roundup of various actions and features that users might wish to take advantage of. As time goes on, we’ll continue to find homes for various tools in the sections mentioned above. In the meantime, know that you can continue to take advantage of the existing tools from eos-voter, as well as the *many*new tools we’ve built specifically for Anchor. ![anchortools.png](https://cdn.steemitimages.com/DQmZkoNejs79vg3jrTQWtkDo8oSRGd4B5ttuakAVtprWbEN/anchortools.png) **EOSIO Signing Request Standard** ![URI.png](https://cdn.steemitimages.com/DQmXYg6xE6TgWo3bXJRfstwKqdmyWwSZNJVpFGBCHNbEXuk/URI.png) One project we’re very excited to introduce to the EOS community is our EOSIO signing request standard. We’ve created an EOS Enhancement Proposal (EEP) for the project, which can be found [here](https://github.com/greymass/EEPs/blob/eep-x/EEPS/eep-7.md) . Our signing request standard takes information about a given transaction and encapsulates it in such a way that it can be auto-populated into any compatible wallet or signature provider. In other words, it allows for easy communication between applications and signature providers in a way that makes it easy to share or request a specific action on the blockchain from a specific account. What’s even better is that these requests can be put in many different formats, such as a QR code or a hyperlink (like [this one](https://eosio.to/gWNgZGRkWLKvhPGVQSgDCCwwugsUgQAYLQRjAIGCm_OuXYwMIDUA) ). Sound confusing? While technical in nature, the signing request standard is actually rather simple. Have you ever gone to a website and clicked on an “Email Us” link, and then watched as that link auto-opened your preferred email client and filled in the address to which you’d be sending? Now imagine if you could do that, but for any arbitrary action on any EOSIO blockchain. As an example, imagine you have a button on your website that says “Donate with EOS.” That button could link to a signing request that, when clicked on, automatically opens the user’s preferred wallet and prepares a transaction to transfer a specific amount of EOS from their account to yours. The user would simply have to approve the transaction, and they could send a donation in just a couple of clicks! Or imagine that a specific community member creates a referendum proposal. They could create a hyperlink that could be shared on Telegram, Twitter, email, and more that automatically creates a request within the recipient’s wallet to vote yes on that specific proposal. Instead of having to direct the user how to find the proposal within a given governance interface, you could simply share the link and have them cast a vote directly! That’s what our signing request standard enables, and we’ve been hard at work building it out! We’ll publish a blog post soon with more details on how this standard works, and the various exciting ways that it can be used! If you’d like to get involved, feel free to join our Telegram group and read more about the EEP on [Github](https://github.com/greymass/EEPs/blob/eep-x/EEPS/eep-7.md) . # Greymass APIs Greymass continues to run some of the most widely-used and performant APIs on the entire EOS network. We dedicate a significant portion of our BP earnings to expand our infrastructure and pay data center leasing and bandwidth fees. We will continue to invest in infrastructure that helps the network itself and the apps and services built on top of it. A few highlights of our API infrastructure: * We run a geographically distributed network of dedicated general-purpose API nodes for world-wide low-latency access, load-balanced to automatically route clients to the fastest node available. * We also developed a [light history implementation](https://blog.greymass.com/eos/@greymass/introducing-light-history-nodes-for-eos) and run dedicated light history nodes (and we’ve been happy to see a number of other BPs begin to run light history!) * We use top-of-the-line dedicated hardware (which we have purchased) located in our US data center for full history, which the geographically distributed network accesses for older history. * We have a custom API extension layer built upon all of our infrastructure to add additional calls to improve client/server communication. Over the past few months we have invested roughly $40k USD into a few new server builds for our US-based data center. This includes a handful of small but powerful dedicated hosts (Intel 4.5ghz + 32gb RAM + Optane) and one much larger build to add more capacity/redundancy to our full history stack (Intel Xeon 6244 + 768gb RAM + 7x Optane). These servers are expected to come online for public use within the next month and will enhance our ability to provide services to the EOSIO community. Further, we continue to explore various ways of improving APIs on EOS. We will be publishing more thoughts and building more tools in the near future on these issues specifically. # Governance We believe that participation in network governance is a core part of the responsibility of an EOS block producer. We believe that this should take two forms— participation in governance discussions within the community, as well as on-chain voting. When we make governance decisions, we not only vote on-chain, but we also do our best to communicate our stance to the community through blog posts, social media, and discussion channels. If you’d like to see our on-chain referendum votes, you can do so using [this useful tool](https://eostitan.com/producers?name=teamgreymass) by [EOS Titan](https://eostitan.com/) . To keep track of BP approval votes, you can use [this tool](https://eosauthority.com/approval/) from [EOS Authority](https://eosauthority.com/) . BP approval votes are requested from the top 30 ranking BPs at the time the approval is submitted. Any time we are in the top 30, we will review proposals, communicate a stance on them, and vote on-chain if we approve. Below are links to some of our blog posts, commentary, and ideas on recent governance initiatives. * Our support of the [tokenauction](https://blog.greymass.com/eos/@greymass/greymass-support-of-the-tokenauction-referendum-proposal) referendum proposal * Our stance on the [retiresaving](https://blog.greymass.com/eos/@greymass/greymass-stance-on-the-retiresaving-proposal) proposal * Our [commentary](https://blog.greymass.com/eos/@greymass/inflation-centralization-and-dpos) on how inflation affects decentralization in EOS * Our [proposal](https://blog.greymass.com/eos/@greymass/a-simple-system-to-support-blockchain-workers-in-dpos) for a “Worker Candidate” system for EOSIO chains For additional commentary on various governance initiatives, be sure to follow us on [Twitter](https://twitter.com/greymass) and [Telegram](https://t.me/teamgreymass) . # Roadmap For much of 2019, our focus has been on designing, building, and testing Anchor. We’re extremely proud of the progress we’ve made and the product we’ve built, and we can’t wait to release the 1.0 version to the community. But we believe the release of Anchor will also mark an important turning point in the project, as it transitions from being something entirely built by Greymass into something that is built, maintained, and improved by a community of developers all over the world. We’re big believers in the ethos of open-source software, and we see Anchor as a type of “dApp” that can live, develop, and grow beyond our organization. Another great thing about the Anchor release is that it will free up time for our team to tackle some other EOSIO ecosystem challenges we’ve been thinking about for quite some time. As many of our voters know, we’ve spent lots of time studying, building, and maintaining infrastructure for EOS APIs. Both of these efforts have given us great insight into how a number of various backend platforms could be improved upon to strengthen any network running on the EOSIO platform. Between new API endpoints, improved data structures, better communication protocols - there’s a lot we hope to contribute improvements towards. You can also expect a brand new version of the Greymass website coming soon! Finally, we’re continuing to look at how we can collaborate with, support, and improve other EOSIO blockchain ecosystems. We strongly believe that there will be hundreds, if not thousands, of interoperable EOSIO chains in the future. This will allow for experimentation and evolution at a speed that we haven’t yet seen in the blockchain world, and we’re excited to be a part of it. Anchor will launch with out-of-the-box support 6 different EOSIO chains, plus the ability for users to add custom blockchains, and we’ll continue to add more support where it makes sense. We also continue to explore other ways of supporting EOSIO infrastructure, including validation, other open-source tools, infrastructure services, second layer expansion (like DSPs), and much more. Stay tuned for more information on all of these projects as we explore each and every one! We’ll be sure to keep our community of voters updated as we do. As always, thank you for your support. We couldn’t do any of this without the community of voters that backs us. If you’d like to continue to support our efforts, you can do so by voting for us at **teamgreymass**. We look forward to continuing to serve this community by building tools, adding value, and actively participating in this network! Sincerely, The Greymass Team
json metadata{"tags":["eos","greymass","bp","update","mainnet"],"image":["https://cdn.steemitimages.com/DQmX17HMGDMzFHzABCcU7QnnqRtTLEDeUiktJYkw1ijSHo6/twitter-assets_Twitter-Avatar.jpg","https://cdn.steemitimages.com/DQmdHGd58epVm1og1dQS3kdTVYT57tEHE8Qt9AzYDsdXfYg/Anchor1.png","https://cdn.steemitimages.com/DQmaR9SS3kzSMRSSzKpg5ef75U2XotYNi88Tgtb53nYNrr8/anchorwallet.png","https://cdn.steemitimages.com/DQmRhhTDp99d6CvE9hvSC9ViwyqLNBKRfaATvrG1V3ZbEeQ/anchorgov.png","https://cdn.steemitimages.com/DQmZkoNejs79vg3jrTQWtkDo8oSRGd4B5ttuakAVtprWbEN/anchortools.png","https://cdn.steemitimages.com/DQmXYg6xE6TgWo3bXJRfstwKqdmyWwSZNJVpFGBCHNbEXuk/URI.png"],"links":["https://twitter.com/greymass","https://t.me/teamgreymass","https://www.auroraeos.com/blog/the-next-chapter-of-aurora-eos/","https://multicoin.capital/","https://stablecoinindex.com/","https://www.auroraeos.com/","https://www.auroraeos.com/blog/","https://eosvoter.transistor.fm/","https://eosupdate.substack.com/","https://github.com/greymass/eos-voter","https://blog.greymass.com/eos/@greymass/the-future-of-the-greymass-wallet-beta-version-available-now","https://github.com/greymass/eos-voter/releases/tag/v0.9.0-anchor","https://t.me/anchorwallet","https://t.me/anchordevs","https://github.com/greymass/EEPs/blob/eep-x/EEPS/eep-7.md","https://eosio.to/gWNgZGRkWLKvhPGVQSgDCCwwugsUgQAYLQRjAIGCm_OuXYwMIDUA","https://blog.greymass.com/eos/@greymass/introducing-light-history-nodes-for-eos","https://eostitan.com/producers?name=teamgreymass","https://eostitan.com/","https://eosauthority.com/approval/","https://eosauthority.com/","https://blog.greymass.com/eos/@greymass/greymass-support-of-the-tokenauction-referendum-proposal","https://blog.greymass.com/eos/@greymass/greymass-stance-on-the-retiresaving-proposal","https://blog.greymass.com/eos/@greymass/inflation-centralization-and-dpos","https://blog.greymass.com/eos/@greymass/a-simple-system-to-support-blockchain-workers-in-dpos"],"app":"steemit/0.1","format":"markdown"}
parent author
parent permlinkeos
permlinkgreymass-team-update-first-half-of-2019
titleGreymass Team Update - First Half of 2019
Transaction InfoBlock #33365366/Trx 0e7243a0ba5231921c37ffc9ac3e1cfa93a6ae35
View Raw JSON Data
{
  "block": 33365366,
  "op": [
    "comment",
    {
      "author": "greymass",
      "body": "![twitter-assets_Twitter-Avatar.jpg](https://cdn.steemitimages.com/DQmX17HMGDMzFHzABCcU7QnnqRtTLEDeUiktJYkw1ijSHo6/twitter-assets_Twitter-Avatar.jpg)\n\n# Intro\n\n\n2019 has been an exciting year for the entire EOS community. It’s hard to believe that we’re already approaching one full year since mainnet launch! We’ve been heads-down in work mode on a number of *really*awesome projects that we’re excited to share with you. In this post, we wanted to take some time to offer the community a major update on our recent progress. \n\nWe continue to focus primarily on two core offerings— world class block producer/network infrastructure and active participation in network governance. We believe these to be the two primary responsibilities of a block producer, so we continue to sharpen our focus to improve in these areas as much as possible. \n\nOn the infrastructure side, we continue to build tools that improve the security, user experience, and efficiency of the network and the applications that run on top of it — our wallet, APIs, signing protocol project, and producer hardware are all built with these goals in mind. On the governance side, we continue to do our best to serve as stewards of the network, guiding its evolution in line with the will of the token holder community and doing our best to maximize the network’s value. We’ve been active participants in network governance, making sure to both vote on-chain and to engage with the community on important topics in discussion forums of all kinds. \n\nWe are constantly looking to improve, and we love hearing from voters and the EOS community at large! Please feel free to reach out on  [Twitter](https://twitter.com/greymass)  or  [Telegram](https://t.me/teamgreymass)  if you’d like to share your thoughts! \n\nNow, let’s get into some detail on what we’ve been up to! \n\n# Team\n\n\nFirst and foremost, we’d like to announce some major additions to our team. While many in the community know Aaron Cox (aka jesta) and Scott Sallinen (aka anyx) as the faces of Greymass, fewer know about the rest of the supporting team and associates— Daniel Fugere, Johan Nordberg, and (more recently) Myles Snider. \n\n**Daniel Fugere**\n\nDaniel is an entrepreneur and software engineer who develops applications that aim to improve the lives of others. At age 19, he started his first web company, through which he developed a health service application for residents of Quebec. He has since continued creating different web applications that have the ultimate goal of making individuals more aware of the issues around them, as well as build positive relationships with people in their communities. Over the last couple of years, he has worked as a web engineer and has done back-end as well as front-end programming for projects at big companies such as Pixar, Autodesk and Riot Games. A blockchain enthusiast and avid learner of everything crypto, Daniel has been involved with Greymass since its first steps, helping develop and engineer the nitty-gritty workings of the eos-voter app. He is also an avid promoter of lifelong health – in 2014, he rode his bicycle across Canada and raised close to C$12,000 for the Canadian Pain Coalition and Quebec Chronic Pain Association. He is also a finisher of the Ironman 70.3 race. At Greymass, Daniel focuses primarily on development of our new Anchor wallet (previously eos-voter). \n\n**Johan Nordberg**\n\nJohan is a prolific developer with a broad range of experience and a passion for open-source — he has released a multitude of open-source projects, many of which are widely used. He founded his first company at age 23 after releasing one of the first iPhone apps in the AppStore. Besides iOS development, his specialties are security research, systems design and web development. Johan is a strong advocate for the Open Web and believes that blockchain technology has the potential to fundamentally change the world for the better. At Greymass he will be focusing on building our upcoming dApps-platform.\n\n**Myles Snider**\n\nMyles Snider is the newest addition to the team,  [recently joining](https://www.auroraeos.com/blog/the-next-chapter-of-aurora-eos/)  Greymass as a partner. Myles has been involved in the EOS ecosystem since long before mainnet launch. He previously lead research at  [Multicoin Capital](https://multicoin.capital/) , where he published a number of EOS-focused investment reports. He also created  [The Stablecoin Index](https://stablecoinindex.com/) , a tool to track and compare various stablecoin projects. Later, he founded a mainnet block producer called  [Aurora EOS](https://www.auroraeos.com/)  before eventually joining Greymass. Myles has  [written extensively](https://www.auroraeos.com/blog/)  about EOS economics and governance, and he’ll continue to do so in his new role here. He’ll also focus on interfacing with the community and helping bring more awareness to Greymass’s core product offerings. Myles also hosts an EOS-focused podcast called  [EOS Voter](https://eosvoter.transistor.fm/)  and writes a bi-weekly  [newsletter](https://eosupdate.substack.com/)  about the EOSIO ecosystem. \n\n\n# Greymass Projects\n\n\n**Anchor — Our eos-voter Rebrand**\n\nMany of you are likely familiar with  [eos-voter](https://github.com/greymass/eos-voter) , our desktop wallet (sometimes simply called the “Greymass Wallet”). Our goal since the inception of this project has been simple— to offer a highly secure, user-friendly desktop wallet that allows users to access the full set of features of EOSIO software. We’re really excited to soon debut the 1.0 version of our redesigned, re-branded, and much-improved successor to eos-voter, which we’re calling *Anchor*. \n\nFor even more details on the Anchor wallet, check our our  [latest blog post](https://blog.greymass.com/eos/@greymass/the-future-of-the-greymass-wallet-beta-version-available-now)  where we introduce the project. You can download the beta version of the wallet  [here](https://github.com/greymass/eos-voter/releases/tag/v0.9.0-anchor)  (note: this Anchor installation will not overwrite or interact with your eos-voter installation, so no need to worry about the beta causing problems with your main wallet!). If you have questions or feedback, feel free to join one of our two new Telegram channels— the  [main wallet channel](https://t.me/anchorwallet) , or the  [developer channel](https://t.me/anchordevs) . \n\neos-voter has been our flagship product since network launch, and we’ve been hard at work building out Anchor into something that’s even better. We’ve created a new look, feel, and branding for the wallet, and we’ve added a ton of new features. We’ll be launching with support for EOS, BOS, Meet.One, BEOS, Telos, and Insights Network. We plan to continue to support other EOSIO chains, and we’ll continue to add new tools and features to allow users to take advantage of everything that each of these chains has to offer, all through a secure and intuitive interface. \n\nWe’re still making some final additions and improvements to Anchor, but you can expect the 1.0 version to be released very soon! Below are some screenshots and short descriptions of some of the major components of Anchor. \n\nThe new “Account(s) Overview” section allows users to easily manage multiple accounts across different EOSIO chains. You’ll have easy access to information about your accounts, the tokens you hold, your network resources, and your governance decisions. \n\n![Anchor1.png](https://cdn.steemitimages.com/DQmdHGd58epVm1og1dQS3kdTVYT57tEHE8Qt9AzYDsdXfYg/Anchor1.png)\n\nThe new wallet UI allows users to quickly and easily perform the most common actions— token transfers, resource management, and token leasing through REX. You can easily switch between accounts, depending on which action you’d like to take with each. \n\n![anchorwallet.png](https://cdn.steemitimages.com/DQmaR9SS3kzSMRSSzKpg5ef75U2XotYNi88Tgtb53nYNrr8/anchorwallet.png)\n\nThe new governance section builds towards the same goal we had with eos-voter— to allow token holders to easily and actively participate in network governance. This section will allow you to vote for BPs, delegate your vote to a proxy, and vote in stake-weighted on-chain referenda. As governance evolves for various EOSIO chains, we will continue to add to this section. \n\n![anchorgov.png](https://cdn.steemitimages.com/DQmRhhTDp99d6CvE9hvSC9ViwyqLNBKRfaATvrG1V3ZbEeQ/anchorgov.png)\n\nOur new “Tools” section currently serves as a miscellaneous roundup of various actions and features that users might wish to take advantage of. As time goes on, we’ll continue to find homes for various tools in the sections mentioned above. In the meantime, know that you can continue to take advantage of the existing tools from eos-voter, as well as the *many*new tools we’ve built specifically for Anchor. \n\n![anchortools.png](https://cdn.steemitimages.com/DQmZkoNejs79vg3jrTQWtkDo8oSRGd4B5ttuakAVtprWbEN/anchortools.png)\n\n**EOSIO Signing Request Standard**\n\n![URI.png](https://cdn.steemitimages.com/DQmXYg6xE6TgWo3bXJRfstwKqdmyWwSZNJVpFGBCHNbEXuk/URI.png)\n\nOne project we’re very excited to introduce to the EOS community is our EOSIO signing request standard. We’ve created an EOS Enhancement Proposal (EEP) for the project, which can be found  [here](https://github.com/greymass/EEPs/blob/eep-x/EEPS/eep-7.md) . \n\nOur signing request standard takes information about a given transaction and encapsulates it in such a way that it can be auto-populated into any compatible wallet or signature provider. In other words, it allows for easy communication between applications and signature providers in a way that makes it easy to share or request a specific action on the blockchain from a specific account. What’s even better is that these requests can be put in many different formats, such as a QR code or a hyperlink (like  [this one](https://eosio.to/gWNgZGRkWLKvhPGVQSgDCCwwugsUgQAYLQRjAIGCm_OuXYwMIDUA) ). \n\nSound confusing? While technical in nature, the signing request standard is actually rather simple. Have you ever gone to a website and clicked on an “Email Us” link, and then watched as that link auto-opened your preferred email client and filled in the address to which you’d be sending? Now imagine if you could do that, but for any arbitrary action on any EOSIO blockchain. \n\nAs an example, imagine you have a button on your website that says “Donate with EOS.” That button could link to a signing request that, when clicked on, automatically opens the user’s preferred wallet and prepares a transaction to transfer a specific amount of EOS from their account to yours. The user would simply have to approve the transaction, and they could send a donation in just a couple of clicks! Or imagine that a specific community member creates a referendum proposal. They could create a hyperlink that could be shared on Telegram, Twitter, email, and more that automatically creates a request within the recipient’s wallet to vote yes on that specific proposal. Instead of having to direct the user how to find the proposal within a given governance interface, you could simply share the link and have them cast a vote directly! \n\nThat’s what our signing request standard enables, and we’ve been hard at work building it out! We’ll publish a blog post soon with more details on how this standard works, and the various exciting ways that it can be used! If you’d like to get involved, feel free to join our Telegram group and read more about the EEP on  [Github](https://github.com/greymass/EEPs/blob/eep-x/EEPS/eep-7.md) . \n\n\n# Greymass APIs\n\n\nGreymass continues to run some of the most widely-used and performant APIs on the entire EOS network. We dedicate a significant portion of our BP earnings to expand our infrastructure and pay data center leasing and bandwidth fees. We will continue to invest in infrastructure that helps the network itself and the apps and services built on top of it. \n\nA few highlights of our API infrastructure: \n\n* We run a geographically distributed network of dedicated general-purpose API nodes for world-wide low-latency access, load-balanced to automatically route clients to the fastest node available.\n\n* We also developed a  [light history implementation](https://blog.greymass.com/eos/@greymass/introducing-light-history-nodes-for-eos)  and run dedicated light history nodes (and we’ve been happy to see a number of other BPs begin to run light history!) \n\n* We use top-of-the-line dedicated hardware (which we have purchased) located in our US data center for full history, which the geographically distributed network accesses for older history.\n\n* We have a custom API extension layer built upon all of our infrastructure to add additional calls to improve client/server communication.\n\n\nOver the past few months we have invested roughly $40k USD into a few new server builds for our US-based data center. This includes a handful of small but powerful dedicated hosts (Intel 4.5ghz + 32gb RAM + Optane) and one much larger build to add more capacity/redundancy to our full history stack (Intel Xeon 6244 + 768gb RAM + 7x Optane). These servers are expected to come online for public use within the next month and will enhance our ability to provide services to the EOSIO community.\n\nFurther, we continue to explore various ways of improving APIs on EOS. We will be publishing more thoughts and building more tools in the near future on these issues specifically. \n# Governance\n\n\nWe believe that participation in network governance is a core part of the responsibility of an EOS block producer. We believe that this should take two forms— participation in governance discussions within the community, as well as on-chain voting. When we make governance decisions, we not only vote on-chain, but we also do our best to communicate our stance to the community through blog posts, social media, and discussion channels. \n\nIf you’d like to see our on-chain referendum votes, you can do so using  [this useful tool](https://eostitan.com/producers?name=teamgreymass)  by  [EOS Titan](https://eostitan.com/) . To keep track of BP approval votes, you can use  [this tool](https://eosauthority.com/approval/)  from  [EOS Authority](https://eosauthority.com/) . BP approval votes are requested from the top 30 ranking BPs at the time the approval is submitted. Any time we are in the top 30, we will review proposals, communicate a stance on them, and vote on-chain if we approve. Below are links to some of our blog posts, commentary, and ideas on recent governance initiatives. \n\n* Our support of the  [tokenauction](https://blog.greymass.com/eos/@greymass/greymass-support-of-the-tokenauction-referendum-proposal)  referendum proposal \n\n* Our stance on the  [retiresaving](https://blog.greymass.com/eos/@greymass/greymass-stance-on-the-retiresaving-proposal)  proposal \n\n* Our  [commentary](https://blog.greymass.com/eos/@greymass/inflation-centralization-and-dpos)  on how inflation affects decentralization in EOS \n\n* Our  [proposal](https://blog.greymass.com/eos/@greymass/a-simple-system-to-support-blockchain-workers-in-dpos)  for a “Worker Candidate” system for EOSIO chains \n\n\nFor additional commentary on various governance initiatives, be sure to follow us on  [Twitter](https://twitter.com/greymass)  and  [Telegram](https://t.me/teamgreymass) . \n\n# Roadmap\n\n\nFor much of 2019, our focus has been on designing, building, and testing Anchor. We’re extremely proud of the progress we’ve made and the product we’ve built, and we can’t wait to release the 1.0 version to the community. But we believe the release of Anchor will also mark an important turning point in the project, as it transitions from being something entirely built by Greymass into something that is built, maintained, and improved by a community of developers all over the world. We’re big believers in the ethos of open-source software, and we see Anchor as a type of “dApp” that can live, develop, and grow beyond our organization. \n\nAnother great thing about the Anchor release is that it will free up time for our team to tackle some other EOSIO ecosystem challenges we’ve been thinking about for quite some time. As many of our voters know, we’ve spent lots of time studying, building, and maintaining infrastructure for EOS APIs. Both of these efforts have given us great insight into how a number of various backend platforms could be improved upon to strengthen any network running on the EOSIO platform. Between new API endpoints, improved data structures, better communication protocols - there’s a lot we hope to contribute improvements towards.\n\nYou can also expect a brand new version of the Greymass website coming soon! \n\nFinally, we’re continuing to look at how we can collaborate with, support, and improve other EOSIO blockchain ecosystems. We strongly believe that there will be hundreds, if not thousands, of interoperable EOSIO chains in the future. This will allow for experimentation and evolution at a speed that we haven’t yet seen in the blockchain world, and we’re excited to be a part of it. Anchor will launch with out-of-the-box support 6 different EOSIO chains, plus the ability for users to add custom blockchains, and we’ll continue to add more support where it makes sense. We also continue to explore other ways of supporting EOSIO infrastructure, including validation, other open-source tools, infrastructure services, second layer expansion (like DSPs), and much more. Stay tuned for more information on all of these projects as we explore each and every one! We’ll be sure to keep our community of voters updated as we do. \n\nAs always, thank you for your support. We couldn’t do any of this without the community of voters that backs us. If you’d like to continue to support our efforts, you can do so by voting for us at **teamgreymass**. We look forward to continuing to serve this community by building tools, adding value, and actively participating in this network! \n\nSincerely, \nThe Greymass Team",
      "json_metadata": "{\"tags\":[\"eos\",\"greymass\",\"bp\",\"update\",\"mainnet\"],\"image\":[\"https://cdn.steemitimages.com/DQmX17HMGDMzFHzABCcU7QnnqRtTLEDeUiktJYkw1ijSHo6/twitter-assets_Twitter-Avatar.jpg\",\"https://cdn.steemitimages.com/DQmdHGd58epVm1og1dQS3kdTVYT57tEHE8Qt9AzYDsdXfYg/Anchor1.png\",\"https://cdn.steemitimages.com/DQmaR9SS3kzSMRSSzKpg5ef75U2XotYNi88Tgtb53nYNrr8/anchorwallet.png\",\"https://cdn.steemitimages.com/DQmRhhTDp99d6CvE9hvSC9ViwyqLNBKRfaATvrG1V3ZbEeQ/anchorgov.png\",\"https://cdn.steemitimages.com/DQmZkoNejs79vg3jrTQWtkDo8oSRGd4B5ttuakAVtprWbEN/anchortools.png\",\"https://cdn.steemitimages.com/DQmXYg6xE6TgWo3bXJRfstwKqdmyWwSZNJVpFGBCHNbEXuk/URI.png\"],\"links\":[\"https://twitter.com/greymass\",\"https://t.me/teamgreymass\",\"https://www.auroraeos.com/blog/the-next-chapter-of-aurora-eos/\",\"https://multicoin.capital/\",\"https://stablecoinindex.com/\",\"https://www.auroraeos.com/\",\"https://www.auroraeos.com/blog/\",\"https://eosvoter.transistor.fm/\",\"https://eosupdate.substack.com/\",\"https://github.com/greymass/eos-voter\",\"https://blog.greymass.com/eos/@greymass/the-future-of-the-greymass-wallet-beta-version-available-now\",\"https://github.com/greymass/eos-voter/releases/tag/v0.9.0-anchor\",\"https://t.me/anchorwallet\",\"https://t.me/anchordevs\",\"https://github.com/greymass/EEPs/blob/eep-x/EEPS/eep-7.md\",\"https://eosio.to/gWNgZGRkWLKvhPGVQSgDCCwwugsUgQAYLQRjAIGCm_OuXYwMIDUA\",\"https://blog.greymass.com/eos/@greymass/introducing-light-history-nodes-for-eos\",\"https://eostitan.com/producers?name=teamgreymass\",\"https://eostitan.com/\",\"https://eosauthority.com/approval/\",\"https://eosauthority.com/\",\"https://blog.greymass.com/eos/@greymass/greymass-support-of-the-tokenauction-referendum-proposal\",\"https://blog.greymass.com/eos/@greymass/greymass-stance-on-the-retiresaving-proposal\",\"https://blog.greymass.com/eos/@greymass/inflation-centralization-and-dpos\",\"https://blog.greymass.com/eos/@greymass/a-simple-system-to-support-blockchain-workers-in-dpos\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
      "parent_author": "",
      "parent_permlink": "eos",
      "permlink": "greymass-team-update-first-half-of-2019",
      "title": "Greymass Team Update - First Half of 2019"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-05-30T16:27:18",
  "trx_id": "0e7243a0ba5231921c37ffc9ac3e1cfa93a6ae35",
  "trx_in_block": 16,
  "virtual_op": 0
}
greymasscustom json: 1
2019/05/26 15:22:12
id1
json{"foo":"bar"}
required auths["greymass"]
required posting auths[]
Transaction InfoBlock #33248971/Trx e55f1bd3de7f588c095237f9f602ef0dbbb85103
View Raw JSON Data
{
  "block": 33248971,
  "op": [
    "custom_json",
    {
      "id": "1",
      "json": "{\"foo\":\"bar\"}",
      "required_auths": [
        "greymass"
      ],
      "required_posting_auths": []
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-05-26T15:22:12",
  "trx_id": "e55f1bd3de7f588c095237f9f602ef0dbbb85103",
  "trx_in_block": 3,
  "virtual_op": 0
}
greymasscustom json: 1
2019/05/26 15:12:03
id1
json{"foo": "bar"}
required auths[]
required posting auths["greymass"]
Transaction InfoBlock #33248768/Trx 1c8fedd6a126f93783de2dfa82f050b24d8567ae
View Raw JSON Data
{
  "block": 33248768,
  "op": [
    "custom_json",
    {
      "id": "1",
      "json": "{\"foo\": \"bar\"}",
      "required_auths": [],
      "required_posting_auths": [
        "greymass"
      ]
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-05-26T15:12:03",
  "trx_id": "1c8fedd6a126f93783de2dfa82f050b24d8567ae",
  "trx_in_block": 43,
  "virtual_op": 0
}
2019/05/22 14:28:42
authorgreymass
permlinkthe-future-of-the-greymass-wallet-beta-version-available-now
voterlior-h
weight10000 (100.00%)
Transaction InfoBlock #33132795/Trx edbec87a610f73300e52c01da963334fd3fb91ed
View Raw JSON Data
{
  "block": 33132795,
  "op": [
    "vote",
    {
      "author": "greymass",
      "permlink": "the-future-of-the-greymass-wallet-beta-version-available-now",
      "voter": "lior-h",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-05-22T14:28:42",
  "trx_id": "edbec87a610f73300e52c01da963334fd3fb91ed",
  "trx_in_block": 26,
  "virtual_op": 0
}
2019/05/22 09:49:09
authorgreymass
permlinkthe-future-of-the-greymass-wallet-beta-version-available-now
voterwackou
weight10000 (100.00%)
Transaction InfoBlock #33127208/Trx 3cd9e88983d4330c406cc5b86284e9b57bff4cce
View Raw JSON Data
{
  "block": 33127208,
  "op": [
    "vote",
    {
      "author": "greymass",
      "permlink": "the-future-of-the-greymass-wallet-beta-version-available-now",
      "voter": "wackou",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-05-22T09:49:09",
  "trx_id": "3cd9e88983d4330c406cc5b86284e9b57bff4cce",
  "trx_in_block": 35,
  "virtual_op": 0
}
2019/05/22 01:41:45
authorv4vapid
bodyCongratulations! I've been patiently awaiting its release and it looks fantastic. The ability to load several blockchains and manage multiple accounts is such an awesome upgrade! Keep up the great work, and I think a lot of people sleep on how much your team provides to the greater community - you deserve much more recognition for your efforts. Excited to test it out :)
json metadata{"tags":["eos"],"app":"steempeak/1.9.9"}
parent authorgreymass
parent permlinkthe-future-of-the-greymass-wallet-beta-version-available-now
permlinkre-greymass-the-future-of-the-greymass-wallet-beta-version-available-now-20190522t014145120z
title
Transaction InfoBlock #33117466/Trx 2f47b1f75d2027a4b9a86198940af8b38e8dfa7d
View Raw JSON Data
{
  "block": 33117466,
  "op": [
    "comment",
    {
      "author": "v4vapid",
      "body": "Congratulations! I've been patiently awaiting its release and it looks fantastic. The ability to load several blockchains and manage multiple accounts is such an awesome upgrade! Keep up the great work, and I think a lot of people sleep on how much your team provides to the greater community - you deserve much more recognition for your efforts. Excited to test it out :)",
      "json_metadata": "{\"tags\":[\"eos\"],\"app\":\"steempeak/1.9.9\"}",
      "parent_author": "greymass",
      "parent_permlink": "the-future-of-the-greymass-wallet-beta-version-available-now",
      "permlink": "re-greymass-the-future-of-the-greymass-wallet-beta-version-available-now-20190522t014145120z",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-05-22T01:41:45",
  "trx_id": "2f47b1f75d2027a4b9a86198940af8b38e8dfa7d",
  "trx_in_block": 25,
  "virtual_op": 0
}
2019/05/21 21:36:06
authorgreymass
permlinkthe-future-of-the-greymass-wallet-beta-version-available-now
voterthemonetaryfew
weight10000 (100.00%)
Transaction InfoBlock #33112556/Trx 082b3d927ab0df9fe7bae7d4e6f87477ecb0776c
View Raw JSON Data
{
  "block": 33112556,
  "op": [
    "vote",
    {
      "author": "greymass",
      "permlink": "the-future-of-the-greymass-wallet-beta-version-available-now",
      "voter": "themonetaryfew",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-05-21T21:36:06",
  "trx_id": "082b3d927ab0df9fe7bae7d4e6f87477ecb0776c",
  "trx_in_block": 18,
  "virtual_op": 0
}
2019/05/21 20:18:06
authorgreymass
permlinkthe-future-of-the-greymass-wallet-beta-version-available-now
voterzoidsoft
weight10000 (100.00%)
Transaction InfoBlock #33110997/Trx 818604933f44daac73329790c278c84a87af5247
View Raw JSON Data
{
  "block": 33110997,
  "op": [
    "vote",
    {
      "author": "greymass",
      "permlink": "the-future-of-the-greymass-wallet-beta-version-available-now",
      "voter": "zoidsoft",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-05-21T20:18:06",
  "trx_id": "818604933f44daac73329790c278c84a87af5247",
  "trx_in_block": 26,
  "virtual_op": 0
}
2019/05/21 18:46:15
authorgreymass
permlinkthe-future-of-the-greymass-wallet-beta-version-available-now
votersteemitboard
weight100 (1.00%)
Transaction InfoBlock #33109163/Trx 5598938f391e9aa4a4a2034dd65f07e54a18bb62
View Raw JSON Data
{
  "block": 33109163,
  "op": [
    "vote",
    {
      "author": "greymass",
      "permlink": "the-future-of-the-greymass-wallet-beta-version-available-now",
      "voter": "steemitboard",
      "weight": 100
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-05-21T18:46:15",
  "trx_id": "5598938f391e9aa4a4a2034dd65f07e54a18bb62",
  "trx_in_block": 8,
  "virtual_op": 0
}
2019/05/21 18:46:12
authorsteemitboard
bodyCongratulations @greymass! You have completed the following achievement on the Steem blockchain and have been rewarded with new badge(s) : <table><tr><td><img src="https://steemitimages.com/60x70/http://steemitboard.com/@greymass/posts.png?201905211752"></td><td>You published more than 30 posts. Your next target is to reach 40 posts.</td></tr> </table> <sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@greymass) and compare to others on the [Steem Ranking](http://steemitboard.com/ranking/index.php?name=greymass)_</sub> <sub>_If you no longer want to receive notifications, reply to this comment with the word_ `STOP`</sub> To support your work, I also upvoted your post! ###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!
json metadata{"image":["https://steemitboard.com/img/notify.png"]}
parent authorgreymass
parent permlinkthe-future-of-the-greymass-wallet-beta-version-available-now
permlinksteemitboard-notify-greymass-20190521t184614000z
title
Transaction InfoBlock #33109162/Trx 476e032414c0fa5d4154cb42067c846e952136ed
View Raw JSON Data
{
  "block": 33109162,
  "op": [
    "comment",
    {
      "author": "steemitboard",
      "body": "Congratulations @greymass! You have completed the following achievement on the Steem blockchain and have been rewarded with new badge(s) :\n\n<table><tr><td><img src=\"https://steemitimages.com/60x70/http://steemitboard.com/@greymass/posts.png?201905211752\"></td><td>You published more than 30 posts. Your next target is to reach 40 posts.</td></tr>\n</table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@greymass) and compare to others on the [Steem Ranking](http://steemitboard.com/ranking/index.php?name=greymass)_</sub>\n<sub>_If you no longer want to receive notifications, reply to this comment with the word_ `STOP`</sub>\n\n\nTo support your work, I also upvoted your post!\n\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
      "json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}",
      "parent_author": "greymass",
      "parent_permlink": "the-future-of-the-greymass-wallet-beta-version-available-now",
      "permlink": "steemitboard-notify-greymass-20190521t184614000z",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-05-21T18:46:12",
  "trx_id": "476e032414c0fa5d4154cb42067c846e952136ed",
  "trx_in_block": 36,
  "virtual_op": 0
}
2019/05/21 17:29:18
authorgreymass
permlinkthe-future-of-the-greymass-wallet-beta-version-available-now
voterpnc
weight10000 (100.00%)
Transaction InfoBlock #33107626/Trx a3d8001e15bef03983160a4f8e1366a94667d565
View Raw JSON Data
{
  "block": 33107626,
  "op": [
    "vote",
    {
      "author": "greymass",
      "permlink": "the-future-of-the-greymass-wallet-beta-version-available-now",
      "voter": "pnc",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-05-21T17:29:18",
  "trx_id": "a3d8001e15bef03983160a4f8e1366a94667d565",
  "trx_in_block": 1,
  "virtual_op": 0
}
2019/05/21 17:28:54
authorgreymass
permlinkthe-future-of-the-greymass-wallet-beta-version-available-now
voterzedpal
weight10000 (100.00%)
Transaction InfoBlock #33107618/Trx fe72e7e403ec2b788a0dd41bd5e570408bd02747
View Raw JSON Data
{
  "block": 33107618,
  "op": [
    "vote",
    {
      "author": "greymass",
      "permlink": "the-future-of-the-greymass-wallet-beta-version-available-now",
      "voter": "zedpal",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-05-21T17:28:54",
  "trx_id": "fe72e7e403ec2b788a0dd41bd5e570408bd02747",
  "trx_in_block": 26,
  "virtual_op": 0
}
2019/05/21 16:42:21
authortts
bodyTo listen to the audio version of this article click on the play image. [![](https://s18.postimg.org/51o0kpijd/play200x46.png)](http://ec2-52-72-169-104.compute-1.amazonaws.com/greymass__the-future-of-the-greymass-wallet-beta-version-available-now.mp3) Brought to you by [@tts](https://steemit.com/tts/@tts/introduction). If you find it useful please consider upvoting this reply.
json metadata
parent authorgreymass
parent permlinkthe-future-of-the-greymass-wallet-beta-version-available-now
permlinkre-the-future-of-the-greymass-wallet-beta-version-available-now-20190521t164220
title
Transaction InfoBlock #33106687/Trx f1222bc687784a5b43278c2086c2696b8d65a526
View Raw JSON Data
{
  "block": 33106687,
  "op": [
    "comment",
    {
      "author": "tts",
      "body": "To listen to the audio version of this article click on the play image.\n[![](https://s18.postimg.org/51o0kpijd/play200x46.png)](http://ec2-52-72-169-104.compute-1.amazonaws.com/greymass__the-future-of-the-greymass-wallet-beta-version-available-now.mp3)\nBrought to you by [@tts](https://steemit.com/tts/@tts/introduction). If you find it useful please consider upvoting this reply.",
      "json_metadata": "",
      "parent_author": "greymass",
      "parent_permlink": "the-future-of-the-greymass-wallet-beta-version-available-now",
      "permlink": "re-the-future-of-the-greymass-wallet-beta-version-available-now-20190521t164220",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-05-21T16:42:21",
  "trx_id": "f1222bc687784a5b43278c2086c2696b8d65a526",
  "trx_in_block": 16,
  "virtual_op": 0
}
2019/05/21 16:32:21
authorgreymass
permlinkthe-future-of-the-greymass-wallet-beta-version-available-now
voterv4vapid
weight2500 (25.00%)
Transaction InfoBlock #33106487/Trx 64ee5c77ddebcc1a736aad048ded73d2799c84ea
View Raw JSON Data
{
  "block": 33106487,
  "op": [
    "vote",
    {
      "author": "greymass",
      "permlink": "the-future-of-the-greymass-wallet-beta-version-available-now",
      "voter": "v4vapid",
      "weight": 2500
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-05-21T16:32:21",
  "trx_id": "64ee5c77ddebcc1a736aad048ded73d2799c84ea",
  "trx_in_block": 34,
  "virtual_op": 0
}
2019/05/21 16:10:27
authorgreymass
permlinkthe-future-of-the-greymass-wallet-beta-version-available-now
voterelowin
weight8000 (80.00%)
Transaction InfoBlock #33106049/Trx f4e365298841cf4b68d7f637c45cf8f03c7fc0dd
View Raw JSON Data
{
  "block": 33106049,
  "op": [
    "vote",
    {
      "author": "greymass",
      "permlink": "the-future-of-the-greymass-wallet-beta-version-available-now",
      "voter": "elowin",
      "weight": 8000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-05-21T16:10:27",
  "trx_id": "f4e365298841cf4b68d7f637c45cf8f03c7fc0dd",
  "trx_in_block": 49,
  "virtual_op": 0
}
2019/05/21 16:02:00
authorgreymass
permlinkthe-future-of-the-greymass-wallet-beta-version-available-now
voterlaissez-faire
weight10000 (100.00%)
Transaction InfoBlock #33105880/Trx da9f87f4217387d41960d3f3050c895d5f006f6e
View Raw JSON Data
{
  "block": 33105880,
  "op": [
    "vote",
    {
      "author": "greymass",
      "permlink": "the-future-of-the-greymass-wallet-beta-version-available-now",
      "voter": "laissez-faire",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-05-21T16:02:00",
  "trx_id": "da9f87f4217387d41960d3f3050c895d5f006f6e",
  "trx_in_block": 16,
  "virtual_op": 0
}
2019/05/21 16:01:57
authorgreymass
permlinkthe-future-of-the-greymass-wallet-beta-version-available-now
voterbluesniper
weight10 (0.10%)
Transaction InfoBlock #33105879/Trx 86171176d88e50f8b195355a1c0ad6b3d29e9406
View Raw JSON Data
{
  "block": 33105879,
  "op": [
    "vote",
    {
      "author": "greymass",
      "permlink": "the-future-of-the-greymass-wallet-beta-version-available-now",
      "voter": "bluesniper",
      "weight": 10
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-05-21T16:01:57",
  "trx_id": "86171176d88e50f8b195355a1c0ad6b3d29e9406",
  "trx_in_block": 24,
  "virtual_op": 0
}

Account Metadata

POSTING JSON METADATA
profile{"website":"https://greymass.com","profile_image":"https://pbs.twimg.com/profile_images/1121141392082964481/ccAzq3U1_400x400.png"}
JSON METADATA
profile{"website":"https://greymass.com","profile_image":"https://pbs.twimg.com/profile_images/1121141392082964481/ccAzq3U1_400x400.png"}
{
  "posting_json_metadata": {
    "profile": {
      "website": "https://greymass.com",
      "profile_image": "https://pbs.twimg.com/profile_images/1121141392082964481/ccAzq3U1_400x400.png"
    }
  },
  "json_metadata": {
    "profile": {
      "website": "https://greymass.com",
      "profile_image": "https://pbs.twimg.com/profile_images/1121141392082964481/ccAzq3U1_400x400.png"
    }
  }
}

Auth Keys

Owner
Single Signature
Public Keys
STM5KfPR7QEF3AzWzKiqRpdZTuKxgsKHKRVbzsPSUB1nHxpukzCgD1/1
Active
Single Signature
Public Keys
STM4yHvuvqGCtU8BuYcambbE7A6B9TF8FNyS4cx5Q1U6gsv4cT3FW1/1
Posting
Single Signature
Public Keys
STM6WGBtymZsu91xi2CBbCkSbF4ezHm47ELuP7fzFnGt4RAnjfRQE1/1
STM6edhNDj8W1XxRQUpLF8oq1fraJvg9X3zeGpw32drjEKKTACcoP1/1
STM6jcsejMKmH4DVBYeRgAjbRDwzKt8Bz8MXYVWnWn2kmeVxk3EPL1/1
App Permissions
Memo
STM6QcW4PukkhLmx3cTbppKf6Wnj7TbEAaWpGjwnGH5CRKfoWtLGd
{
  "owner": {
    "account_auths": [],
    "key_auths": [
      [
        "STM5KfPR7QEF3AzWzKiqRpdZTuKxgsKHKRVbzsPSUB1nHxpukzCgD",
        1
      ]
    ],
    "weight_threshold": 1
  },
  "active": {
    "account_auths": [],
    "key_auths": [
      [
        "STM4yHvuvqGCtU8BuYcambbE7A6B9TF8FNyS4cx5Q1U6gsv4cT3FW",
        1
      ]
    ],
    "weight_threshold": 1
  },
  "posting": {
    "account_auths": [
      [
        "jesta",
        1
      ],
      [
        "paxmagnus",
        1
      ],
      [
        "streemian",
        1
      ]
    ],
    "key_auths": [
      [
        "STM6WGBtymZsu91xi2CBbCkSbF4ezHm47ELuP7fzFnGt4RAnjfRQE",
        1
      ],
      [
        "STM6edhNDj8W1XxRQUpLF8oq1fraJvg9X3zeGpw32drjEKKTACcoP",
        1
      ],
      [
        "STM6jcsejMKmH4DVBYeRgAjbRDwzKt8Bz8MXYVWnWn2kmeVxk3EPL",
        1
      ]
    ],
    "weight_threshold": 1
  },
  "memo": "STM6QcW4PukkhLmx3cTbppKf6Wnj7TbEAaWpGjwnGH5CRKfoWtLGd"
}

Witness Votes

0 / 30
No active witness votes (Proxied to @jesta).
[]