Transaction: 393efe78b59abbced9c25108444196e1023abbe1

Included in block 19,833,530 at 2018/02/13 12:27:24 (UTC).

Transaction overview

Loading...
Transaction info
transaction_id 393efe78b59abbced9c25108444196e1023abbe1
ref_block_num 41,637
block_num19,833,530
ref_block_prefix 90,774,712
expiration2018/02/13T12:37:18
transaction_num 35
extensions[]
signatures 1f46c4caed61859e6ebb695930467db03d196caa244e801989dbdacd4454a51ed96f52d4e765b14f46dcda3138181ac0b38c495dee3091c424fb6556c49b1d4ac8
operations
comment
"parent_author":"jringo",<br>"parent_permlink":"a-superblock-for-pool-polls",<br>"author":"shmoogleosukami",<br>"permlink":"re-jringo-a-superblock-for-pool-polls-20180213t122719713z",<br>"title":"",<br>"body":"As discussed in the slack economics channel,<br> so long as we implement means to prevent abuse and\/or means to independently validate submitted pool data I'm all for it.\n\nI think the first option being the easiest to implement. \n\nGiven that having pool users being able to vote does outweight the risks of relying on trusting pool owners to calculate mag and provide the data without falsifying it,<br> It can be justified implementing some form of pool superblock.\n\nI personally would prefer keeping pool users from voting with mag simply as that is one of the downsides to being a pool users,<br> But that it only a justifiable way of thinking if being a solo miner was not so difficult.\n\nGiven that it would be some months before proposed fixes to staking would be implemented and we still need to have votes on said things it's sorta a catch 22 as to what you fix first and how.",<br>"json_metadata":" \"tags\":[\"gridcoin\" ,<br>\"app\":\"steemit\/0.1\" "
* The API used to generate this page is provided by @steemchiller.