VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS0.00%
Net Worth
13.842USD
HIVE
0.000HIVE
HBD
0.521HBD
Effective Power
79.497HP
├── Own HP
277.762HP
└── Outgoing DelegationsDeleg
-198.265HP
Detailed Balance
| HIVE | ||
| balance | 0.000HIVE | HIVE |
| market_balance | 0.000HIVE | HIVE |
| savings_balance | 0.000HIVE | HIVE |
| reward_hive_balance | 0.000HIVE | HIVE |
| HIVE POWER | ||
| Own HP | 277.762HP | HP |
| Delegated Out | 198.265HP | HP |
| Delegation In | 0.000HP | HP |
| Effective Power | 79.497HP | HP |
| Reward HP (pending) | 0.000HP | HP |
| HBD | ||
| hbd_balance | 0.521HBD | HBD |
| hbd_conversions | 0.000HBD | HBD |
| hbd_market_balance | 0.000HBD | HBD |
| savings_hbd_balance | 0.000HBD | HBD |
| reward_hbd_balance | 0.000HBD | HBD |
{
"balance": "0.000 HIVE",
"savings_balance": "0.000 HIVE",
"reward_hive_balance": "0.000 HIVE",
"vesting_shares": "450870.205844 VESTS",
"delegated_vesting_shares": "321828.655578 VESTS",
"received_vesting_shares": "0.000000 VESTS",
"hbd_balance": "0.521 HBD",
"savings_hbd_balance": "0.000 HBD",
"reward_hbd_balance": "0.000 HBD"
}Account Info
| name | blockchained |
| id | 126776 |
| rank | 0 |
| reputation | 0 |
| created | 2017-01-16T01:38:42 |
| recovery_account | smailer |
| proxy | None |
| invited_by | null |
| post_count | 744 |
| comment_count | 0 |
| lifetime_vote_count | 0 |
| witnesses_voted_for | 0 |
| last_post | 2021-06-21T11:38:27 |
| last_root_post | 2021-06-21T11:38:27 |
| last_vote_time | 2020-03-19T22:20:00 |
| proxied_vsf_votes | 0, 0, 0, 0 |
| can_vote | 1 |
| voting_power | 0 |
| delayed_votes | None |
| governance_vote_expiration_ts | 1969-12-31T23:59:59 |
| balance | 0.000 HIVE |
| savings_balance | 0.000 HIVE |
| hbd_balance | 0.521 HBD |
| savings_hbd_balance | 0.000 HBD |
| vesting_shares | 450870.205844 VESTS |
| delegated_vesting_shares | 321828.655578 VESTS |
| received_vesting_shares | 0.000000 VESTS |
| reward_vesting_balance | 0.000000 VESTS |
| vesting_balance | 0.000 HIVE |
| vesting_withdraw_rate | 0.000000 VESTS |
| next_vesting_withdrawal | 1969-12-31T23:59:59 |
| withdrawn | 0 |
| to_withdraw | 0 |
| withdraw_routes | 0 |
| savings_withdraw_requests | 0 |
| last_account_recovery | 1970-01-01T00:00:00 |
| reset_account | null |
| last_owner_update | 2017-01-16T01:44:00 |
| last_account_update | 2020-11-13T15:18:39 |
| mined | No |
| hbd_seconds | 0 |
| hbd_last_interest_payment | 2020-04-26T14:31:36 |
| savings_hbd_last_interest_payment | 1970-01-01T00:00:00 |
{
"active": {
"account_auths": [],
"key_auths": [
[
"STM7NDcAdmUXdep3T1sRJLi6JWXBrc1651LRZ1ty5pveUdmsXR7Qi",
1
]
],
"weight_threshold": 1
},
"balance": "0.000 HIVE",
"can_vote": true,
"comment_count": 0,
"created": "2017-01-16T01:38:42",
"curation_rewards": 660719,
"delayed_votes": [],
"delegated_vesting_shares": "321828.655578 VESTS",
"downvote_manabar": {
"current_mana": 32260387567,
"last_update_time": 1745955345
},
"governance_vote_expiration_ts": "1969-12-31T23:59:59",
"guest_bloggers": [],
"hbd_balance": "0.521 HBD",
"hbd_last_interest_payment": "2020-04-26T14:31:36",
"hbd_seconds": "0",
"hbd_seconds_last_update": "2020-04-26T14:31:36",
"id": 126776,
"json_metadata": "{\"profile\":{\"website\":\"https://golos.id/@blockchained\"}}",
"last_account_recovery": "1970-01-01T00:00:00",
"last_account_update": "2020-11-13T15:18:39",
"last_owner_update": "2017-01-16T01:44:00",
"last_post": "2021-06-21T11:38:27",
"last_root_post": "2021-06-21T11:38:27",
"last_vote_time": "2020-03-19T22:20:00",
"lifetime_vote_count": 0,
"market_history": [],
"memo_key": "STM8FzhiboKEgeeMkvp8SPuXCy9cb8TiuykztSQdzCB4ZTkqzhNgx",
"mined": false,
"name": "blockchained",
"next_vesting_withdrawal": "1969-12-31T23:59:59",
"open_recurrent_transfers": 0,
"other_history": [],
"owner": {
"account_auths": [],
"key_auths": [
[
"STM88v4ckBjZsKJ5vjhM1PcyPp2QVVTvGeVXNy99MgqXX9idHXcXv",
1
]
],
"weight_threshold": 1
},
"pending_claimed_accounts": 4,
"pending_transfers": 0,
"post_bandwidth": 10000,
"post_count": 744,
"post_history": [],
"post_voting_power": "129041.550266 VESTS",
"posting": {
"account_auths": [
[
"busy.app",
1
],
[
"dlive.app",
1
],
[
"dmania.app",
1
],
[
"memestagram-app",
1
],
[
"peakd.app",
1
],
[
"steempeak.app",
1
],
[
"streemian",
1
],
[
"utopian.app",
1
]
],
"key_auths": [
[
"STM6szSXTRJECqeA5Wb2jXD26ocvB88R5ZyiFo2YkSdm5cCBpQNR5",
1
]
],
"weight_threshold": 1
},
"posting_json_metadata": "{\"profile\":{\"profile_image\":\"https://i.imgur.com/RJjW8VP.png\",\"name\":\"BLOCKCHAINED\",\"about\":\"Decentralization is a product\",\"website\":\"https://rudex.org/\"}}",
"posting_rewards": 8472539,
"previous_owner_update": "1970-01-01T00:00:00",
"proxied_vsf_votes": [
0,
0,
0,
0
],
"proxy": "",
"received_vesting_shares": "0.000000 VESTS",
"recovery_account": "smailer",
"reputation": 0,
"reset_account": "null",
"reward_hbd_balance": "0.000 HBD",
"reward_hive_balance": "0.000 HIVE",
"reward_vesting_balance": "0.000000 VESTS",
"reward_vesting_hive": "0.000 HIVE",
"savings_balance": "0.000 HIVE",
"savings_hbd_balance": "0.000 HBD",
"savings_hbd_last_interest_payment": "1970-01-01T00:00:00",
"savings_hbd_seconds": "0",
"savings_hbd_seconds_last_update": "1970-01-01T00:00:00",
"savings_withdraw_requests": 0,
"tags_usage": [],
"to_withdraw": 0,
"transfer_history": [],
"vesting_balance": "0.000 HIVE",
"vesting_shares": "450870.205844 VESTS",
"vesting_withdraw_rate": "0.000000 VESTS",
"vote_history": [],
"voting_manabar": {
"current_mana": 129041550266,
"last_update_time": 1745955345
},
"voting_power": 0,
"withdraw_routes": 0,
"withdrawn": 0,
"witness_votes": [],
"witnesses_voted_for": 0,
"rank": 0
}Withdraw Routes
| Incoming | Outgoing |
|---|---|
Empty | Empty |
{
"incoming": [],
"outgoing": []
}From Date
To Date
blockchainedblockchain operation: delayed voting2025/05/29 19:35:21
blockchainedblockchain operation: delayed voting
2025/05/29 19:35:21
| voter | blockchained |
| votes | 47893417336 |
| Transaction Info | Block #96322490/Virtual Operation 4294967295:3 |
View Raw JSON Data
{
"block": 96322490,
"op": [
"delayed_voting",
{
"voter": "blockchained",
"votes": 47893417336
}
],
"op_in_trx": 3,
"timestamp": "2025-05-29T19:35:21",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": true
}blockchaineddelegated 72.294 HP to @marel2025/04/29 19:35:48
blockchaineddelegated 72.294 HP to @marel
2025/04/29 19:35:48
| delegatee | marel |
| delegator | blockchained |
| vesting shares | 117348.950986 VESTS |
| Transaction Info | Block #95459469/Trx f78a11e7507780ddaea579c0e240c317840e77f8 |
View Raw JSON Data
{
"block": 95459469,
"op": [
"delegate_vesting_shares",
{
"delegatee": "marel",
"delegator": "blockchained",
"vesting_shares": "117348.950986 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2025-04-29T19:35:48",
"trx_id": "f78a11e7507780ddaea579c0e240c317840e77f8",
"trx_in_block": 3,
"virtual_op": false
}blockchainedblockchain operation: transfer to vesting completed2025/04/29 19:35:24
blockchainedblockchain operation: transfer to vesting completed
2025/04/29 19:35:24
| from account | blockchained |
| hive vested | 28.569 HIVE |
| to account | blockchained |
| vesting shares received | 47893.417336 VESTS |
| Transaction Info | Block #95459461/Trx 93a7d76f73ed1844e2871cded8eee368121a8c4c |
View Raw JSON Data
{
"block": 95459461,
"op": [
"transfer_to_vesting_completed",
{
"from_account": "blockchained",
"hive_vested": "28.569 HIVE",
"to_account": "blockchained",
"vesting_shares_received": "47893.417336 VESTS"
}
],
"op_in_trx": 1,
"timestamp": "2025-04-29T19:35:24",
"trx_id": "93a7d76f73ed1844e2871cded8eee368121a8c4c",
"trx_in_block": 5,
"virtual_op": true
}blockchainedpowered up 28.569 HIVE to @blockchained2025/04/29 19:35:24
blockchainedpowered up 28.569 HIVE to @blockchained
2025/04/29 19:35:24
| amount | 28.569 HIVE |
| from | blockchained |
| to | blockchained |
| Transaction Info | Block #95459461/Trx 93a7d76f73ed1844e2871cded8eee368121a8c4c |
View Raw JSON Data
{
"block": 95459461,
"op": [
"transfer_to_vesting",
{
"amount": "28.569 HIVE",
"from": "blockchained",
"to": "blockchained"
}
],
"op_in_trx": 0,
"timestamp": "2025-04-29T19:35:24",
"trx_id": "93a7d76f73ed1844e2871cded8eee368121a8c4c",
"trx_in_block": 5,
"virtual_op": false
}therealwolfsent 0.002 HIVE to @blockchained- "Hey there blockchained. I hope you don’t mind this short message, but I wanted to quickly share this update with you on my Hive-related work. For the past 7 years, I've been deeply committed to Hive, ..."2024/11/14 16:12:09
therealwolfsent 0.002 HIVE to @blockchained- "Hey there blockchained. I hope you don’t mind this short message, but I wanted to quickly share this update with you on my Hive-related work. For the past 7 years, I've been deeply committed to Hive, ..."
2024/11/14 16:12:09
| amount | 0.002 HIVE |
| from | therealwolf |
| memo | Hey there blockchained. I hope you don’t mind this short message, but I wanted to quickly share this update with you on my Hive-related work. For the past 7 years, I've been deeply committed to Hive, working on projects like hive.io, vessel, dhive & more to strengthen our community, while providing reliable witness infrastructure to secure our blockchain. Recently, I've released an upgraded witness toolkit (peakd.com/@therealwolf/major-hive-witness-essentials-upgrade-v2) and celebrated 7+ years on Hive (peakd.com/@therealwolf/year-8). If you'd like to support my work, I'd be honored to have your witness vote. Thank you! PS: You can vote for me here: peakd.com/witnesses |
| to | blockchained |
| Transaction Info | Block #90682544/Trx 1f69e3842ee152976e983338cb0be8871778dad0 |
View Raw JSON Data
{
"block": 90682544,
"op": [
"transfer",
{
"amount": "0.002 HIVE",
"from": "therealwolf",
"memo": "Hey there blockchained. I hope you don’t mind this short message, but I wanted to quickly share this update with you on my Hive-related work. For the past 7 years, I've been deeply committed to Hive, working on projects like hive.io, vessel, dhive & more to strengthen our community, while providing reliable witness infrastructure to secure our blockchain. Recently, I've released an upgraded witness toolkit (peakd.com/@therealwolf/major-hive-witness-essentials-upgrade-v2) and celebrated 7+ years on Hive (peakd.com/@therealwolf/year-8). If you'd like to support my work, I'd be honored to have your witness vote. Thank you! PS: You can vote for me here: peakd.com/witnesses",
"to": "blockchained"
}
],
"op_in_trx": 7,
"timestamp": "2024-11-14T16:12:09",
"trx_id": "1f69e3842ee152976e983338cb0be8871778dad0",
"trx_in_block": 28,
"virtual_op": false
}fractalnodeunvoted witness @blockchained2024/02/29 19:55:33
fractalnodeunvoted witness @blockchained
2024/02/29 19:55:33
| account | fractalnode |
| approve | false |
| witness | blockchained |
| Transaction Info | Block #83240729/Trx 2698e3d4b8259b6b51b6b3d89e4f75523a61fdbe |
View Raw JSON Data
{
"block": 83240729,
"op": [
"account_witness_vote",
{
"account": "fractalnode",
"approve": false,
"witness": "blockchained"
}
],
"op_in_trx": 0,
"timestamp": "2024-02-29T19:55:33",
"trx_id": "2698e3d4b8259b6b51b6b3d89e4f75523a61fdbe",
"trx_in_block": 26,
"virtual_op": false
}ratelunvoted witness @blockchained2024/01/29 02:33:36
ratelunvoted witness @blockchained
2024/01/29 02:33:36
| account | ratel |
| approve | false |
| witness | blockchained |
| Transaction Info | Block #82328313/Trx cf6a6a5d65031feae8ab2a37873938896a44207c |
View Raw JSON Data
{
"block": 82328313,
"op": [
"account_witness_vote",
{
"account": "ratel",
"approve": false,
"witness": "blockchained"
}
],
"op_in_trx": 0,
"timestamp": "2024-01-29T02:33:36",
"trx_id": "cf6a6a5d65031feae8ab2a37873938896a44207c",
"trx_in_block": 14,
"virtual_op": false
}howosent 0.002 HIVE to @blockchained- "Hey @blockchained I am launching a new solo witness and am looking for support. If you are unfamiliar with what I do, I wrote a post announcing my witness here: https://peakd.com/witness/@howo/annouci..."2023/11/30 19:51:42
howosent 0.002 HIVE to @blockchained- "Hey @blockchained I am launching a new solo witness and am looking for support. If you are unfamiliar with what I do, I wrote a post announcing my witness here: https://peakd.com/witness/@howo/annouci..."
2023/11/30 19:51:42
| amount | 0.002 HIVE |
| from | howo |
| memo | Hey @blockchained I am launching a new solo witness and am looking for support. If you are unfamiliar with what I do, I wrote a post announcing my witness here: https://peakd.com/witness/@howo/annoucing-my-solo-witness. The tl;dr is that I've been on Hive for 6 years and for the past 4 I've been working as a core developer meaning I'm working directly on the blockchain code to add features. You might have interacted with some of them already like RC delegations, recurrent transfers or more recently I've been working on updating communities (new update soon !). If you want to support me, could you vote for me as a witness ? You can do it on this page https://peakd.com/me/witnesses. Thank you ! |
| to | blockchained |
| Transaction Info | Block #80623207/Trx c11d99b44e3622a5c011a955f146c021fef66bd6 |
View Raw JSON Data
{
"block": 80623207,
"op": [
"transfer",
{
"amount": "0.002 HIVE",
"from": "howo",
"memo": "Hey @blockchained I am launching a new solo witness and am looking for support. If you are unfamiliar with what I do, I wrote a post announcing my witness here: https://peakd.com/witness/@howo/annoucing-my-solo-witness. The tl;dr is that I've been on Hive for 6 years and for the past 4 I've been working as a core developer meaning I'm working directly on the blockchain code to add features. You might have interacted with some of them already like RC delegations, recurrent transfers or more recently I've been working on updating communities (new update soon !). If you want to support me, could you vote for me as a witness ? You can do it on this page https://peakd.com/me/witnesses. Thank you !",
"to": "blockchained"
}
],
"op_in_trx": 0,
"timestamp": "2023-11-30T19:51:42",
"trx_id": "c11d99b44e3622a5c011a955f146c021fef66bd6",
"trx_in_block": 25,
"virtual_op": false
}sharkerunvoted witness @blockchained2023/07/31 13:25:24
sharkerunvoted witness @blockchained
2023/07/31 13:25:24
| account | sharker |
| approve | false |
| witness | blockchained |
| Transaction Info | Block #77105614/Trx de2bb1862c9a38449b4367375092210712a43fa3 |
View Raw JSON Data
{
"block": 77105614,
"op": [
"account_witness_vote",
{
"account": "sharker",
"approve": false,
"witness": "blockchained"
}
],
"op_in_trx": 0,
"timestamp": "2023-07-31T13:25:24",
"trx_id": "de2bb1862c9a38449b4367375092210712a43fa3",
"trx_in_block": 32,
"virtual_op": false
}howosent 0.001 HBD to @blockchained- "Hi ! I've been a core developer on hive for three years now, working on features that are now powering the chain and improving user experience like RC delegations or recurrent transfers and currently ..."2023/04/22 16:30:30
howosent 0.001 HBD to @blockchained- "Hi ! I've been a core developer on hive for three years now, working on features that are now powering the chain and improving user experience like RC delegations or recurrent transfers and currently ..."
2023/04/22 16:30:30
| amount | 0.001 HBD |
| from | howo |
| memo | Hi ! I've been a core developer on hive for three years now, working on features that are now powering the chain and improving user experience like RC delegations or recurrent transfers and currently wrapping up some features that will go live in hard fork 27. I'm also hosting the monthly core dev meeting. I would like to carry on working for hive for a fourth year. I am looking for support on my renewed proposal as the current one will expire soon. It's the same deal as the last one. Could you review it and maybe vote on it if it's worth your support ? https://peakd.com/me/proposals/261 Thanks a lot ! |
| to | blockchained |
| Transaction Info | Block #74233319/Trx 01810531fbca222a3d400d862321323dccd38ed1 |
View Raw JSON Data
{
"block": 74233319,
"op": [
"transfer",
{
"amount": "0.001 HBD",
"from": "howo",
"memo": "Hi ! I've been a core developer on hive for three years now, working on features that are now powering the chain and improving user experience like RC delegations or recurrent transfers and currently wrapping up some features that will go live in hard fork 27. I'm also hosting the monthly core dev meeting. I would like to carry on working for hive for a fourth year. I am looking for support on my renewed proposal as the current one will expire soon. It's the same deal as the last one. Could you review it and maybe vote on it if it's worth your support ? https://peakd.com/me/proposals/261 Thanks a lot !",
"to": "blockchained"
}
],
"op_in_trx": 0,
"timestamp": "2023-04-22T16:30:30",
"trx_id": "01810531fbca222a3d400d862321323dccd38ed1",
"trx_in_block": 3,
"virtual_op": false
}sponge-bobunvoted witness @blockchained2023/04/16 15:28:12
sponge-bobunvoted witness @blockchained
2023/04/16 15:28:12
| account | sponge-bob |
| approve | false |
| witness | blockchained |
| Transaction Info | Block #74059813/Trx fbdaee10b2a53cf0c0de46f988a0a5d7d94d648e |
View Raw JSON Data
{
"block": 74059813,
"op": [
"account_witness_vote",
{
"account": "sponge-bob",
"approve": false,
"witness": "blockchained"
}
],
"op_in_trx": 0,
"timestamp": "2023-04-16T15:28:12",
"trx_id": "fbdaee10b2a53cf0c0de46f988a0a5d7d94d648e",
"trx_in_block": 73,
"virtual_op": false
}orlandogonzalezunvoted witness @blockchained2023/04/13 21:48:39
orlandogonzalezunvoted witness @blockchained
2023/04/13 21:48:39
| account | orlandogonzalez |
| approve | false |
| witness | blockchained |
| Transaction Info | Block #73981087/Trx 606ab2b10b726398bf3c632b9b17e26289b6d994 |
View Raw JSON Data
{
"block": 73981087,
"op": [
"account_witness_vote",
{
"account": "orlandogonzalez",
"approve": false,
"witness": "blockchained"
}
],
"op_in_trx": 0,
"timestamp": "2023-04-13T21:48:39",
"trx_id": "606ab2b10b726398bf3c632b9b17e26289b6d994",
"trx_in_block": 1,
"virtual_op": false
}earn.hivesent 0.001 HIVE to @blockchained- "Did you know that you can get rewarded for your witness vote? Cast your witness vote on @earn.hive and start to receive HIVE tokens everyday."2023/01/05 00:05:30
earn.hivesent 0.001 HIVE to @blockchained- "Did you know that you can get rewarded for your witness vote? Cast your witness vote on @earn.hive and start to receive HIVE tokens everyday."
2023/01/05 00:05:30
| amount | 0.001 HIVE |
| from | earn.hive |
| memo | Did you know that you can get rewarded for your witness vote? Cast your witness vote on @earn.hive and start to receive HIVE tokens everyday. |
| to | blockchained |
| Transaction Info | Block #71135786/Trx 210dd0d8bf52216de45cc23d9571fe8e5e3f09e9 |
View Raw JSON Data
{
"block": 71135786,
"op": [
"transfer",
{
"amount": "0.001 HIVE",
"from": "earn.hive",
"memo": "Did you know that you can get rewarded for your witness vote? Cast your witness vote on @earn.hive and start to receive HIVE tokens everyday.",
"to": "blockchained"
}
],
"op_in_trx": 0,
"timestamp": "2023-01-05T00:05:30",
"trx_id": "210dd0d8bf52216de45cc23d9571fe8e5e3f09e9",
"trx_in_block": 2,
"virtual_op": false
}gomeravibzliberated governance voting proxy2022/10/28 10:07:06
gomeravibzliberated governance voting proxy
2022/10/28 10:07:06
| account | gomeravibz |
| proxy | blockchained |
| Transaction Info | Block #69162825/Virtual Operation 4294967295:2 |
View Raw JSON Data
{
"block": 69162825,
"op": [
"proxy_cleared",
{
"account": "gomeravibz",
"proxy": "blockchained"
}
],
"op_in_trx": 2,
"timestamp": "2022-10-28T10:07:06",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": true
}smailerliberated governance voting proxy2022/10/22 15:21:12
smailerliberated governance voting proxy
2022/10/22 15:21:12
| account | smailer |
| proxy | blockchained |
| Transaction Info | Block #68996582/Virtual Operation 4294967295:7 |
View Raw JSON Data
{
"block": 68996582,
"op": [
"proxy_cleared",
{
"account": "smailer",
"proxy": "blockchained"
}
],
"op_in_trx": 7,
"timestamp": "2022-10-22T15:21:12",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": true
}blockchainedaccount expired: @blockchained2022/09/13 07:54:27
blockchainedaccount expired: @blockchained
2022/09/13 07:54:27
| account | blockchained |
| Transaction Info | Block #67866836/Virtual Operation 4294967295:2 |
View Raw JSON Data
{
"block": 67866836,
"op": [
"expired_account_notification",
{
"account": "blockchained"
}
],
"op_in_trx": 2,
"timestamp": "2022-09-13T07:54:27",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": true
}angarliberated governance voting proxy2022/09/11 15:10:45
angarliberated governance voting proxy
2022/09/11 15:10:45
| account | angar |
| proxy | blockchained |
| Transaction Info | Block #67818058/Virtual Operation 4294967295:3 |
View Raw JSON Data
{
"block": 67818058,
"op": [
"proxy_cleared",
{
"account": "angar",
"proxy": "blockchained"
}
],
"op_in_trx": 3,
"timestamp": "2022-09-11T15:10:45",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": true
}catomoonunvoted witness @blockchained2022/08/05 12:55:51
catomoonunvoted witness @blockchained
2022/08/05 12:55:51
| account | catomoon |
| approve | false |
| witness | blockchained |
| Transaction Info | Block #66752765/Trx a41e67457cb35b2aeb4bd81d4d72bab9e0bd18f5 |
View Raw JSON Data
{
"block": 66752765,
"op": [
"account_witness_vote",
{
"account": "catomoon",
"approve": false,
"witness": "blockchained"
}
],
"op_in_trx": 0,
"timestamp": "2022-08-05T12:55:51",
"trx_id": "a41e67457cb35b2aeb4bd81d4d72bab9e0bd18f5",
"trx_in_block": 61,
"virtual_op": false
}blockainedliberated governance voting proxy2022/08/01 03:31:45
blockainedliberated governance voting proxy
2022/08/01 03:31:45
| account | blockained |
| proxy | blockchained |
| Transaction Info | Block #66626495/Virtual Operation 4294967295:4 |
View Raw JSON Data
{
"block": 66626495,
"op": [
"proxy_cleared",
{
"account": "blockained",
"proxy": "blockchained"
}
],
"op_in_trx": 4,
"timestamp": "2022-08-01T03:31:45",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": true
}marco.worldliberated governance voting proxy2022/08/01 03:31:12
marco.worldliberated governance voting proxy
2022/08/01 03:31:12
| account | marco.world |
| proxy | blockchained |
| Transaction Info | Block #66626484/Virtual Operation 4294967295:2 |
View Raw JSON Data
{
"block": 66626484,
"op": [
"proxy_cleared",
{
"account": "marco.world",
"proxy": "blockchained"
}
],
"op_in_trx": 2,
"timestamp": "2022-08-01T03:31:12",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": true
}marelliberated governance voting proxy2022/08/01 03:29:51
marelliberated governance voting proxy
2022/08/01 03:29:51
| account | marel |
| proxy | blockchained |
| Transaction Info | Block #66626457/Virtual Operation 4294967295:2 |
View Raw JSON Data
{
"block": 66626457,
"op": [
"proxy_cleared",
{
"account": "marel",
"proxy": "blockchained"
}
],
"op_in_trx": 2,
"timestamp": "2022-08-01T03:29:51",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": true
}criticalkushliberated governance voting proxy2022/07/27 05:17:00
criticalkushliberated governance voting proxy
2022/07/27 05:17:00
| account | criticalkush |
| proxy | blockchained |
| Transaction Info | Block #66484867/Virtual Operation 4294967295:2 |
View Raw JSON Data
{
"block": 66484867,
"op": [
"proxy_cleared",
{
"account": "criticalkush",
"proxy": "blockchained"
}
],
"op_in_trx": 2,
"timestamp": "2022-07-27T05:17:00",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": true
}whalepunkliberated governance voting proxy2022/07/27 05:16:00
whalepunkliberated governance voting proxy
2022/07/27 05:16:00
| account | whalepunk |
| proxy | blockchained |
| Transaction Info | Block #66484847/Virtual Operation 4294967295:3 |
View Raw JSON Data
{
"block": 66484847,
"op": [
"proxy_cleared",
{
"account": "whalepunk",
"proxy": "blockchained"
}
],
"op_in_trx": 3,
"timestamp": "2022-07-27T05:16:00",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": true
}zaebarsliberated governance voting proxy2022/07/27 05:14:45
zaebarsliberated governance voting proxy
2022/07/27 05:14:45
| account | zaebars |
| proxy | blockchained |
| Transaction Info | Block #66484822/Virtual Operation 4294967295:2 |
View Raw JSON Data
{
"block": 66484822,
"op": [
"proxy_cleared",
{
"account": "zaebars",
"proxy": "blockchained"
}
],
"op_in_trx": 2,
"timestamp": "2022-07-27T05:14:45",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": true
}rusteemitblogliberated governance voting proxy2022/07/27 05:13:57
rusteemitblogliberated governance voting proxy
2022/07/27 05:13:57
| account | rusteemitblog |
| proxy | blockchained |
| Transaction Info | Block #66484806/Virtual Operation 4294967295:3 |
View Raw JSON Data
{
"block": 66484806,
"op": [
"proxy_cleared",
{
"account": "rusteemitblog",
"proxy": "blockchained"
}
],
"op_in_trx": 3,
"timestamp": "2022-07-27T05:13:57",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": true
}free-mindliberated governance voting proxy2022/07/09 18:59:15
free-mindliberated governance voting proxy
2022/07/09 18:59:15
| account | free-mind |
| proxy | blockchained |
| Transaction Info | Block #65984183/Virtual Operation 4294967295:3 |
View Raw JSON Data
{
"block": 65984183,
"op": [
"proxy_cleared",
{
"account": "free-mind",
"proxy": "blockchained"
}
],
"op_in_trx": 3,
"timestamp": "2022-07-09T18:59:15",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": true
}tommyl33unvoted witness @blockchained2022/04/25 06:23:21
tommyl33unvoted witness @blockchained
2022/04/25 06:23:21
| account | tommyl33 |
| approve | false |
| witness | blockchained |
| Transaction Info | Block #63813788/Trx 3abf0fef005d7080d0b4899f85598394dbf885bd |
View Raw JSON Data
{
"block": 63813788,
"op": [
"account_witness_vote",
{
"account": "tommyl33",
"approve": false,
"witness": "blockchained"
}
],
"op_in_trx": 0,
"timestamp": "2022-04-25T06:23:21",
"trx_id": "3abf0fef005d7080d0b4899f85598394dbf885bd",
"trx_in_block": 79,
"virtual_op": false
}howosent 0.001 HIVE to @blockchained- "Hi, I have been working for the past two years as a core developer on hive. I worked on a lot of things last year some which went live in hard fork 25 already or will go live soon with hard fork 26. T..."2022/04/09 03:20:03
howosent 0.001 HIVE to @blockchained- "Hi, I have been working for the past two years as a core developer on hive. I worked on a lot of things last year some which went live in hard fork 25 already or will go live soon with hard fork 26. T..."
2022/04/09 03:20:03
| amount | 0.001 HIVE |
| from | howo |
| memo | Hi, I have been working for the past two years as a core developer on hive. I worked on a lot of things last year some which went live in hard fork 25 already or will go live soon with hard fork 26. To name a few, RC delegations, recurrent transfers or communities V2. I would love to continue working on hive for a third year on the next hard fork, communities and everything else. I am looking for support on my renewed proposal as the current one will expire soon. Could you review it and maybe vote on it if it's worth your support ? https://peakd.com/me/proposals/214 Thanks a lot ! |
| to | blockchained |
| Transaction Info | Block #63350569/Trx 27cc4076dc1e33b2bfb2e35b7b686f9f178b2fdf |
View Raw JSON Data
{
"block": 63350569,
"op": [
"transfer",
{
"amount": "0.001 HIVE",
"from": "howo",
"memo": "Hi, I have been working for the past two years as a core developer on hive. I worked on a lot of things last year some which went live in hard fork 25 already or will go live soon with hard fork 26. To name a few, RC delegations, recurrent transfers or communities V2. I would love to continue working on hive for a third year on the next hard fork, communities and everything else. I am looking for support on my renewed proposal as the current one will expire soon. Could you review it and maybe vote on it if it's worth your support ? https://peakd.com/me/proposals/214 Thanks a lot !",
"to": "blockchained"
}
],
"op_in_trx": 0,
"timestamp": "2022-04-09T03:20:03",
"trx_id": "27cc4076dc1e33b2bfb2e35b7b686f9f178b2fdf",
"trx_in_block": 74,
"virtual_op": false
}blockchainedclaimed reward balance: 0.509 HBD, 2.529 HP2022/01/19 17:39:54
blockchainedclaimed reward balance: 0.509 HBD, 2.529 HP
2022/01/19 17:39:54
| account | blockchained |
| reward hbd | 0.509 HBD |
| reward hive | 0.000 HIVE |
| reward vests | 4104.917718 VESTS |
| Transaction Info | Block #61070397/Trx 62e34f5e86817b6bfc37e09667c2051175dda918 |
View Raw JSON Data
{
"block": 61070397,
"op": [
"claim_reward_balance",
{
"account": "blockchained",
"reward_hbd": "0.509 HBD",
"reward_hive": "0.000 HIVE",
"reward_vests": "4104.917718 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2022-01-19T17:39:54",
"trx_id": "62e34f5e86817b6bfc37e09667c2051175dda918",
"trx_in_block": 54,
"virtual_op": false
}hebrewunvoted witness @blockchained2022/01/17 02:03:24
hebrewunvoted witness @blockchained
2022/01/17 02:03:24
| account | hebrew |
| approve | false |
| witness | blockchained |
| Transaction Info | Block #60994245/Trx 170ef8e410ef3499e920ed21b2a156455b6ebf97 |
View Raw JSON Data
{
"block": 60994245,
"op": [
"account_witness_vote",
{
"account": "hebrew",
"approve": false,
"witness": "blockchained"
}
],
"op_in_trx": 0,
"timestamp": "2022-01-17T02:03:24",
"trx_id": "170ef8e410ef3499e920ed21b2a156455b6ebf97",
"trx_in_block": 50,
"virtual_op": false
}ranesa70unvoted witness @blockchained2021/10/26 15:57:21
ranesa70unvoted witness @blockchained
2021/10/26 15:57:21
| account | ranesa70 |
| approve | false |
| witness | blockchained |
| Transaction Info | Block #58627044/Trx 6c7851c0e7b5c8c729fa3ffab5d7b8e5bc22c4e7 |
View Raw JSON Data
{
"block": 58627044,
"op": [
"account_witness_vote",
{
"account": "ranesa70",
"approve": false,
"witness": "blockchained"
}
],
"op_in_trx": 0,
"timestamp": "2021-10-26T15:57:21",
"trx_id": "6c7851c0e7b5c8c729fa3ffab5d7b8e5bc22c4e7",
"trx_in_block": 32,
"virtual_op": false
}marelchanged recovery account to @blockchained2021/10/14 21:31:27
marelchanged recovery account to @blockchained
2021/10/14 21:31:27
| account | marel |
| new recovery account | blockchained |
| old recovery account | steem |
| Transaction Info | Block #58288967/Virtual Operation 4294967295:4 |
View Raw JSON Data
{
"block": 58288967,
"op": [
"changed_recovery_account",
{
"account": "marel",
"new_recovery_account": "blockchained",
"old_recovery_account": "steem"
}
],
"op_in_trx": 4,
"timestamp": "2021-10-14T21:31:27",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": true
}on0tolechanged recovery account to @blockchained2021/09/07 20:31:06
on0tolechanged recovery account to @blockchained
2021/09/07 20:31:06
| account | on0tole |
| new recovery account | blockchained |
| old recovery account | steem |
| Transaction Info | Block #57224770/Virtual Operation 4294967295:2 |
View Raw JSON Data
{
"block": 57224770,
"op": [
"changed_recovery_account",
{
"account": "on0tole",
"new_recovery_account": "blockchained",
"old_recovery_account": "steem"
}
],
"op_in_trx": 2,
"timestamp": "2021-09-07T20:31:06",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": true
}blockchainedupdated payout for bitshares-drama2021/06/28 11:38:27
blockchainedupdated payout for bitshares-drama
2021/06/28 11:38:27
| author | blockchained |
| permlink | bitshares-drama |
| Transaction Info | Block #55175517/Virtual Operation 4294967295:10 |
View Raw JSON Data
{
"block": 55175517,
"op": [
"comment_payout_update",
{
"author": "blockchained",
"permlink": "bitshares-drama"
}
],
"op_in_trx": 10,
"timestamp": "2021-06-28T11:38:27",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": true
}blockchainedreceived 1.937 HBD reward share for bitshares-drama2021/06/28 11:38:27
blockchainedreceived 1.937 HBD reward share for bitshares-drama
2021/06/28 11:38:27
| author | blockchained |
| author rewards | 3958 |
| beneficiary payout value | 0.000 HBD |
| curator payout value | 0.962 HBD |
| payout | 1.937 HBD |
| permlink | bitshares-drama |
| total payout value | 0.974 HBD |
| Transaction Info | Block #55175517/Virtual Operation 4294967295:9 |
View Raw JSON Data
{
"block": 55175517,
"op": [
"comment_reward",
{
"author": "blockchained",
"author_rewards": 3958,
"beneficiary_payout_value": "0.000 HBD",
"curator_payout_value": "0.962 HBD",
"payout": "1.937 HBD",
"permlink": "bitshares-drama",
"total_payout_value": "0.974 HBD"
}
],
"op_in_trx": 9,
"timestamp": "2021-06-28T11:38:27",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": true
}blockchainedreceived 0.487 HBD, 2.291 HP author reward for @blockchained / bitshares-drama2021/06/28 11:38:27
blockchainedreceived 0.487 HBD, 2.291 HP author reward for @blockchained / bitshares-drama
2021/06/28 11:38:27
| author | blockchained |
| curators vesting payout | 7339.606313 VESTS |
| hbd payout | 0.487 HBD |
| hive payout | 0.000 HIVE |
| payout must be claimed | true |
| permlink | bitshares-drama |
| vesting payout | 3718.658703 VESTS |
| Transaction Info | Block #55175517/Virtual Operation 4294967295:8 |
View Raw JSON Data
{
"block": 55175517,
"op": [
"author_reward",
{
"author": "blockchained",
"curators_vesting_payout": "7339.606313 VESTS",
"hbd_payout": "0.487 HBD",
"hive_payout": "0.000 HIVE",
"payout_must_be_claimed": true,
"permlink": "bitshares-drama",
"vesting_payout": "3718.658703 VESTS"
}
],
"op_in_trx": 8,
"timestamp": "2021-06-28T11:38:27",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": true
}blockchainedcustom json: peakd_notify2021/06/23 17:28:27
blockchainedcustom json: peakd_notify
2021/06/23 17:28:27
| id | peakd_notify |
| json | {"action":"markAsRead","date":"2021-06-23T17:26:22"} |
| required auths | [] |
| required posting auths | ["blockchained"] |
| Transaction Info | Block #55038716/Trx fa7e9a1c9a78672707ad3174e8d58f41e5faa197 |
View Raw JSON Data
{
"block": 55038716,
"op": [
"custom_json",
{
"id": "peakd_notify",
"json": "{\"action\":\"markAsRead\",\"date\":\"2021-06-23T17:26:22\"}",
"required_auths": [],
"required_posting_auths": [
"blockchained"
]
}
],
"op_in_trx": 1,
"timestamp": "2021-06-23T17:28:27",
"trx_id": "fa7e9a1c9a78672707ad3174e8d58f41e5faa197",
"trx_in_block": 11,
"virtual_op": false
}blockchainedcustom json: notify2021/06/23 17:28:27
blockchainedcustom json: notify
2021/06/23 17:28:27
| id | notify |
| json | ["setLastRead",{"date":"2021-06-23T17:26:22"}] |
| required auths | [] |
| required posting auths | ["blockchained"] |
| Transaction Info | Block #55038716/Trx fa7e9a1c9a78672707ad3174e8d58f41e5faa197 |
View Raw JSON Data
{
"block": 55038716,
"op": [
"custom_json",
{
"id": "notify",
"json": "[\"setLastRead\",{\"date\":\"2021-06-23T17:26:22\"}]",
"required_auths": [],
"required_posting_auths": [
"blockchained"
]
}
],
"op_in_trx": 0,
"timestamp": "2021-06-23T17:28:27",
"trx_id": "fa7e9a1c9a78672707ad3174e8d58f41e5faa197",
"trx_in_block": 11,
"virtual_op": false
}grider123effective vote applied for @blockchained / bitshares-drama2021/06/22 18:53:39
grider123effective vote applied for @blockchained / bitshares-drama
2021/06/22 18:53:39
| author | blockchained |
| pending payout | 2.122 HBD |
| permlink | bitshares-drama |
| rshares | 4478625129 |
| total vote weight | 1749881 |
| voter | grider123 |
| weight | 1090 (10.90%) |
| Transaction Info | Block #55011654/Trx 6433a36b23520e8205540a01e7b1215f192f824c |
View Raw JSON Data
{
"block": 55011654,
"op": [
"effective_comment_vote",
{
"author": "blockchained",
"pending_payout": "2.122 HBD",
"permlink": "bitshares-drama",
"rshares": 4478625129,
"total_vote_weight": 1749881,
"voter": "grider123",
"weight": 1090
}
],
"op_in_trx": 1,
"timestamp": "2021-06-22T18:53:39",
"trx_id": "6433a36b23520e8205540a01e7b1215f192f824c",
"trx_in_block": 36,
"virtual_op": true
}grider123upvoted (100.00%) @blockchained / bitshares-drama2021/06/22 18:53:39
grider123upvoted (100.00%) @blockchained / bitshares-drama
2021/06/22 18:53:39
| author | blockchained |
| permlink | bitshares-drama |
| voter | grider123 |
| weight | 10000 (100.00%) |
| Transaction Info | Block #55011654/Trx 6433a36b23520e8205540a01e7b1215f192f824c |
View Raw JSON Data
{
"block": 55011654,
"op": [
"vote",
{
"author": "blockchained",
"permlink": "bitshares-drama",
"voter": "grider123",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2021-06-22T18:53:39",
"trx_id": "6433a36b23520e8205540a01e7b1215f192f824c",
"trx_in_block": 36,
"virtual_op": false
}vortaceffective vote applied for @blockchained / bitshares-drama2021/06/22 18:53:30
vortaceffective vote applied for @blockchained / bitshares-drama
2021/06/22 18:53:30
| author | blockchained |
| pending payout | 2.120 HBD |
| permlink | bitshares-drama |
| rshares | 5625078325618 |
| total vote weight | 1748791 |
| voter | vortac |
| weight | 1718123 |
| Transaction Info | Block #55011651/Trx 4c02ed6e846e4e6c6af73233d0635ab33291055c |
View Raw JSON Data
{
"block": 55011651,
"op": [
"effective_comment_vote",
{
"author": "blockchained",
"pending_payout": "2.120 HBD",
"permlink": "bitshares-drama",
"rshares": 5625078325618,
"total_vote_weight": 1748791,
"voter": "vortac",
"weight": 1718123
}
],
"op_in_trx": 1,
"timestamp": "2021-06-22T18:53:30",
"trx_id": "4c02ed6e846e4e6c6af73233d0635ab33291055c",
"trx_in_block": 33,
"virtual_op": true
}vortacupvoted (100.00%) @blockchained / bitshares-drama2021/06/22 18:53:30
vortacupvoted (100.00%) @blockchained / bitshares-drama
2021/06/22 18:53:30
| author | blockchained |
| permlink | bitshares-drama |
| voter | vortac |
| weight | 10000 (100.00%) |
| Transaction Info | Block #55011651/Trx 4c02ed6e846e4e6c6af73233d0635ab33291055c |
View Raw JSON Data
{
"block": 55011651,
"op": [
"vote",
{
"author": "blockchained",
"permlink": "bitshares-drama",
"voter": "vortac",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2021-06-22T18:53:30",
"trx_id": "4c02ed6e846e4e6c6af73233d0635ab33291055c",
"trx_in_block": 33,
"virtual_op": false
}jugnooeffective vote applied for @blockchained / bitshares-drama2021/06/21 15:48:27
jugnooeffective vote applied for @blockchained / bitshares-drama
2021/06/21 15:48:27
| author | blockchained |
| pending payout | 0.018 HBD |
| permlink | bitshares-drama |
| rshares | 625151617 |
| total vote weight | 30668 |
| voter | jugnoo |
| weight | 308 (3.08%) |
| Transaction Info | Block #54979186/Trx c1df5ca03d17c5dd8e97b80660b9938684184c54 |
View Raw JSON Data
{
"block": 54979186,
"op": [
"effective_comment_vote",
{
"author": "blockchained",
"pending_payout": "0.018 HBD",
"permlink": "bitshares-drama",
"rshares": 625151617,
"total_vote_weight": 30668,
"voter": "jugnoo",
"weight": 308
}
],
"op_in_trx": 1,
"timestamp": "2021-06-21T15:48:27",
"trx_id": "c1df5ca03d17c5dd8e97b80660b9938684184c54",
"trx_in_block": 32,
"virtual_op": true
}jugnooupvoted (100.00%) @blockchained / bitshares-drama2021/06/21 15:48:27
jugnooupvoted (100.00%) @blockchained / bitshares-drama
2021/06/21 15:48:27
| author | blockchained |
| permlink | bitshares-drama |
| voter | jugnoo |
| weight | 10000 (100.00%) |
| Transaction Info | Block #54979186/Trx c1df5ca03d17c5dd8e97b80660b9938684184c54 |
View Raw JSON Data
{
"block": 54979186,
"op": [
"vote",
{
"author": "blockchained",
"permlink": "bitshares-drama",
"voter": "jugnoo",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2021-06-21T15:48:27",
"trx_id": "c1df5ca03d17c5dd8e97b80660b9938684184c54",
"trx_in_block": 32,
"virtual_op": false
}duekieeffective vote applied for @blockchained / bitshares-drama2021/06/21 13:45:03
duekieeffective vote applied for @blockchained / bitshares-drama
2021/06/21 13:45:03
| author | blockchained |
| pending payout | 0.017 HBD |
| permlink | bitshares-drama |
| rshares | 280536525 |
| total vote weight | 30360 |
| voter | duekie |
| weight | 138 (1.38%) |
| Transaction Info | Block #54976721/Trx d4f2d63d227d67af47e3124fcf7737e23c3a09ed |
View Raw JSON Data
{
"block": 54976721,
"op": [
"effective_comment_vote",
{
"author": "blockchained",
"pending_payout": "0.017 HBD",
"permlink": "bitshares-drama",
"rshares": 280536525,
"total_vote_weight": 30360,
"voter": "duekie",
"weight": 138
}
],
"op_in_trx": 1,
"timestamp": "2021-06-21T13:45:03",
"trx_id": "d4f2d63d227d67af47e3124fcf7737e23c3a09ed",
"trx_in_block": 17,
"virtual_op": true
}duekieupvoted (100.00%) @blockchained / bitshares-drama2021/06/21 13:45:03
duekieupvoted (100.00%) @blockchained / bitshares-drama
2021/06/21 13:45:03
| author | blockchained |
| permlink | bitshares-drama |
| voter | duekie |
| weight | 10000 (100.00%) |
| Transaction Info | Block #54976721/Trx d4f2d63d227d67af47e3124fcf7737e23c3a09ed |
View Raw JSON Data
{
"block": 54976721,
"op": [
"vote",
{
"author": "blockchained",
"permlink": "bitshares-drama",
"voter": "duekie",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2021-06-21T13:45:03",
"trx_id": "d4f2d63d227d67af47e3124fcf7737e23c3a09ed",
"trx_in_block": 17,
"virtual_op": false
}steembet.asiaeffective vote applied for @blockchained / bitshares-drama2021/06/21 12:10:57
steembet.asiaeffective vote applied for @blockchained / bitshares-drama
2021/06/21 12:10:57
| author | blockchained |
| pending payout | 0.017 HBD |
| permlink | bitshares-drama |
| rshares | 653746470 |
| total vote weight | 30222 |
| voter | steembet.asia |
| weight | 322 (3.22%) |
| Transaction Info | Block #54974841/Trx 40e0b4efc0897091b6fe9777732d42668c234995 |
View Raw JSON Data
{
"block": 54974841,
"op": [
"effective_comment_vote",
{
"author": "blockchained",
"pending_payout": "0.017 HBD",
"permlink": "bitshares-drama",
"rshares": 653746470,
"total_vote_weight": 30222,
"voter": "steembet.asia",
"weight": 322
}
],
"op_in_trx": 1,
"timestamp": "2021-06-21T12:10:57",
"trx_id": "40e0b4efc0897091b6fe9777732d42668c234995",
"trx_in_block": 1,
"virtual_op": true
}steembet.asiaupvoted (100.00%) @blockchained / bitshares-drama2021/06/21 12:10:57
steembet.asiaupvoted (100.00%) @blockchained / bitshares-drama
2021/06/21 12:10:57
| author | blockchained |
| permlink | bitshares-drama |
| voter | steembet.asia |
| weight | 10000 (100.00%) |
| Transaction Info | Block #54974841/Trx 40e0b4efc0897091b6fe9777732d42668c234995 |
View Raw JSON Data
{
"block": 54974841,
"op": [
"vote",
{
"author": "blockchained",
"permlink": "bitshares-drama",
"voter": "steembet.asia",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2021-06-21T12:10:57",
"trx_id": "40e0b4efc0897091b6fe9777732d42668c234995",
"trx_in_block": 1,
"virtual_op": false
}blockchainedcustom json: peakd_notify2021/06/21 12:04:54
blockchainedcustom json: peakd_notify
2021/06/21 12:04:54
| id | peakd_notify |
| json | {"action":"markAsRead","date":"2021-06-21T12:02:52"} |
| required auths | [] |
| required posting auths | ["blockchained"] |
| Transaction Info | Block #54974720/Trx 5156a93dad44b77f69d8a10d3bb0bf5465c32d7f |
View Raw JSON Data
{
"block": 54974720,
"op": [
"custom_json",
{
"id": "peakd_notify",
"json": "{\"action\":\"markAsRead\",\"date\":\"2021-06-21T12:02:52\"}",
"required_auths": [],
"required_posting_auths": [
"blockchained"
]
}
],
"op_in_trx": 1,
"timestamp": "2021-06-21T12:04:54",
"trx_id": "5156a93dad44b77f69d8a10d3bb0bf5465c32d7f",
"trx_in_block": 38,
"virtual_op": false
}blockchainedcustom json: notify2021/06/21 12:04:54
blockchainedcustom json: notify
2021/06/21 12:04:54
| id | notify |
| json | ["setLastRead",{"date":"2021-06-21T12:02:52"}] |
| required auths | [] |
| required posting auths | ["blockchained"] |
| Transaction Info | Block #54974720/Trx 5156a93dad44b77f69d8a10d3bb0bf5465c32d7f |
View Raw JSON Data
{
"block": 54974720,
"op": [
"custom_json",
{
"id": "notify",
"json": "[\"setLastRead\",{\"date\":\"2021-06-21T12:02:52\"}]",
"required_auths": [],
"required_posting_auths": [
"blockchained"
]
}
],
"op_in_trx": 0,
"timestamp": "2021-06-21T12:04:54",
"trx_id": "5156a93dad44b77f69d8a10d3bb0bf5465c32d7f",
"trx_in_block": 38,
"virtual_op": false
}blockchainedpublished a new post: bitshares-drama2021/06/21 12:02:48
blockchainedpublished a new post: bitshares-drama
2021/06/21 12:02:48
| author | blockchained |
| body |  *This is a translation, Russian original: https://golos.id/ru--blokcheijn/@akledirs/khroniki-dramy-v-bitshares* There always is, was and will be a place for drama in Bitshares, as it is a blockchain with ~~DPoS~~ DPoBS consensus, where “meat bags” play an important role. In the last year the scale of the drama reached mythica sizes. Recently in Russian community there was a request for coverage of the events that split the community and resulted in the launch of two new blockchains. This request was answered by Alexey Petrov (@tnam0rken) with his article [“Split in the Bitshares community. How it happened…”](https://golos.id/ru--blokcheijn/@tnam0rken/raskol-v-soobshestve-bitshares-kak-eto-bylo) (article is in Russian) Below is my attempt to cover some facts and events during this period in more detail, gather all the scattered pieces of information and all the changes that affected the chain of events. I am doing this for all who are interested in the history of the project, and would like to understand these events better. Some of the details that were covered by Alexey’s article will be omitted here for the sake of brevity. ## HF 4.0  30 June 2020 a new version of Bitshares-core [was released](https://github.com/bitshares/bitshares-core/releases/tag/4.0.0), which included a significant upgrade of the protocol (hardfork) to version 4.0. Release was planned for November 2019, but due to changes in votes for the core worker and disruption in financing that resulted the release was delayed. Protocol activation happens with a delay of 1 month, which means that the changes will come into effect on 30 July 2020. To get details about the changes in the release you can check the [release page](https://github.com/bitshares/bitshares-core/releases/tag/4.0.0). Here I will list the most significant. # Economic model changes ## [BSIP-74](https://github.com/bitshares/bsips/blob/master/bsip-0074.md) — Introduction of a Margin Call Fee Ratio In addition to the Maximum Short Squeeze Ration (MSSR), which is the premium that goes from the borrower that allowed a margin call to happen to MPA holder that sells their assets to fill that call, an additional fee is introduced, that can be set by the asset owner, and that is paid by the borrower — Margin Call Fee Ration (MCFR). Info about this fee is not displayed in the UI. ## [BSIP-75](https://github.com/bitshares/bsips/blob/master/bsip-0075.md) — Asset Owner Defines MCR and MSSR Values Now the owner of the asset can define who can change those parameters (asset owner or blockchain witnesses, before the change only witnesses could change them). Additionally the owner can freeze the values, and permanently decline the access to change it, which results in lower control over the smartasset, but higher level of trust, that results from the lowering of the amount of vectors for manipulation. ## [BSIP-77](https://github.com/bitshares/bsips/blob/master/bsip-0077.md) — Require Higher CR When Creating / Adjusting Debt Positions A new parameter is added to all MPAs — Initial Collateral Ration (ICR), that is defined by the smart asset owner or witnesses. It allows the blockchain to require from the borrower to put up higher collateral in relation to the Maintenance Collateral Ration (MCR). ## [BSIP-81](https://github.com/bitshares/bsips/blob/master/bsip-0081.md) — Simple Maker-Taker Market Fees Now the asset owner can define different market fees for the asset buyer, depending on whether the order is filled from the market (Taker), or is added to the order book (Maker). By default the fees are equal. UI does not reflect the difference in the fees. ## [BSIP-85](https://github.com/bitshares/bsips/blob/master/bsip-0085.md) — Maker order creation fee discount In essence this proposal is similar to BSIP-81, but in this case it talks about fees in BTS and their size is defined by the blockchain committee. ## [BSIP-86](https://github.com/bitshares/bsips/blob/master/bsip-0086.md) — Share market fees to the network This inconspicuous name hides a tax on the revenue of the asset owner from the market fees. Committee can now set a ratio of up to 30% that the asset owner must pay to the committee account vesting balance. The idea to call things as they are and rename the BSIP to “Share market fees to the committee” got a [negative reaction from Abit](https://github.com/bitshares/bsips/pull/270#issuecomment-616542051). ## [BSIP-87](https://github.com/bitshares/bsips/blob/master/bsip-0087.md) — Force Settlement Fee In addition to static MPA Force Settlement fee and Force Settlement Offset (FSO), that is paid by the user requesting the settlement to the borrower, this BSIP adds an ability to specify a percentage fee from the amount of amount being settled (Force Settlement Fee Percentage (FSFP)). The size of the fee is set by the asset owner and is paid from the user requesting Force Settlement to the asset owner when the MPA is settled. The change was suggested by bitcrab (Jerry Lee) and supported by Abit. This adds a new risk for smartcoin holders: the asset owner can at any point specify a 100% fee, in effect taking the collateral without an ability to control it until the settlement request. The risk is made more severe by the fact that the information about the fee amount is not displayed in UI. # Governance model changes These changes were not announced — they were added by the auditor (abit) despite no consensus decision on them. These changes were announced [after](https://bitsharestalk.org/index.php?topic=32546.0) the fact. **BTS in collateral are no longer counted for voting purposes.** Why was this decision made? Let us use Abit’s explanation: > The past flaw was simply that BTS in locked collateral would retain voting power. So when those holders found the market against them, were easily corrupted to vote against the common good. In other words, give everyone a free vote, and a majority will always form to use it for ‘themselves’. > > The result of a group of holders doubling power through collateral, then locking price feeds through block producers, held the blockchain ‘hostage’ since 2019 – destroying the standing reputation of a product with highest demand in 2020. [BitShares BitAssets Reloaded | Committee Owned True StableCoins](https://news.bitshares.org/bitshares-reloaded-bitassets1/) Indeed a group of borrowers, who were also holders of BTS, used collateralized borrowing to increase their stake in the project to a significant level. They had an interest to protect their capital, influence and also enough influence to elect witnesses who would provide feeds that would satisfy their interest. And they used that tactics for a long time to provide fake feeds, promote [BSIP-42](https://github.com/bitshares/bsips/blob/master/bsip-0042.md) and [price feed level freeze](https://bitsharestalk.org/index.php?topic=27753.0) at a set level for bitUSD and bitCNY. A conflict of interest is apparent, and talks about it were ongoing since 2018. Something had to change, but the borrowers facing margin call liquidations of all of their leveraged positions were clearly against it. ## Automatic vote weight decrease for sleeping accounts After each vote the vote weight would return to 100%. First 360 days of inactivity it is lowered by 12.5%, and then for 315 day the weight is decreased by additional 12.5% points every 45 days. On day 675 of inactivity the vote weight is 0. ## One vote principle If the holder of BTS votes for more than one committee member, then the sum of their stake weight is split among the number of votes for committee members. Before the change every voted member would receive full stake weight of the voter. ## Staking based voting This change requires freezing BTS for them to be eligible for voting with 4 durations: 180/360/720/∞ days. Depending on selected duration a multiplier of x2/x4/x8/x0 is applied respectively. x0 multiplier for permanent freeze is explained below. Fee for this transaction type is 50 BTS and not subject to change by committee. In the case of the permanent blocking of BTS the blocked amount loses its vote weight and can not be used ever, which is equal to burning of BTS, but the equivalent sum staked has a multiplier of x8 applied to it. The multiplier is temporary, it decreases every 180 days by half, and in 720 days its influence is over. The maximum multiplier possible using the staking rules is capped at x32. After the staking transaction the multiplier comes into effect gradually in stages, with a delay after every stage, each stage comes into effect in 15 more days. The staking can be canceled in 15 days, but tokens will stay staked for 7 more days. Unstaking transaction removes the multiplier immediately, but the funds will stay staked for the period chosen by the user during staking. In case of the permanent token lock, the funds will stay blocked. A user can have more than one staked position, with duration of the staked positions tracked separately. **After the first permanent staked position...** New rules come into the effect: 1. Accounts that do not have at least 1 BTS staked do not participate in the voting; 2. BTS used as an MPA collateral no longer have voting power; 3. BTS in the order books no longer have voting power. ## DPoBS — new consensus algorithm and its justification This new model where voting preference is given to those who stake, and even effectively burn their tokens by permanently blocking them, which results in deflation Abit [has called](https://bitsharestalk.org/index.php?topic=32357.0) DPoBS — Delegated Proof of Burn and Proof of Stake CustomMiner has suggested back in 2017 the implementation of [BSIP-0024](https://github.com/bitshares/bsips/blob/master/bsip-0024.md) that gives voting preference for those who stake their BTS. You can get the most detailed view on Abit’s stance on voting by reading this article on Github from 2018 [New BSIP or BSIP24 discussion: stake lock-up mechanism, count only real "locked" stake as voting stake](https://github.com/bitshares/bsips/issues/83) . On 30th July 2020 the hardfork with all the changes described above has come into effect. A [curious fix](https://github.com/bitshares/bitshares-core/issues/2103) was also added, that corrected the displayed maximum supply of Bitshares. The actual supply was higher by **250 million coins higher**, than any of the blockchain explorers showed, including what was displayed on Coinmarketcap. # CNVOTE reaction -> New Bitshares  - On 31st of July first people who noticed the non standard behavior of the voting page, and some committee members started asking questions about the changes to the voting model to the developers. As a result it was discovered who was behind those non consensus changes, and votes were removed from Abit. - On 2nd of August the CNVOTE team started developing a fix that would affirm the existing consensus from before the hardfork. During the fix development a heated debate was happening, with defenders of abit’s changes arguing that there is some value to the changes, and since it happened it would be better not to change anything. - By 10th of August the fix was ready, but to deploy it CNVOTE needed to convince the witnesses to apply it, which encountered some difficulties. - On 16th of August Abit was approached with a request to relinquish the control over the official Github repository to committee, but he declined - On 17th of August after deciding that further effort in applying the patch is hopeless the CNVOTE team decided to create a new blockchain [BTS4.0 upgrade tampering code incident | NewBitshares [CN]](http://news.newbitshares.org/?p=218) [Announcement on Implementation of BTS CNVOTE Patch | BitsharesTalk [CN, EN]](https://bitsharestalk.org/index.php?topic=32584.0) - On 30th of August 2020 the chinese community unhappy with the changes and coming transition to a harsher voting model [announces](https://bitcointalk.org/index.php?topic=5272354) a new blockchain based on BTS 4.0 code, but without changes to the voting model added by Abit. Many call this a fork, but only the codebase was forked with the blockchain formed from a new genesis. - On 10th of September the network was launched named NewBitshares, and the token with NBS ticker. # Next Hardfork — Splash (5.x)  On 22nd of September a [new Bitshares core was released](https://github.com/bitshares/bitshares-core/releases/tag/5.0.0), with the hardfork [planned](https://github.com/bitshares/bitshares-core/blob/bd40332a3b9c25ca0acbe55e212f6959e5734fec/libraries/chain/hardfork.d/CORE_2262.hf) for 28th of September. This hardfork included two main changes — the support for AMM liquidity pools, and another change to the governance model — now **unstaked BTS do not have any voting weight at all**. On the next day everything came tumbling down. Abit consolidates the control over the network by staking his funds. Due to effectively sole control over the network he elects loyal witnesses and committee members. The committee (aka Abit) [disables MPA borrowing (block 51860407)](https://bitsharestalk.org/index.php?topic=32640.0) for bitCNY and bitUSD, the blockreward for witnesses is lowered to 0.1 BTS, and order placement fee is raised 20 times, MSSR for bitUSD is raised to 1.1, [which results in the global settlement for bitUSD (block 51889804)](https://bitsharestalk.org/index.php?topic=32646.0). Here we need to remind you, that fake oracle feeds were in effect which were against the borrowers of bitUSD. As a result bitUSD holders could get less than 70% of the tokens used as a collateral going by the spot prices at that time. bitCNY situation was similar, but Abit decided against doing the same there. In addition now the committee decides who can provide bitasset feeds. **Witnesses can not provide feeds without committee approval.** As a result of those news XCHNG announces closing of their Tre-Fund (market ticker XCHNG.FUND).  On the same day a batch of new bitassets is created by committee — bitassets 1.0. By the announcement of the committee the MSSR, MCR, delay and force settlement price offset will not be changed in the future [[BitsharesTalk]](https://bitsharestalk.org/index.php?topic=32647.0)[[News Bitshares]](https://news.bitshares.org/bitshares-reloaded-bitassets1/). # RuDEX/BLCKCHND reaction -> Graphene  - Blckchnd witness has publicly denounced Abit’s actions everywhere they could, and as a result was banned in the main english BitsharesDAC chat. - Team RuDEX supported CNVOTE fix patch - On 16th of September RuDEX [launched an NBS gateway](https://steemit.com/rudex/@rudex/newbitshares-nbs-gateway-on-decentralized-trading-platform-bitshares-rudex-launched) on bitshares, as well as a [public access point](https://market.nbsdex.io/) for the new network. - On 29th of September in the RUDEX Trollbox chat Dima BLCKCHND (@blockchained) announced a fork based on BTS 3.0 codebase named Graphene - On 12th of November 2020 team RuDEX [announced](https://steemit.com/blockchain/@rudex/graphene-blockchain-by-rudex-team-initial-distribution-announcement) an all win lottery to get the initial distribution and form a genesis block for the new chain - On 23rd of December the [results of the lottery](https://steemit.com/graphene/@rudex/graphene-lottery-end-announcement) were published, and all participants were given a stake and their funds were returned, possibly as a result of my critical comments on the lottery mechanics  - On 12th of April 2021 a new chain [was launched](https://gph.ai/) with GPH token ticker, and the maximum supply of 100 million tokens. **UPD** *- On 27th of May 2021 RuDEX have [migrated](https://steemit.com/rudex/@rudex/announcement-of-rudex-migration-from-bitshares-to-graphene-dates-and-terms) to Graphene from Bitshares.* # And now you are here...  On 19th of May the private Honest.USD smartcoin honestly went into global settlement state. In the next 24 hours ⅔ of all coins in circulation during the black swan event were settled. Such a significant reduction in debt, small volume and price bounce allowed @Chibchombia (BTS: imm-ortal) to revive the asset on the very next day. On 22th of May during the price safety margin of bitUSD was not enough, which resulted in a global settlement (“black swan event”). Selected witnesses abruptly stopped providing feeds for this assets, and despite the fact that the declared life time of the price feed is 24 hours, the mechanisms depending on the price feed stopped. After some time 2 feeds appeared, but the minimum required number is 3. Without feeds a manual asset revival is impossible, even if enough people want to bid on collateral for required amount. Abit [announced](https://bitsharestalk.org/index.php?topic=33051.0) that the collateral bids will be ignored, and he will revive the asset himself. Apparently he disabled witnesses feeds from being accepted, so they would not interfere with his plans. It is worth noting that once bitUSD encountered a black swan, hourly feeds for HERO private MPA were also stopped by terradacs-bp and liondani witnesses. It is not clear yet if that was manipulation, or reliance on bitUSD feeds.  # Authors position If you try to become a committee member, you will get a message that the position is unpaid.  [Abits](https://github.com/abitmore) actions resulted in a creation of a funding stream towards committee account fueled by new fees. On one hand only BSIP-86 directly creates revenues for the committee, and is probably not in effect right now, however most of the trading happens in committee bitassets, so the fees paid to MPA owners go to committee in most cases. Despite the lack of paid workers for development, updates of the core software are being developed, yet the display of the new fees in the UI are being delayed with responses in the vein of “we are not paid for it”. In essence under the pretense of increasing the revenue of Bitshares as a DAC (Decentralized Autonomous Company) via the fee burn that would result in deflatory pressure, which is similar to the shares buyback by a company, that would result in the appreciation of BTS holders assets, the value flows were reformed in such a way, that most of the share (Market Fee) comes under control of the committee, that can be spent as they see fit. Where is the guarantee that the committee doesn’t block and unvote current members, to keep the status quo? Previous track record shows that on bitcrab’s suggestion under pretense of bitasset liquidity they have lost a lot of money by participating in margin trading. What will happen this time we are yet to see. If we view Bitshares as a company, the committee as a Board of Directors, and BTS holders as stakeholders, then the stakeholders stock as unilaterally converted to preferred equity shares (non voting), and the Board of Directors is milking the company, leaving miniscule remainder of the market and transfer fees that go into reserve pool. **The revenue of those “directors” is based on the hidden fees, that most users are not aware of yet.** Such a situation in a real company is nonsense and such activity is **illegal** in most countries. Abit and his team got scot free so far. That is one side of the situation. On another hand shareholders themselves (lets call them majority holders) before all this mess were methodically scamming the users (mainly bitasset holders) by not having enough collateral against their debt obligations (bitassets) effectively stealing from them. To stop this fraud shareholders themselves would have to accept losses and lose their voting assets. If we take into the account that most users did not understand the intricacies of the platform the HODLers weren’t paying enough attention to the situation, such an abuse from major debt holders did not result in BTS price decline that was adequate to the outrageousness of the situation. The status quo with fake asset feeds (BSIP-42) and milking the reserve through the workers were a gainful strategy for them. But as they say there is more. The author of [BSIP-42](https://github.com/bitshares/bsips/blob/master/bsip-0042.md) is not bitcrab, but **Abit**. Everything he could reply when that was pointed out was “That is in the past”. My opinion on the NewBitshares is only that the new blockchain received mainly the cunning chinese as its community, which were fine with feed manipulation on Bitshares, and I was and still am against such methods, I did not have the inclination to follow them there. # In closing Since the new chain parameters are still not displayed in BitsharesUI, I decided to create a table with current parameters of main committee MPA’s including the new 1.0 ones. [Current bitasset parameters with “hidden” fees](https://golos.id/ru--blokcheijn/@akledirs/tekushie-parametry-bitassetov-so-skrytymi-komissiyami) |
| json metadata | {"app":"peakd/2021.06.2","format":"markdown","description":"Such a situation in a real company is nonsense and such activity is illegal in most countries.","tags":["blockchain","bitshares"],"users":["akledirs","tnam0rken","rudex","blockchained","Chibchombia"],"image":["https://cdn.steemitimages.com/DQmb3jTeWvua1bU6FK16Uxvj1qZhrZf9oU7E4Wkkyge6tKs/image.png","https://cdn.steemitimages.com/DQmPrwNuiFBSKAXBPfQDaQ4pFBQ7gLP9G29XoA4gvdUJpBs/image.png","https://cdn.steemitimages.com/DQmTM8HCQJCjwYT3XiVW6WTpjtPdHaU1ZV4jtXGXo6H16Ms/image.png","https://cdn.steemitimages.com/DQmbPbB73F8tm7yf3gKPzXpveEBwafuaVV7LeuJ1P7NWszn/image.png","https://cdn.steemitimages.com/DQmewYHhbyCo99mSvzFpTZCe4UeUuDpkEGBsv97nr9Zs6es/image.png","https://cdn.steemitimages.com/DQmYsobchTR8nfHKAyQfFWyvrMsoPhgNz5qcnacthjc6g8N/image.png","https://cdn.steemitimages.com/DQmUfuVNip9tokPwmR7yN3wmwcqsTcqnYCKPiw3vKLeZpvx/image.png","https://cdn.steemitimages.com/DQmb4bG9qopoq7uep4Kn7im1cjs8oxategzSzStZ7YzAeEp/image.png","https://cdn.steemitimages.com/DQmSzhvZ7HnX8VBErCkoaHHNmJsTumXCaZ26NvrenrMBLBm/image.png","https://cdn.steemitimages.com/DQmU6JkTsLFYosnHQTBnU6r9vaJSdiNxtdAA947hwzxWxEY/Screenshot%202021-06-21%20at%2013.14.28.png"]} |
| parent author | |
| parent permlink | blockchain |
| permlink | bitshares-drama |
| title | Bitshares Drama |
| Transaction Info | Block #54974678/Trx 57ff3496d0387236adb65d1f1ed0111b3730f469 |
View Raw JSON Data
{
"block": 54974678,
"op": [
"comment",
{
"author": "blockchained",
"body": "\n\n*This is a translation, Russian original: https://golos.id/ru--blokcheijn/@akledirs/khroniki-dramy-v-bitshares*\n\nThere always is, was and will be a place for drama in Bitshares, as it is a blockchain with ~~DPoS~~ DPoBS consensus, where “meat bags” play an important role. In the last year the scale of the drama reached mythica sizes. Recently in Russian community there was a request for coverage of the events that split the community and resulted in the launch of two new blockchains. This request was answered by Alexey Petrov (@tnam0rken) with his article [“Split in the Bitshares community. How it happened…”](https://golos.id/ru--blokcheijn/@tnam0rken/raskol-v-soobshestve-bitshares-kak-eto-bylo) (article is in Russian)\n\nBelow is my attempt to cover some facts and events during this period in more detail, gather all the scattered pieces of information and all the changes that affected the chain of events. I am doing this for all who are interested in the history of the project, and would like to understand these events better. Some of the details that were covered by Alexey’s article will be omitted here for the sake of brevity.\n\n## HF 4.0\n\n\n\n\n30 June 2020 a new version of Bitshares-core [was released](https://github.com/bitshares/bitshares-core/releases/tag/4.0.0), which included a significant upgrade of the protocol (hardfork) to version 4.0. Release was planned for November 2019, but due to changes in votes for the core worker and disruption in financing that resulted the release was delayed.\n\nProtocol activation happens with a delay of 1 month, which means that the changes will come into effect on 30 July 2020. To get details about the changes in the release you can check the [release page](https://github.com/bitshares/bitshares-core/releases/tag/4.0.0). Here I will list the most significant. \n\n# Economic model changes\n\n## [BSIP-74](https://github.com/bitshares/bsips/blob/master/bsip-0074.md) — Introduction of a Margin Call Fee Ratio\n\nIn addition to the Maximum Short Squeeze Ration (MSSR), which is the premium that goes from the borrower that allowed a margin call to happen to MPA holder that sells their assets to fill that call, an additional fee is introduced, that can be set by the asset owner, and that is paid by the borrower — Margin Call Fee Ration (MCFR).\n\nInfo about this fee is not displayed in the UI.\n\n\n## [BSIP-75](https://github.com/bitshares/bsips/blob/master/bsip-0075.md) — Asset Owner Defines MCR and MSSR Values\n\nNow the owner of the asset can define who can change those parameters (asset owner or blockchain witnesses, before the change only witnesses could change them). Additionally the owner can freeze the values, and permanently decline the access to change it, which results in lower control over the smartasset, but higher level of trust, that results from the lowering of the amount of vectors for manipulation.\n\n## [BSIP-77](https://github.com/bitshares/bsips/blob/master/bsip-0077.md) — Require Higher CR When Creating / Adjusting Debt Positions\n\nA new parameter is added to all MPAs — Initial Collateral Ration (ICR), that is defined by the smart asset owner or witnesses. It allows the blockchain to require from the borrower to put up higher collateral in relation to the Maintenance Collateral Ration (MCR).\n\n## [BSIP-81](https://github.com/bitshares/bsips/blob/master/bsip-0081.md) — Simple Maker-Taker Market Fees\n\nNow the asset owner can define different market fees for the asset buyer, depending on whether the order is filled from the market (Taker), or is added to the order book (Maker). By default the fees are equal.\n\nUI does not reflect the difference in the fees.\n\n## [BSIP-85](https://github.com/bitshares/bsips/blob/master/bsip-0085.md) — Maker order creation fee discount\n\nIn essence this proposal is similar to BSIP-81, but in this case it talks about fees in BTS and their size is defined by the blockchain committee.\n\n## [BSIP-86](https://github.com/bitshares/bsips/blob/master/bsip-0086.md) — Share market fees to the network\n\nThis inconspicuous name hides a tax on the revenue of the asset owner from the market fees. Committee can now set a ratio of up to 30% that the asset owner must pay to the committee account vesting balance. The idea to call things as they are and rename the BSIP to “Share market fees to the committee” got a [negative reaction from Abit](https://github.com/bitshares/bsips/pull/270#issuecomment-616542051). \n\n## [BSIP-87](https://github.com/bitshares/bsips/blob/master/bsip-0087.md) — Force Settlement Fee\n\nIn addition to static MPA Force Settlement fee and Force Settlement Offset (FSO), that is paid by the user requesting the settlement to the borrower, this BSIP adds an ability to specify a percentage fee from the amount of amount being settled (Force Settlement Fee Percentage (FSFP)). The size of the fee is set by the asset owner and is paid from the user requesting Force Settlement to the asset owner when the MPA is settled. The change was suggested by bitcrab (Jerry Lee) and supported by Abit.\n\nThis adds a new risk for smartcoin holders: the asset owner can at any point specify a 100% fee, in effect taking the collateral without an ability to control it until the settlement request. The risk is made more severe by the fact that the information about the fee amount is not displayed in UI.\n\n# Governance model changes\n\nThese changes were not announced — they were added by the auditor (abit) despite no consensus decision on them. These changes were announced [after](https://bitsharestalk.org/index.php?topic=32546.0) the fact.\n\n**BTS in collateral are no longer counted for voting purposes.**\n\nWhy was this decision made? Let us use Abit’s explanation:\n\n> The past flaw was simply that BTS in locked collateral would retain voting power. So when those holders found the market against them, were easily corrupted to vote against the common good. In other words, give everyone a free vote, and a majority will always form to use it for ‘themselves’. \n>\n> The result of a group of holders doubling power through collateral, then locking price feeds through block producers, held the blockchain ‘hostage’ since 2019 – destroying the standing reputation of a product with highest demand in 2020. \n[BitShares BitAssets Reloaded | Committee Owned True StableCoins](https://news.bitshares.org/bitshares-reloaded-bitassets1/)\n\nIndeed a group of borrowers, who were also holders of BTS, used collateralized borrowing to increase their stake in the project to a significant level. They had an interest to protect their capital, influence and also enough influence to elect witnesses who would provide feeds that would satisfy their interest. And they used that tactics for a long time to provide fake feeds, promote [BSIP-42](https://github.com/bitshares/bsips/blob/master/bsip-0042.md) and [price feed level freeze](https://bitsharestalk.org/index.php?topic=27753.0) at a set level for bitUSD and bitCNY. A conflict of interest is apparent, and talks about it were ongoing since 2018. Something had to change, but the borrowers facing margin call liquidations of all of their leveraged positions were clearly against it. \n\n## Automatic vote weight decrease for sleeping accounts\n\nAfter each vote the vote weight would return to 100%. First 360 days of inactivity it is lowered by 12.5%, and then for 315 day the weight is decreased by additional 12.5% points every 45 days. On day 675 of inactivity the vote weight is 0.\n\n## One vote principle\n\nIf the holder of BTS votes for more than one committee member, then the sum of their stake weight is split among the number of votes for committee members. Before the change every voted member would receive full stake weight of the voter.\n\n## Staking based voting\n\nThis change requires freezing BTS for them to be eligible for voting with 4 durations: 180/360/720/∞ days. Depending on selected duration a multiplier of x2/x4/x8/x0 is applied respectively. x0 multiplier for permanent freeze is explained below. Fee for this transaction type is 50 BTS and not subject to change by committee.\n\nIn the case of the permanent blocking of BTS the blocked amount loses its vote weight and can not be used ever, which is equal to burning of BTS, but the equivalent sum staked has a multiplier of x8 applied to it. The multiplier is temporary, it decreases every 180 days by half, and in 720 days its influence is over. The maximum multiplier possible using the staking rules is capped at x32.\n\nAfter the staking transaction the multiplier comes into effect gradually in stages, with a delay after every stage, each stage comes into effect in 15 more days. The staking can be canceled in 15 days, but tokens will stay staked for 7 more days.\n\nUnstaking transaction removes the multiplier immediately, but the funds will stay staked for the period chosen by the user during staking. In case of the permanent token lock, the funds will stay blocked.\n\nA user can have more than one staked position, with duration of the staked positions tracked separately.\n\n**After the first permanent staked position...**\n\nNew rules come into the effect:\n\n1. Accounts that do not have at least 1 BTS staked do not participate in the voting;\n2. BTS used as an MPA collateral no longer have voting power;\n3. BTS in the order books no longer have voting power.\n\n## DPoBS — new consensus algorithm and its justification\n\nThis new model where voting preference is given to those who stake, and even effectively burn their tokens by permanently blocking them, which results in deflation Abit [has called](https://bitsharestalk.org/index.php?topic=32357.0) DPoBS — Delegated Proof of Burn and Proof of Stake\n\nCustomMiner has suggested back in 2017 the implementation of [BSIP-0024](https://github.com/bitshares/bsips/blob/master/bsip-0024.md) that gives voting preference for those who stake their BTS.\n\nYou can get the most detailed view on Abit’s stance on voting by reading this article on Github from 2018 [New BSIP or BSIP24 discussion: stake lock-up mechanism, count only real \"locked\" stake as voting stake](https://github.com/bitshares/bsips/issues/83) .\n\nOn 30th July 2020 the hardfork with all the changes described above has come into effect. A [curious fix](https://github.com/bitshares/bitshares-core/issues/2103) was also added, that corrected the displayed maximum supply of Bitshares. The actual supply was higher by **250 million coins higher**, than any of the blockchain explorers showed, including what was displayed on Coinmarketcap.\n\n# CNVOTE reaction -> New Bitshares\n\n\n\n\n- On 31st of July first people who noticed the non standard behavior of the voting page, and some committee members started asking questions about the changes to the voting model to the developers. As a result it was discovered who was behind those non consensus changes, and votes were removed from Abit.\n- On 2nd of August the CNVOTE team started developing a fix that would affirm the existing consensus from before the hardfork. During the fix development a heated debate was happening, with defenders of abit’s changes arguing that there is some value to the changes, and since it happened it would be better not to change anything.\n- By 10th of August the fix was ready, but to deploy it CNVOTE needed to convince the witnesses to apply it, which encountered some difficulties.\n- On 16th of August Abit was approached with a request to relinquish the control over the official Github repository to committee, but he declined\n- On 17th of August after deciding that further effort in applying the patch is hopeless the CNVOTE team decided to create a new blockchain [BTS4.0 upgrade tampering code incident | NewBitshares [CN]](http://news.newbitshares.org/?p=218)\n [Announcement on Implementation of BTS CNVOTE Patch | BitsharesTalk [CN, EN]](https://bitsharestalk.org/index.php?topic=32584.0)\n- On 30th of August 2020 the chinese community unhappy with the changes and coming transition to a harsher voting model [announces](https://bitcointalk.org/index.php?topic=5272354) a new blockchain based on BTS 4.0 code, but without changes to the voting model added by Abit. Many call this a fork, but only the codebase was forked with the blockchain formed from a new genesis.\n- On 10th of September the network was launched named NewBitshares, and the token with NBS ticker.\n\n# Next Hardfork — Splash (5.x)\n\n\n\n\nOn 22nd of September a [new Bitshares core was released](https://github.com/bitshares/bitshares-core/releases/tag/5.0.0), with the hardfork [planned](https://github.com/bitshares/bitshares-core/blob/bd40332a3b9c25ca0acbe55e212f6959e5734fec/libraries/chain/hardfork.d/CORE_2262.hf) for 28th of September.\n\nThis hardfork included two main changes — the support for AMM liquidity pools, and another change to the governance model — now **unstaked BTS do not have any voting weight at all**.\n\nOn the next day everything came tumbling down. Abit consolidates the control over the network by staking his funds. Due to effectively sole control over the network he elects loyal witnesses and committee members. The committee (aka Abit) [disables MPA borrowing (block 51860407)](https://bitsharestalk.org/index.php?topic=32640.0) for bitCNY and bitUSD, the blockreward for witnesses is lowered to 0.1 BTS, and order placement fee is raised 20 times, MSSR for bitUSD is raised to 1.1, [which results in the global settlement for bitUSD (block 51889804)](https://bitsharestalk.org/index.php?topic=32646.0). Here we need to remind you, that fake oracle feeds were in effect which were against the borrowers of bitUSD. As a result bitUSD holders could get less than 70% of the tokens used as a collateral going by the spot prices at that time. bitCNY situation was similar, but Abit decided against doing the same there.\n\nIn addition now the committee decides who can provide bitasset feeds. **Witnesses can not provide feeds without committee approval.**\n\nAs a result of those news XCHNG announces closing of their Tre-Fund (market ticker XCHNG.FUND).\n\n\n\n\nOn the same day a batch of new bitassets is created by committee — bitassets 1.0. By the announcement of the committee the MSSR, MCR, delay and force settlement price offset will not be changed in the future [[BitsharesTalk]](https://bitsharestalk.org/index.php?topic=32647.0)[[News Bitshares]](https://news.bitshares.org/bitshares-reloaded-bitassets1/).\n\n# RuDEX/BLCKCHND reaction -> Graphene\n\n\n\n\n\n- Blckchnd witness has publicly denounced Abit’s actions everywhere they could, and as a result was banned in the main english BitsharesDAC chat.\n- Team RuDEX supported CNVOTE fix patch\n- On 16th of September RuDEX [launched an NBS gateway](https://steemit.com/rudex/@rudex/newbitshares-nbs-gateway-on-decentralized-trading-platform-bitshares-rudex-launched) on bitshares, as well as a [public access point](https://market.nbsdex.io/) for the new network.\n- On 29th of September in the RUDEX Trollbox chat Dima BLCKCHND (@blockchained) announced a fork based on BTS 3.0 codebase named Graphene\n- On 12th of November 2020 team RuDEX [announced](https://steemit.com/blockchain/@rudex/graphene-blockchain-by-rudex-team-initial-distribution-announcement) an all win lottery to get the initial distribution and form a genesis block for the new chain\n- On 23rd of December the [results of the lottery](https://steemit.com/graphene/@rudex/graphene-lottery-end-announcement) were published, and all participants were given a stake and their funds were returned, possibly as a result of my critical comments on the lottery mechanics\n\n\n\n\n- On 12th of April 2021 a new chain [was launched](https://gph.ai/) with GPH token ticker, and the maximum supply of 100 million tokens.\n\n**UPD**\n*- On 27th of May 2021 RuDEX have [migrated](https://steemit.com/rudex/@rudex/announcement-of-rudex-migration-from-bitshares-to-graphene-dates-and-terms) to Graphene from Bitshares.*\n\n# And now you are here...\n\n\n\n\nOn 19th of May the private Honest.USD smartcoin honestly went into global settlement state. In the next 24 hours ⅔ of all coins in circulation during the black swan event were settled. Such a significant reduction in debt, small volume and price bounce allowed @Chibchombia (BTS: imm-ortal) to revive the asset on the very next day.\n\nOn 22th of May during the price safety margin of bitUSD was not enough, which resulted in a global settlement (“black swan event”). Selected witnesses abruptly stopped providing feeds for this assets, and despite the fact that the declared life time of the price feed is 24 hours, the mechanisms depending on the price feed stopped. After some time 2 feeds appeared, but the minimum required number is 3. Without feeds a manual asset revival is impossible, even if enough people want to bid on collateral for required amount. Abit [announced](https://bitsharestalk.org/index.php?topic=33051.0) that the collateral bids will be ignored, and he will revive the asset himself. Apparently he disabled witnesses feeds from being accepted, so they would not interfere with his plans.\n\nIt is worth noting that once bitUSD encountered a black swan, hourly feeds for HERO private MPA were also stopped by terradacs-bp and liondani witnesses. It is not clear yet if that was manipulation, or reliance on bitUSD feeds.\n\n\n\n\n\n# Authors position\n\nIf you try to become a committee member, you will get a message that the position is unpaid.\n\n\n\n\n[Abits](https://github.com/abitmore) actions resulted in a creation of a funding stream towards committee account fueled by new fees. On one hand only BSIP-86 directly creates revenues for the committee, and is probably not in effect right now, however most of the trading happens in committee bitassets, so the fees paid to MPA owners go to committee in most cases.\n\nDespite the lack of paid workers for development, updates of the core software are being developed, yet the display of the new fees in the UI are being delayed with responses in the vein of “we are not paid for it”.\n\nIn essence under the pretense of increasing the revenue of Bitshares as a DAC (Decentralized Autonomous Company) via the fee burn that would result in deflatory pressure, which is similar to the shares buyback by a company, that would result in the appreciation of BTS holders assets, the value flows were reformed in such a way, that most of the share (Market Fee) comes under control of the committee, that can be spent as they see fit. Where is the guarantee that the committee doesn’t block and unvote current members, to keep the status quo? Previous track record shows that on bitcrab’s suggestion under pretense of bitasset liquidity they have lost a lot of money by participating in margin trading. What will happen this time we are yet to see.\n\nIf we view Bitshares as a company, the committee as a Board of Directors, and BTS holders as stakeholders, then the stakeholders stock as unilaterally converted to preferred equity shares (non voting), and the Board of Directors is milking the company, leaving miniscule remainder of the market and transfer fees that go into reserve pool. **The revenue of those “directors” is based on the hidden fees, that most users are not aware of yet.**\n\nSuch a situation in a real company is nonsense and such activity is **illegal** in most countries. Abit and his team got scot free so far.\n\n That is one side of the situation.\n\nOn another hand shareholders themselves (lets call them majority holders) before all this mess were methodically scamming the users (mainly bitasset holders) by not having enough collateral against their debt obligations (bitassets) effectively stealing from them. To stop this fraud shareholders themselves would have to accept losses and lose their voting assets. If we take into the account that most users did not understand the intricacies of the platform the HODLers weren’t paying enough attention to the situation, such an abuse from major debt holders did not result in BTS price decline that was adequate to the outrageousness of the situation. The status quo with fake asset feeds (BSIP-42) and milking the reserve through the workers were a gainful strategy for them.\n\nBut as they say there is more. The author of [BSIP-42](https://github.com/bitshares/bsips/blob/master/bsip-0042.md) is not bitcrab, but **Abit**. Everything he could reply when that was pointed out was “That is in the past”.\n\nMy opinion on the NewBitshares is only that the new blockchain received mainly the cunning chinese as its community, which were fine with feed manipulation on Bitshares, and I was and still am against such methods, I did not have the inclination to follow them there.\n\n# In closing\n\nSince the new chain parameters are still not displayed in BitsharesUI, I decided to create a table with current parameters of main committee MPA’s including the new 1.0 ones.\n\n[Current bitasset parameters with “hidden” fees](https://golos.id/ru--blokcheijn/@akledirs/tekushie-parametry-bitassetov-so-skrytymi-komissiyami)",
"json_metadata": "{\"app\":\"peakd/2021.06.2\",\"format\":\"markdown\",\"description\":\"Such a situation in a real company is nonsense and such activity is illegal in most countries.\",\"tags\":[\"blockchain\",\"bitshares\"],\"users\":[\"akledirs\",\"tnam0rken\",\"rudex\",\"blockchained\",\"Chibchombia\"],\"image\":[\"https://cdn.steemitimages.com/DQmb3jTeWvua1bU6FK16Uxvj1qZhrZf9oU7E4Wkkyge6tKs/image.png\",\"https://cdn.steemitimages.com/DQmPrwNuiFBSKAXBPfQDaQ4pFBQ7gLP9G29XoA4gvdUJpBs/image.png\",\"https://cdn.steemitimages.com/DQmTM8HCQJCjwYT3XiVW6WTpjtPdHaU1ZV4jtXGXo6H16Ms/image.png\",\"https://cdn.steemitimages.com/DQmbPbB73F8tm7yf3gKPzXpveEBwafuaVV7LeuJ1P7NWszn/image.png\",\"https://cdn.steemitimages.com/DQmewYHhbyCo99mSvzFpTZCe4UeUuDpkEGBsv97nr9Zs6es/image.png\",\"https://cdn.steemitimages.com/DQmYsobchTR8nfHKAyQfFWyvrMsoPhgNz5qcnacthjc6g8N/image.png\",\"https://cdn.steemitimages.com/DQmUfuVNip9tokPwmR7yN3wmwcqsTcqnYCKPiw3vKLeZpvx/image.png\",\"https://cdn.steemitimages.com/DQmb4bG9qopoq7uep4Kn7im1cjs8oxategzSzStZ7YzAeEp/image.png\",\"https://cdn.steemitimages.com/DQmSzhvZ7HnX8VBErCkoaHHNmJsTumXCaZ26NvrenrMBLBm/image.png\",\"https://cdn.steemitimages.com/DQmU6JkTsLFYosnHQTBnU6r9vaJSdiNxtdAA947hwzxWxEY/Screenshot%202021-06-21%20at%2013.14.28.png\"]}",
"parent_author": "",
"parent_permlink": "blockchain",
"permlink": "bitshares-drama",
"title": "Bitshares Drama"
}
],
"op_in_trx": 0,
"timestamp": "2021-06-21T12:02:48",
"trx_id": "57ff3496d0387236adb65d1f1ed0111b3730f469",
"trx_in_block": 3,
"virtual_op": false
}cryptoninja.gurueffective vote applied for @blockchained / bitshares-drama2021/06/21 11:50:45
cryptoninja.gurueffective vote applied for @blockchained / bitshares-drama
2021/06/21 11:50:45
| author | blockchained |
| pending payout | 0.017 HBD |
| permlink | bitshares-drama |
| rshares | 959418114 |
| total vote weight | 29900 |
| voter | cryptoninja.guru |
| weight | 472 (4.72%) |
| Transaction Info | Block #54974437/Trx 56100a62f90087d9463944c2e44f400eeb926cd4 |
View Raw JSON Data
{
"block": 54974437,
"op": [
"effective_comment_vote",
{
"author": "blockchained",
"pending_payout": "0.017 HBD",
"permlink": "bitshares-drama",
"rshares": 959418114,
"total_vote_weight": 29900,
"voter": "cryptoninja.guru",
"weight": 472
}
],
"op_in_trx": 1,
"timestamp": "2021-06-21T11:50:45",
"trx_id": "56100a62f90087d9463944c2e44f400eeb926cd4",
"trx_in_block": 30,
"virtual_op": true
}cryptoninja.guruupvoted (100.00%) @blockchained / bitshares-drama2021/06/21 11:50:45
cryptoninja.guruupvoted (100.00%) @blockchained / bitshares-drama
2021/06/21 11:50:45
| author | blockchained |
| permlink | bitshares-drama |
| voter | cryptoninja.guru |
| weight | 10000 (100.00%) |
| Transaction Info | Block #54974437/Trx 56100a62f90087d9463944c2e44f400eeb926cd4 |
View Raw JSON Data
{
"block": 54974437,
"op": [
"vote",
{
"author": "blockchained",
"permlink": "bitshares-drama",
"voter": "cryptoninja.guru",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2021-06-21T11:50:45",
"trx_id": "56100a62f90087d9463944c2e44f400eeb926cd4",
"trx_in_block": 30,
"virtual_op": false
}mrstafeffective vote applied for @blockchained / bitshares-drama2021/06/21 11:40:57
mrstafeffective vote applied for @blockchained / bitshares-drama
2021/06/21 11:40:57
| author | blockchained |
| pending payout | 0.017 HBD |
| permlink | bitshares-drama |
| rshares | 1940694644 |
| total vote weight | 29428 |
| voter | mrstaf |
| weight | 468 (4.68%) |
| Transaction Info | Block #54974241/Trx b4f1ceeb296a45a7d1f580639d6ddd69636d6e56 |
View Raw JSON Data
{
"block": 54974241,
"op": [
"effective_comment_vote",
{
"author": "blockchained",
"pending_payout": "0.017 HBD",
"permlink": "bitshares-drama",
"rshares": 1940694644,
"total_vote_weight": 29428,
"voter": "mrstaf",
"weight": 468
}
],
"op_in_trx": 1,
"timestamp": "2021-06-21T11:40:57",
"trx_id": "b4f1ceeb296a45a7d1f580639d6ddd69636d6e56",
"trx_in_block": 51,
"virtual_op": true
}mrstafupvoted (50.00%) @blockchained / bitshares-drama2021/06/21 11:40:57
mrstafupvoted (50.00%) @blockchained / bitshares-drama
2021/06/21 11:40:57
| author | blockchained |
| permlink | bitshares-drama |
| voter | mrstaf |
| weight | 5000 (50.00%) |
| Transaction Info | Block #54974241/Trx b4f1ceeb296a45a7d1f580639d6ddd69636d6e56 |
View Raw JSON Data
{
"block": 54974241,
"op": [
"vote",
{
"author": "blockchained",
"permlink": "bitshares-drama",
"voter": "mrstaf",
"weight": 5000
}
],
"op_in_trx": 0,
"timestamp": "2021-06-21T11:40:57",
"trx_id": "b4f1ceeb296a45a7d1f580639d6ddd69636d6e56",
"trx_in_block": 51,
"virtual_op": false
}kimchi-kingeffective vote applied for @blockchained / bitshares-drama2021/06/21 11:40:57
kimchi-kingeffective vote applied for @blockchained / bitshares-drama
2021/06/21 11:40:57
| author | blockchained |
| pending payout | 0.016 HBD |
| permlink | bitshares-drama |
| rshares | 1800053321 |
| total vote weight | 28472 |
| voter | kimchi-king |
| weight | 434 (4.34%) |
| Transaction Info | Block #54974241/Trx ba24bdb2cd3e1da1e5d7ffe4f9279e20012c1b97 |
View Raw JSON Data
{
"block": 54974241,
"op": [
"effective_comment_vote",
{
"author": "blockchained",
"pending_payout": "0.016 HBD",
"permlink": "bitshares-drama",
"rshares": 1800053321,
"total_vote_weight": 28472,
"voter": "kimchi-king",
"weight": 434
}
],
"op_in_trx": 1,
"timestamp": "2021-06-21T11:40:57",
"trx_id": "ba24bdb2cd3e1da1e5d7ffe4f9279e20012c1b97",
"trx_in_block": 50,
"virtual_op": true
}kimchi-kingupvoted (50.00%) @blockchained / bitshares-drama2021/06/21 11:40:57
kimchi-kingupvoted (50.00%) @blockchained / bitshares-drama
2021/06/21 11:40:57
| author | blockchained |
| permlink | bitshares-drama |
| voter | kimchi-king |
| weight | 5000 (50.00%) |
| Transaction Info | Block #54974241/Trx ba24bdb2cd3e1da1e5d7ffe4f9279e20012c1b97 |
View Raw JSON Data
{
"block": 54974241,
"op": [
"vote",
{
"author": "blockchained",
"permlink": "bitshares-drama",
"voter": "kimchi-king",
"weight": 5000
}
],
"op_in_trx": 0,
"timestamp": "2021-06-21T11:40:57",
"trx_id": "ba24bdb2cd3e1da1e5d7ffe4f9279e20012c1b97",
"trx_in_block": 50,
"virtual_op": false
}apasia.techeffective vote applied for @blockchained / bitshares-drama2021/06/21 11:40:45
apasia.techeffective vote applied for @blockchained / bitshares-drama
2021/06/21 11:40:45
| author | blockchained |
| pending payout | 0.016 HBD |
| permlink | bitshares-drama |
| rshares | 9366083692 |
| total vote weight | 27585 |
| voter | apasia.tech |
| weight | 2079 (20.79%) |
| Transaction Info | Block #54974237/Trx ba40d43ec9bfc5a7e3b2e2ee2895030476f90d08 |
View Raw JSON Data
{
"block": 54974237,
"op": [
"effective_comment_vote",
{
"author": "blockchained",
"pending_payout": "0.016 HBD",
"permlink": "bitshares-drama",
"rshares": 9366083692,
"total_vote_weight": 27585,
"voter": "apasia.tech",
"weight": 2079
}
],
"op_in_trx": 1,
"timestamp": "2021-06-21T11:40:45",
"trx_id": "ba40d43ec9bfc5a7e3b2e2ee2895030476f90d08",
"trx_in_block": 46,
"virtual_op": true
}apasia.techupvoted (100.00%) @blockchained / bitshares-drama2021/06/21 11:40:45
apasia.techupvoted (100.00%) @blockchained / bitshares-drama
2021/06/21 11:40:45
| author | blockchained |
| permlink | bitshares-drama |
| voter | apasia.tech |
| weight | 10000 (100.00%) |
| Transaction Info | Block #54974237/Trx ba40d43ec9bfc5a7e3b2e2ee2895030476f90d08 |
View Raw JSON Data
{
"block": 54974237,
"op": [
"vote",
{
"author": "blockchained",
"permlink": "bitshares-drama",
"voter": "apasia.tech",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2021-06-21T11:40:45",
"trx_id": "ba40d43ec9bfc5a7e3b2e2ee2895030476f90d08",
"trx_in_block": 46,
"virtual_op": false
}bitsharesorgeffective vote applied for @blockchained / bitshares-drama2021/06/21 11:39:45
bitsharesorgeffective vote applied for @blockchained / bitshares-drama
2021/06/21 11:39:45
| author | blockchained |
| pending payout | 0.013 HBD |
| permlink | bitshares-drama |
| rshares | 46232410148 |
| total vote weight | 22963 |
| voter | bitsharesorg |
| weight | 5740 (57.40%) |
| Transaction Info | Block #54974217/Trx eead953e8b405a11511987900246349a400dbb85 |
View Raw JSON Data
{
"block": 54974217,
"op": [
"effective_comment_vote",
{
"author": "blockchained",
"pending_payout": "0.013 HBD",
"permlink": "bitshares-drama",
"rshares": 46232410148,
"total_vote_weight": 22963,
"voter": "bitsharesorg",
"weight": 5740
}
],
"op_in_trx": 1,
"timestamp": "2021-06-21T11:39:45",
"trx_id": "eead953e8b405a11511987900246349a400dbb85",
"trx_in_block": 20,
"virtual_op": true
}bitsharesorgupvoted (100.00%) @blockchained / bitshares-drama2021/06/21 11:39:45
bitsharesorgupvoted (100.00%) @blockchained / bitshares-drama
2021/06/21 11:39:45
| author | blockchained |
| permlink | bitshares-drama |
| voter | bitsharesorg |
| weight | 10000 (100.00%) |
| Transaction Info | Block #54974217/Trx eead953e8b405a11511987900246349a400dbb85 |
View Raw JSON Data
{
"block": 54974217,
"op": [
"vote",
{
"author": "blockchained",
"permlink": "bitshares-drama",
"voter": "bitsharesorg",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2021-06-21T11:39:45",
"trx_id": "eead953e8b405a11511987900246349a400dbb85",
"trx_in_block": 20,
"virtual_op": false
}blockchainedpublished a new post: bitshares-drama2021/06/21 11:38:30
blockchainedpublished a new post: bitshares-drama
2021/06/21 11:38:30
| author | blockchained |
| body |  *This is a translation, Russian original: https://golos.id/ru--blokcheijn/@akledirs/khroniki-dramy-v-bitshares* There always is, was and will be a place for drama in Bitshares, as it is a blockchain with ~~DPoS~~ DPoBS consensus, where “meat bags” play an important role. In the last year the scale of the drama reached mythica sizes. Recently in Russian community there was a request for coverage of the events that split the community and resulted in the launch of two new blockchains. This request was answered by Alexey Petrov (@tnam0rken) with his article [“Split in the Bitshares community. How it happened…”](https://golos.id/ru--blokcheijn/@tnam0rken/raskol-v-soobshestve-bitshares-kak-eto-bylo) (article is in Russian) Below is my attempt to cover some facts and events during this period in more detail, gather all the scattered pieces of information and all the changes that affected the chain of events. I am doing this for all who are interested in the history of the project, and would like to understand these events better. Some of the details that were covered by Alexey’s article will be omitted here for the sake of brevity. ## HF 4.0  30 June 2020 a new version of Bitshares-core [was released](https://github.com/bitshares/bitshares-core/releases/tag/4.0.0), which included a significant upgrade of the protocol (hardfork) to version 4.0. Release was planned for November 2019, but due to changes in votes for the core worker and disruption in financing that resulted the release was delayed. Protocol activation happens with a delay of 1 month, which means that the changes will come into effect on 30 July 2020. To get details about the changes in the release you can check the [release page](https://github.com/bitshares/bitshares-core/releases/tag/4.0.0). Here I will list the most significant. # Economic model changes ## [BSIP-74](https://github.com/bitshares/bsips/blob/master/bsip-0074.md) — Introduction of a Margin Call Fee Ratio In addition to the Maximum Short Squeeze Ration (MSSR), which is the premium that goes from the borrower that allowed a margin call to happen to MPA holder that sells their assets to fill that call, an additional fee is introduced, that can be set by the asset owner, and that is paid by the borrower — Margin Call Fee Ration (MCFR). Info about this fee is not displayed in the UI. ## [BSIP-75](https://github.com/bitshares/bsips/blob/master/bsip-0075.md) — Asset Owner Defines MCR and MSSR Values Now the owner of the asset can define who can change those parameters (asset owner or blockchain witnesses, before the change only witnesses could change them). Additionally the owner can freeze the values, and permanently decline the access to change it, which results in lower control over the smartasset, but higher level of trust, that results from the lowering of the amount of vectors for manipulation. ## [BSIP-77](https://github.com/bitshares/bsips/blob/master/bsip-0077.md) — Require Higher CR When Creating / Adjusting Debt Positions A new parameter is added to all MPAs — Initial Collateral Ration (ICR), that is defined by the smart asset owner or witnesses. It allows the blockchain to require from the borrower to put up higher collateral in relation to the Maintenance Collateral Ration (MCR). ## [BSIP-81](https://github.com/bitshares/bsips/blob/master/bsip-0081.md) — Simple Maker-Taker Market Fees Now the asset owner can define different market fees for the asset buyer, depending on whether the order is filled from the market (Taker), or is added to the order book (Maker). By default the fees are equal. UI does not reflect the difference in the fees. ## [BSIP-85](https://github.com/bitshares/bsips/blob/master/bsip-0085.md) — Maker order creation fee discount In essence this proposal is similar to BSIP-81, but in this case it talks about fees in BTS and their size is defined by the blockchain committee. ## [BSIP-86](https://github.com/bitshares/bsips/blob/master/bsip-0086.md) — Share market fees to the network This inconspicuous name hides a tax on the revenue of the asset owner from the market fees. Committee can now set a ratio of up to 30% that the asset owner must pay to the committee account vesting balance. The idea to call things as they are and rename the BSIP to “Share market fees to the committee” got a [negative reaction from Abit](https://github.com/bitshares/bsips/pull/270#issuecomment-616542051). ## [BSIP-87](https://github.com/bitshares/bsips/blob/master/bsip-0087.md) — Force Settlement Fee In addition to static MPA Force Settlement fee and Force Settlement Offset (FSO), that is paid by the user requesting the settlement to the borrower, this BSIP adds an ability to specify a percentage fee from the amount of amount being settled (Force Settlement Fee Percentage (FSFP)). The size of the fee is set by the asset owner and is paid from the user requesting Force Settlement to the asset owner when the MPA is settled. The change was suggested by bitcrab (Jerry Lee) and supported by Abit. This adds a new risk for smartcoin holders: the asset owner can at any point specify a 100% fee, in effect taking the collateral without an ability to control it until the settlement request. The risk is made more severe by the fact that the information about the fee amount is not displayed in UI. # Governance model changes These changes were not announced — they were added by the auditor (abit) despite no consensus decision on them. These changes were announced [after](https://bitsharestalk.org/index.php?topic=32546.0) the fact. **BTS in collateral are no longer counted for voting purposes.** Why was this decision made? Let us use Abit’s explanation: > The past flaw was simply that BTS in locked collateral would retain voting power. So when those holders found the market against them, were easily corrupted to vote against the common good. In other words, give everyone a free vote, and a majority will always form to use it for ‘themselves’. > > The result of a group of holders doubling power through collateral, then locking price feeds through block producers, held the blockchain ‘hostage’ since 2019 – destroying the standing reputation of a product with highest demand in 2020. [BitShares BitAssets Reloaded | Committee Owned True StableCoins](https://news.bitshares.org/bitshares-reloaded-bitassets1/) Indeed a group of borrowers, who were also holders of BTS, used collateralized borrowing to increase their stake in the project to a significant level. They had an interest to protect their capital, influence and also enough influence to elect witnesses who would provide feeds that would satisfy their interest. And they used that tactics for a long time to provide fake feeds, promote [BSIP-42](https://github.com/bitshares/bsips/blob/master/bsip-0042.md) and [price feed level freeze](https://bitsharestalk.org/index.php?topic=27753.0) at a set level for bitUSD and bitCNY. A conflict of interest is apparent, and talks about it were ongoing since 2018. Something had to change, but the borrowers facing margin call liquidations of all of their leveraged positions were clearly against it. ## Automatic vote weight decrease for sleeping accounts After each vote the vote weight would return to 100%. First 360 days of inactivity it is lowered by 12.5%, and then for 315 day the weight is decreased by additional 12.5% points every 45 days. On day 675 of inactivity the vote weight is 0. ## One vote principle If the holder of BTS votes for more than one committee member, then the sum of their stake weight is split among the number of votes for committee members. Before the change every voted member would receive full stake weight of the voter. ## Staking based voting This change requires freezing BTS for them to be eligible for voting with 4 durations: 180/360/720/∞ days. Depending on selected duration a multiplier of x2/x4/x8/x0 is applied respectively. x0 multiplier for permanent freeze is explained below. Fee for this transaction type is 50 BTS and not subject to change by committee. In the case of the permanent blocking of BTS the blocked amount loses its vote weight and can not be used ever, which is equal to burning of BTS, but the equivalent sum staked has a multiplier of x8 applied to it. The multiplier is temporary, it decreases every 180 days by half, and in 720 days its influence is over. The maximum multiplier possible using the staking rules is capped at x32. After the staking transaction the multiplier comes into effect gradually in stages, with a delay after every stage, each stage comes into effect in 15 more days. The staking can be canceled in 15 days, but tokens will stay staked for 7 more days. Unstaking transaction removes the multiplier immediately, but the funds will stay staked for the period chosen by the user during staking. In case of the permanent token lock, the funds will stay blocked. A user can have more than one staked position, with duration of the staked positions tracked separately. **After the first permanent staked position...** New rules come into the effect: 1. Accounts that do not have at least 1 BTS staked do not participate in the voting; 2. BTS used as an MPA collateral no longer have voting power; 3. BTS in the order books no longer have voting power. ## DPoBS — new consensus algorithm and its justification This new model where voting preference is given to those who stake, and even effectively burn their tokens by permanently blocking them, which results in deflation Abit [has called](https://bitsharestalk.org/index.php?topic=32357.0) DPoBS — Delegated Proof of Burn and Proof of Stake CustomMiner has suggested back in 2017 the implementation of [BSIP-0024](https://github.com/bitshares/bsips/blob/master/bsip-0024.md) that gives voting preference for those who stake their BTS. You can get the most detailed view on Abit’s stance on voting by reading this article on Github from 2018 [New BSIP or BSIP24 discussion: stake lock-up mechanism, count only real "locked" stake as voting stake](https://github.com/bitshares/bsips/issues/83) . On 30th July 2020 the hardfork with all the changes described above has come into effect. A [curious fix](https://github.com/bitshares/bitshares-core/issues/2103) was also added, that corrected the displayed maximum supply of Bitshares. The actual supply was higher by **250 million coins higher**, than any of the blockchain explorers showed, including what was displayed on Coinmarketcap. # CNVOTE reaction -> New Bitshares  - On 31st of July first people who noticed the non standard behavior of the voting page, and some committee members started asking questions about the changes to the voting model to the developers. As a result it was discovered who was behind those non consensus changes, and votes were removed from Abit. - On 2nd of August the CNVOTE team started developing a fix that would affirm the existing consensus from before the hardfork. During the fix development a heated debate was happening, with defenders of abit’s changes arguing that there is some value to the changes, and since it happened it would be better not to change anything. - By 10th of August the fix was ready, but to deploy it CNVOTE needed to convince the witnesses to apply it, which encountered some difficulties. - On 16th of August Abit was approached with a request to relinquish the control over the official Github repository to committee, but he declined - On 17th of August after deciding that further effort in applying the patch is hopeless the CNVOTE team decided to create a new blockchain [BTS4.0 upgrade tampering code incident | NewBitshares [CN]](http://news.newbitshares.org/?p=218) [Announcement on Implementation of BTS CNVOTE Patch | BitsharesTalk [CN, EN]](https://bitsharestalk.org/index.php?topic=32584.0) - On 30th of August 2020 the chinese community unhappy with the changes and coming transition to a harsher voting model [announces](https://bitcointalk.org/index.php?topic=5272354) a new blockchain based on BTS 4.0 code, but without changes to the voting model added by Abit. Many call this a fork, but only the codebase was forked with the blockchain formed from a new genesis. - On 10th of September the network was launched named NewBitshares, and the token with NBS ticker. # Next Hardfork — Splash (5.x)  On 22nd of September a [new Bitshares core was released](https://github.com/bitshares/bitshares-core/releases/tag/5.0.0), with the hardfork [planned](https://github.com/bitshares/bitshares-core/blob/bd40332a3b9c25ca0acbe55e212f6959e5734fec/libraries/chain/hardfork.d/CORE_2262.hf) for 28th of September. This hardfork included two main changes — the support for AMM liquidity pools, and another change to the governance model — now **unstaked BTS do not have any voting weight at all**. On the next day everything came tumbling down. Abit consolidates the control over the network by staking his funds. Due to effectively sole control over the network he elects loyal witnesses and committee members. The committee (aka Abit) [disables MPA borrowing (block 51860407)](https://bitsharestalk.org/index.php?topic=32640.0) for bitCNY and bitUSD, the blockreward for witnesses is lowered to 0.1 BTS, and order placement fee is raised 20 times, MSSR for bitUSD is raised to 1.1, [which results in the global settlement for bitUSD (block 51889804)](https://bitsharestalk.org/index.php?topic=32646.0). Here we need to remind you, that fake oracle feeds were in effect which were against the borrowers of bitUSD. As a result bitUSD holders could get less than 70% of the tokens used as a collateral going by the spot prices at that time. bitCNY situation was similar, but Abit decided against doing the same there. In addition now the committee decides who can provide bitasset feeds. **Witnesses can not provide feeds without committee approval.** As a result of those news XCHNG announces closing of their Tre-Fund (market ticker XCHNG.FUND).  On the same day a batch of new bitassets is created by committee — bitassets 1.0. By the announcement of the committee the MSSR, MCR, delay and force settlement price offset will not be changed in the future [[BitsharesTalk]](https://bitsharestalk.org/index.php?topic=32647.0)[[News Bitshares]](https://news.bitshares.org/bitshares-reloaded-bitassets1/). # RuDEX/BLCKCHND reaction -> Graphene  - Blckchnd witness has publicly denounced Abit’s actions everywhere they could, and as a result was banned in the main english BitsharesDAC chat. - Team RuDEX supported CNVOTE fix patch - On 16th of September RuDEX [launched an NBS gateway](https://steemit.com/rudex/@rudex/newbitshares-nbs-gateway-on-decentralized-trading-platform-bitshares-rudex-launched) on bitshares, as well as a [public access point](https://market.nbsdex.io/) for the new network. - On 29th of September in the RUDEX Trollbox chat Dima BLCKCHND (@blockchained) announced a fork based on BTS 3.0 codebase named Graphene - On 12th of November 2020 team RuDEX [announced](https://steemit.com/blockchain/@rudex/graphene-blockchain-by-rudex-team-initial-distribution-announcement) an all win lottery to get the initial distribution and form a genesis block for the new chain - On 23rd of December the [results of the lottery](https://steemit.com/graphene/@rudex/graphene-lottery-end-announcement) were published, and all participants were given a stake and their funds were returned, possibly as a result of my critical comments on the lottery mechanics  - On 12th of April 2021 a new chain [was launched](https://gph.ai/) with GPH token ticker, and the maximum supply of 100 million tokens. **UPD** *- On 27th of May 2021 RuDEX have [migrated](https://steemit.com/rudex/@rudex/announcement-of-rudex-migration-from-bitshares-to-graphene-dates-and-terms) to Graphene from Bitshares.* # And now you are here...  On 19th of May the private Honest.USD smartcoin honestly went into global settlement state. In the next 24 hours ⅔ of all coins in circulation during the black swan event were settled. Such a significant reduction in debt, small volume and price bounce allowed @Chibchombia (BTS: imm-ortal) to revive the asset on the very next day. On 22th of May during the price safety margin of bitUSD was not enough, which resulted in a global settlement (“black swan event”). Selected witnesses abruptly stopped providing feeds for this assets, and despite the fact that the declared life time of the price feed is 24 hours, the mechanisms depending on the price feed stopped. After some time 2 feeds appeared, but the minimum required number is 3. Without feeds a manual asset revival is impossible, even if enough people want to bid on collateral for required amount. Abit [announced](https://bitsharestalk.org/index.php?topic=33051.0) that the collateral bids will be ignored, and he will revive the asset himself. Apparently he disabled witnesses feeds from being accepted, so they would not interfere with his plans. It is worth noting that once bitUSD encountered a black swan, hourly feeds for HERO private MPA were also stopped by terradacs-bp and liondani witnesses. It is not clear yet if that was manipulation, or reliance on bitUSD feeds.  # Authors position If you try to become a committee member, you will get a message that the position is unpaid.  [Abits](https://github.com/abitmore) actions resulted in a creation of a funding stream towards committee account fueled by new fees. On one hand only BSIP-86 directly creates revenues for the committee, and is probably not in effect right now, however most of the trading happens in committee bitassets, so the fees paid to MPA owners go to committee in most cases. Despite the lack of paid workers for development, updates of the core software are being developed, yet the display of the new fees in the UI are being delayed with responses in the vein of “we are not paid for it”. In essence under the pretense of increasing the revenue of Bitshares as a DAC (Decentralized Autonomous Company) via the fee burn that would result in deflatory pressure, which is similar to the shares buyback by a company, that would result in the appreciation of BTS holders assets, the value flows were reformed in such a way, that most of the share (Market Fee) comes under control of the committee, that can be spent as they see fit. Where is the guarantee that the committee doesn’t block and unvote current members, to keep the status quo? Previous track record shows that on bitcrab’s suggestion under pretense of bitasset liquidity they have lost a lot of money by participating in margin trading. What will happen this time we are yet to see. If we view Bitshares as a company, the committee as a Board of Directors, and BTS holders as stakeholders, then the stakeholders stock as unilaterally converted to preferred equity shares (non voting), and the Board of Directors is milking the company, leaving miniscule remainder of the market and transfer fees that go into reserve pool. **The revenue of those “directors” is based on the hidden fees, that most users are not aware of yet.** Such a situation in a real company is nonsense and such activity is **illegal** in most countries. Abit and his team got scot free so far. That is one side of the situation. On another hand shareholders themselves (lets call them majority holders) before all this mess were methodically scamming the users (mainly bitasset holders) by not having enough collateral against their debt obligations (bitassets) effectively stealing from them. To stop this fraud shareholders themselves would have to accept losses and lose their voting assets. If we take into the account that most users did not understand the intricacies of the platform the HODLers weren’t paying enough attention to the situation, such an abuse from major debt holders did not result in BTS price decline that was adequate to the outrageousness of the situation. The status quo with fake asset feeds (BSIP-42) and milking the reserve through the workers were a gainful strategy for them. But as they say there is more. The author of [BSIP-42](https://github.com/bitshares/bsips/blob/master/bsip-0042.md) is not bitcrab, but **Abit**. Everything he could reply when that was pointed out was “That is in the past”. My opinion on the NewBitshares is only that the new blockchain received mainly the cunning chinese as its community, which were fine with feed manipulation on Bitshares, and I was and still am against such methods, I did not have the inclination to follow them there. # In closing Since the new chain parameters are still not displayed in BitsharesUI, I decided to create a table with current parameters of main committee MPA’s including the new 1.0 ones. [Current bitasset parameters with “hidden” fees](https://golos.id/ru--blokcheijn/@akledirs/tekushie-parametry-bitassetov-so-skrytymi-komissiyami) |
| json metadata | {"app":"peakd/2021.06.2","format":"markdown","description":"Such a situation in a real company is nonsense and such activity is illegal in most countries. Abit and his team got scot free so far.","tags":["blockchain","bitshares"],"users":["akledirs","tnam0rken","rudex","blockchained","Chibchombia"],"image":["https://cdn.steemitimages.com/DQmb3jTeWvua1bU6FK16Uxvj1qZhrZf9oU7E4Wkkyge6tKs/image.png","https://cdn.steemitimages.com/DQmPrwNuiFBSKAXBPfQDaQ4pFBQ7gLP9G29XoA4gvdUJpBs/image.png","https://cdn.steemitimages.com/DQmTM8HCQJCjwYT3XiVW6WTpjtPdHaU1ZV4jtXGXo6H16Ms/image.png","https://cdn.steemitimages.com/DQmbPbB73F8tm7yf3gKPzXpveEBwafuaVV7LeuJ1P7NWszn/image.png","https://cdn.steemitimages.com/DQmewYHhbyCo99mSvzFpTZCe4UeUuDpkEGBsv97nr9Zs6es/image.png","https://cdn.steemitimages.com/DQmYsobchTR8nfHKAyQfFWyvrMsoPhgNz5qcnacthjc6g8N/image.png","https://cdn.steemitimages.com/DQmUfuVNip9tokPwmR7yN3wmwcqsTcqnYCKPiw3vKLeZpvx/image.png","https://cdn.steemitimages.com/DQmb4bG9qopoq7uep4Kn7im1cjs8oxategzSzStZ7YzAeEp/image.png","https://cdn.steemitimages.com/DQmSzhvZ7HnX8VBErCkoaHHNmJsTumXCaZ26NvrenrMBLBm/image.png","https://cdn.steemitimages.com/DQmU6JkTsLFYosnHQTBnU6r9vaJSdiNxtdAA947hwzxWxEY/Screenshot%202021-06-21%20at%2013.14.28.png"]} |
| parent author | |
| parent permlink | blockchain |
| permlink | bitshares-drama |
| title | Bitshares Drama |
| Transaction Info | Block #54974192/Trx b228d5fbe7ea0eb3e682f7a42047f5b449af5c42 |
View Raw JSON Data
{
"block": 54974192,
"op": [
"comment",
{
"author": "blockchained",
"body": "\n\n*This is a translation, Russian original: https://golos.id/ru--blokcheijn/@akledirs/khroniki-dramy-v-bitshares*\n\nThere always is, was and will be a place for drama in Bitshares, as it is a blockchain with ~~DPoS~~ DPoBS consensus, where “meat bags” play an important role. In the last year the scale of the drama reached mythica sizes. Recently in Russian community there was a request for coverage of the events that split the community and resulted in the launch of two new blockchains. This request was answered by Alexey Petrov (@tnam0rken) with his article [“Split in the Bitshares community. How it happened…”](https://golos.id/ru--blokcheijn/@tnam0rken/raskol-v-soobshestve-bitshares-kak-eto-bylo) (article is in Russian)\n\nBelow is my attempt to cover some facts and events during this period in more detail, gather all the scattered pieces of information and all the changes that affected the chain of events. I am doing this for all who are interested in the history of the project, and would like to understand these events better. Some of the details that were covered by Alexey’s article will be omitted here for the sake of brevity.\n\n## HF 4.0\n\n\n\n\n30 June 2020 a new version of Bitshares-core [was released](https://github.com/bitshares/bitshares-core/releases/tag/4.0.0), which included a significant upgrade of the protocol (hardfork) to version 4.0. Release was planned for November 2019, but due to changes in votes for the core worker and disruption in financing that resulted the release was delayed.\n\nProtocol activation happens with a delay of 1 month, which means that the changes will come into effect on 30 July 2020. To get details about the changes in the release you can check the [release page](https://github.com/bitshares/bitshares-core/releases/tag/4.0.0). Here I will list the most significant. \n\n# Economic model changes\n\n## [BSIP-74](https://github.com/bitshares/bsips/blob/master/bsip-0074.md) — Introduction of a Margin Call Fee Ratio\n\nIn addition to the Maximum Short Squeeze Ration (MSSR), which is the premium that goes from the borrower that allowed a margin call to happen to MPA holder that sells their assets to fill that call, an additional fee is introduced, that can be set by the asset owner, and that is paid by the borrower — Margin Call Fee Ration (MCFR).\n\nInfo about this fee is not displayed in the UI.\n\n\n## [BSIP-75](https://github.com/bitshares/bsips/blob/master/bsip-0075.md) — Asset Owner Defines MCR and MSSR Values\n\nNow the owner of the asset can define who can change those parameters (asset owner or blockchain witnesses, before the change only witnesses could change them). Additionally the owner can freeze the values, and permanently decline the access to change it, which results in lower control over the smartasset, but higher level of trust, that results from the lowering of the amount of vectors for manipulation.\n\n## [BSIP-77](https://github.com/bitshares/bsips/blob/master/bsip-0077.md) — Require Higher CR When Creating / Adjusting Debt Positions\n\nA new parameter is added to all MPAs — Initial Collateral Ration (ICR), that is defined by the smart asset owner or witnesses. It allows the blockchain to require from the borrower to put up higher collateral in relation to the Maintenance Collateral Ration (MCR).\n\n## [BSIP-81](https://github.com/bitshares/bsips/blob/master/bsip-0081.md) — Simple Maker-Taker Market Fees\n\nNow the asset owner can define different market fees for the asset buyer, depending on whether the order is filled from the market (Taker), or is added to the order book (Maker). By default the fees are equal.\n\nUI does not reflect the difference in the fees.\n\n## [BSIP-85](https://github.com/bitshares/bsips/blob/master/bsip-0085.md) — Maker order creation fee discount\n\nIn essence this proposal is similar to BSIP-81, but in this case it talks about fees in BTS and their size is defined by the blockchain committee.\n\n## [BSIP-86](https://github.com/bitshares/bsips/blob/master/bsip-0086.md) — Share market fees to the network\n\nThis inconspicuous name hides a tax on the revenue of the asset owner from the market fees. Committee can now set a ratio of up to 30% that the asset owner must pay to the committee account vesting balance. The idea to call things as they are and rename the BSIP to “Share market fees to the committee” got a [negative reaction from Abit](https://github.com/bitshares/bsips/pull/270#issuecomment-616542051). \n\n## [BSIP-87](https://github.com/bitshares/bsips/blob/master/bsip-0087.md) — Force Settlement Fee\n\nIn addition to static MPA Force Settlement fee and Force Settlement Offset (FSO), that is paid by the user requesting the settlement to the borrower, this BSIP adds an ability to specify a percentage fee from the amount of amount being settled (Force Settlement Fee Percentage (FSFP)). The size of the fee is set by the asset owner and is paid from the user requesting Force Settlement to the asset owner when the MPA is settled. The change was suggested by bitcrab (Jerry Lee) and supported by Abit.\n\nThis adds a new risk for smartcoin holders: the asset owner can at any point specify a 100% fee, in effect taking the collateral without an ability to control it until the settlement request. The risk is made more severe by the fact that the information about the fee amount is not displayed in UI.\n\n# Governance model changes\n\nThese changes were not announced — they were added by the auditor (abit) despite no consensus decision on them. These changes were announced [after](https://bitsharestalk.org/index.php?topic=32546.0) the fact.\n\n**BTS in collateral are no longer counted for voting purposes.**\n\nWhy was this decision made? Let us use Abit’s explanation:\n\n> The past flaw was simply that BTS in locked collateral would retain voting power. So when those holders found the market against them, were easily corrupted to vote against the common good. In other words, give everyone a free vote, and a majority will always form to use it for ‘themselves’. \n>\n> The result of a group of holders doubling power through collateral, then locking price feeds through block producers, held the blockchain ‘hostage’ since 2019 – destroying the standing reputation of a product with highest demand in 2020. \n[BitShares BitAssets Reloaded | Committee Owned True StableCoins](https://news.bitshares.org/bitshares-reloaded-bitassets1/)\n\nIndeed a group of borrowers, who were also holders of BTS, used collateralized borrowing to increase their stake in the project to a significant level. They had an interest to protect their capital, influence and also enough influence to elect witnesses who would provide feeds that would satisfy their interest. And they used that tactics for a long time to provide fake feeds, promote [BSIP-42](https://github.com/bitshares/bsips/blob/master/bsip-0042.md) and [price feed level freeze](https://bitsharestalk.org/index.php?topic=27753.0) at a set level for bitUSD and bitCNY. A conflict of interest is apparent, and talks about it were ongoing since 2018. Something had to change, but the borrowers facing margin call liquidations of all of their leveraged positions were clearly against it. \n\n## Automatic vote weight decrease for sleeping accounts\n\nAfter each vote the vote weight would return to 100%. First 360 days of inactivity it is lowered by 12.5%, and then for 315 day the weight is decreased by additional 12.5% points every 45 days. On day 675 of inactivity the vote weight is 0.\n\n## One vote principle\n\nIf the holder of BTS votes for more than one committee member, then the sum of their stake weight is split among the number of votes for committee members. Before the change every voted member would receive full stake weight of the voter.\n\n## Staking based voting\n\nThis change requires freezing BTS for them to be eligible for voting with 4 durations: 180/360/720/∞ days. Depending on selected duration a multiplier of x2/x4/x8/x0 is applied respectively. x0 multiplier for permanent freeze is explained below. Fee for this transaction type is 50 BTS and not subject to change by committee.\n\nIn the case of the permanent blocking of BTS the blocked amount loses its vote weight and can not be used ever, which is equal to burning of BTS, but the equivalent sum staked has a multiplier of x8 applied to it. The multiplier is temporary, it decreases every 180 days by half, and in 720 days its influence is over. The maximum multiplier possible using the staking rules is capped at x32.\n\nAfter the staking transaction the multiplier comes into effect gradually in stages, with a delay after every stage, each stage comes into effect in 15 more days. The staking can be canceled in 15 days, but tokens will stay staked for 7 more days.\n\nUnstaking transaction removes the multiplier immediately, but the funds will stay staked for the period chosen by the user during staking. In case of the permanent token lock, the funds will stay blocked.\n\nA user can have more than one staked position, with duration of the staked positions tracked separately.\n\n**After the first permanent staked position...**\n\nNew rules come into the effect:\n\n1. Accounts that do not have at least 1 BTS staked do not participate in the voting;\n2. BTS used as an MPA collateral no longer have voting power;\n3. BTS in the order books no longer have voting power.\n\n## DPoBS — new consensus algorithm and its justification\n\nThis new model where voting preference is given to those who stake, and even effectively burn their tokens by permanently blocking them, which results in deflation Abit [has called](https://bitsharestalk.org/index.php?topic=32357.0) DPoBS — Delegated Proof of Burn and Proof of Stake\n\nCustomMiner has suggested back in 2017 the implementation of [BSIP-0024](https://github.com/bitshares/bsips/blob/master/bsip-0024.md) that gives voting preference for those who stake their BTS.\n\nYou can get the most detailed view on Abit’s stance on voting by reading this article on Github from 2018 [New BSIP or BSIP24 discussion: stake lock-up mechanism, count only real \"locked\" stake as voting stake](https://github.com/bitshares/bsips/issues/83) .\n\nOn 30th July 2020 the hardfork with all the changes described above has come into effect. A [curious fix](https://github.com/bitshares/bitshares-core/issues/2103) was also added, that corrected the displayed maximum supply of Bitshares. The actual supply was higher by **250 million coins higher**, than any of the blockchain explorers showed, including what was displayed on Coinmarketcap.\n\n# CNVOTE reaction -> New Bitshares\n\n\n\n\n- On 31st of July first people who noticed the non standard behavior of the voting page, and some committee members started asking questions about the changes to the voting model to the developers. As a result it was discovered who was behind those non consensus changes, and votes were removed from Abit.\n- On 2nd of August the CNVOTE team started developing a fix that would affirm the existing consensus from before the hardfork. During the fix development a heated debate was happening, with defenders of abit’s changes arguing that there is some value to the changes, and since it happened it would be better not to change anything.\n- By 10th of August the fix was ready, but to deploy it CNVOTE needed to convince the witnesses to apply it, which encountered some difficulties.\n- On 16th of August Abit was approached with a request to relinquish the control over the official Github repository to committee, but he declined\n- On 17th of August after deciding that further effort in applying the patch is hopeless the CNVOTE team decided to create a new blockchain [BTS4.0 upgrade tampering code incident | NewBitshares [CN]](http://news.newbitshares.org/?p=218)\n [Announcement on Implementation of BTS CNVOTE Patch | BitsharesTalk [CN, EN]](https://bitsharestalk.org/index.php?topic=32584.0)\n- On 30th of August 2020 the chinese community unhappy with the changes and coming transition to a harsher voting model [announces](https://bitcointalk.org/index.php?topic=5272354) a new blockchain based on BTS 4.0 code, but without changes to the voting model added by Abit. Many call this a fork, but only the codebase was forked with the blockchain formed from a new genesis.\n- On 10th of September the network was launched named NewBitshares, and the token with NBS ticker.\n\n# Next Hardfork — Splash (5.x)\n\n\n\n\nOn 22nd of September a [new Bitshares core was released](https://github.com/bitshares/bitshares-core/releases/tag/5.0.0), with the hardfork [planned](https://github.com/bitshares/bitshares-core/blob/bd40332a3b9c25ca0acbe55e212f6959e5734fec/libraries/chain/hardfork.d/CORE_2262.hf) for 28th of September.\n\nThis hardfork included two main changes — the support for AMM liquidity pools, and another change to the governance model — now **unstaked BTS do not have any voting weight at all**.\n\nOn the next day everything came tumbling down. Abit consolidates the control over the network by staking his funds. Due to effectively sole control over the network he elects loyal witnesses and committee members. The committee (aka Abit) [disables MPA borrowing (block 51860407)](https://bitsharestalk.org/index.php?topic=32640.0) for bitCNY and bitUSD, the blockreward for witnesses is lowered to 0.1 BTS, and order placement fee is raised 20 times, MSSR for bitUSD is raised to 1.1, [which results in the global settlement for bitUSD (block 51889804)](https://bitsharestalk.org/index.php?topic=32646.0). Here we need to remind you, that fake oracle feeds were in effect which were against the borrowers of bitUSD. As a result bitUSD holders could get less than 70% of the tokens used as a collateral going by the spot prices at that time. bitCNY situation was similar, but Abit decided against doing the same there.\n\nIn addition now the committee decides who can provide bitasset feeds. **Witnesses can not provide feeds without committee approval.**\n\nAs a result of those news XCHNG announces closing of their Tre-Fund (market ticker XCHNG.FUND).\n\n\n\n\nOn the same day a batch of new bitassets is created by committee — bitassets 1.0. By the announcement of the committee the MSSR, MCR, delay and force settlement price offset will not be changed in the future [[BitsharesTalk]](https://bitsharestalk.org/index.php?topic=32647.0)[[News Bitshares]](https://news.bitshares.org/bitshares-reloaded-bitassets1/).\n\n# RuDEX/BLCKCHND reaction -> Graphene\n\n\n\n\n\n- Blckchnd witness has publicly denounced Abit’s actions everywhere they could, and as a result was banned in the main english BitsharesDAC chat.\n- Team RuDEX supported CNVOTE fix patch\n- On 16th of September RuDEX [launched an NBS gateway](https://steemit.com/rudex/@rudex/newbitshares-nbs-gateway-on-decentralized-trading-platform-bitshares-rudex-launched) on bitshares, as well as a [public access point](https://market.nbsdex.io/) for the new network.\n- On 29th of September in the RUDEX Trollbox chat Dima BLCKCHND (@blockchained) announced a fork based on BTS 3.0 codebase named Graphene\n- On 12th of November 2020 team RuDEX [announced](https://steemit.com/blockchain/@rudex/graphene-blockchain-by-rudex-team-initial-distribution-announcement) an all win lottery to get the initial distribution and form a genesis block for the new chain\n- On 23rd of December the [results of the lottery](https://steemit.com/graphene/@rudex/graphene-lottery-end-announcement) were published, and all participants were given a stake and their funds were returned, possibly as a result of my critical comments on the lottery mechanics\n\n\n\n\n- On 12th of April 2021 a new chain [was launched](https://gph.ai/) with GPH token ticker, and the maximum supply of 100 million tokens.\n\n**UPD**\n*- On 27th of May 2021 RuDEX have [migrated](https://steemit.com/rudex/@rudex/announcement-of-rudex-migration-from-bitshares-to-graphene-dates-and-terms) to Graphene from Bitshares.*\n\n# And now you are here...\n\n\n\n\nOn 19th of May the private Honest.USD smartcoin honestly went into global settlement state. In the next 24 hours ⅔ of all coins in circulation during the black swan event were settled. Such a significant reduction in debt, small volume and price bounce allowed @Chibchombia (BTS: imm-ortal) to revive the asset on the very next day.\n\nOn 22th of May during the price safety margin of bitUSD was not enough, which resulted in a global settlement (“black swan event”). Selected witnesses abruptly stopped providing feeds for this assets, and despite the fact that the declared life time of the price feed is 24 hours, the mechanisms depending on the price feed stopped. After some time 2 feeds appeared, but the minimum required number is 3. Without feeds a manual asset revival is impossible, even if enough people want to bid on collateral for required amount. Abit [announced](https://bitsharestalk.org/index.php?topic=33051.0) that the collateral bids will be ignored, and he will revive the asset himself. Apparently he disabled witnesses feeds from being accepted, so they would not interfere with his plans.\n\nIt is worth noting that once bitUSD encountered a black swan, hourly feeds for HERO private MPA were also stopped by terradacs-bp and liondani witnesses. It is not clear yet if that was manipulation, or reliance on bitUSD feeds.\n\n\n\n\n\n# Authors position\n\nIf you try to become a committee member, you will get a message that the position is unpaid.\n\n\n\n\n[Abits](https://github.com/abitmore) actions resulted in a creation of a funding stream towards committee account fueled by new fees. On one hand only BSIP-86 directly creates revenues for the committee, and is probably not in effect right now, however most of the trading happens in committee bitassets, so the fees paid to MPA owners go to committee in most cases.\n\nDespite the lack of paid workers for development, updates of the core software are being developed, yet the display of the new fees in the UI are being delayed with responses in the vein of “we are not paid for it”.\n\nIn essence under the pretense of increasing the revenue of Bitshares as a DAC (Decentralized Autonomous Company) via the fee burn that would result in deflatory pressure, which is similar to the shares buyback by a company, that would result in the appreciation of BTS holders assets, the value flows were reformed in such a way, that most of the share (Market Fee) comes under control of the committee, that can be spent as they see fit. Where is the guarantee that the committee doesn’t block and unvote current members, to keep the status quo? Previous track record shows that on bitcrab’s suggestion under pretense of bitasset liquidity they have lost a lot of money by participating in margin trading. What will happen this time we are yet to see.\n\nIf we view Bitshares as a company, the committee as a Board of Directors, and BTS holders as stakeholders, then the stakeholders stock as unilaterally converted to preferred equity shares (non voting), and the Board of Directors is milking the company, leaving miniscule remainder of the market and transfer fees that go into reserve pool. **The revenue of those “directors” is based on the hidden fees, that most users are not aware of yet.**\n\nSuch a situation in a real company is nonsense and such activity is **illegal** in most countries. Abit and his team got scot free so far.\n\n That is one side of the situation.\n\nOn another hand shareholders themselves (lets call them majority holders) before all this mess were methodically scamming the users (mainly bitasset holders) by not having enough collateral against their debt obligations (bitassets) effectively stealing from them. To stop this fraud shareholders themselves would have to accept losses and lose their voting assets. If we take into the account that most users did not understand the intricacies of the platform the HODLers weren’t paying enough attention to the situation, such an abuse from major debt holders did not result in BTS price decline that was adequate to the outrageousness of the situation. The status quo with fake asset feeds (BSIP-42) and milking the reserve through the workers were a gainful strategy for them.\n\nBut as they say there is more. The author of [BSIP-42](https://github.com/bitshares/bsips/blob/master/bsip-0042.md) is not bitcrab, but **Abit**. Everything he could reply when that was pointed out was “That is in the past”.\n\nMy opinion on the NewBitshares is only that the new blockchain received mainly the cunning chinese as its community, which were fine with feed manipulation on Bitshares, and I was and still am against such methods, I did not have the inclination to follow them there.\n\n# In closing\n\nSince the new chain parameters are still not displayed in BitsharesUI, I decided to create a table with current parameters of main committee MPA’s including the new 1.0 ones.\n\n[Current bitasset parameters with “hidden” fees](https://golos.id/ru--blokcheijn/@akledirs/tekushie-parametry-bitassetov-so-skrytymi-komissiyami)",
"json_metadata": "{\"app\":\"peakd/2021.06.2\",\"format\":\"markdown\",\"description\":\"Such a situation in a real company is nonsense and such activity is illegal in most countries. Abit and his team got scot free so far.\",\"tags\":[\"blockchain\",\"bitshares\"],\"users\":[\"akledirs\",\"tnam0rken\",\"rudex\",\"blockchained\",\"Chibchombia\"],\"image\":[\"https://cdn.steemitimages.com/DQmb3jTeWvua1bU6FK16Uxvj1qZhrZf9oU7E4Wkkyge6tKs/image.png\",\"https://cdn.steemitimages.com/DQmPrwNuiFBSKAXBPfQDaQ4pFBQ7gLP9G29XoA4gvdUJpBs/image.png\",\"https://cdn.steemitimages.com/DQmTM8HCQJCjwYT3XiVW6WTpjtPdHaU1ZV4jtXGXo6H16Ms/image.png\",\"https://cdn.steemitimages.com/DQmbPbB73F8tm7yf3gKPzXpveEBwafuaVV7LeuJ1P7NWszn/image.png\",\"https://cdn.steemitimages.com/DQmewYHhbyCo99mSvzFpTZCe4UeUuDpkEGBsv97nr9Zs6es/image.png\",\"https://cdn.steemitimages.com/DQmYsobchTR8nfHKAyQfFWyvrMsoPhgNz5qcnacthjc6g8N/image.png\",\"https://cdn.steemitimages.com/DQmUfuVNip9tokPwmR7yN3wmwcqsTcqnYCKPiw3vKLeZpvx/image.png\",\"https://cdn.steemitimages.com/DQmb4bG9qopoq7uep4Kn7im1cjs8oxategzSzStZ7YzAeEp/image.png\",\"https://cdn.steemitimages.com/DQmSzhvZ7HnX8VBErCkoaHHNmJsTumXCaZ26NvrenrMBLBm/image.png\",\"https://cdn.steemitimages.com/DQmU6JkTsLFYosnHQTBnU6r9vaJSdiNxtdAA947hwzxWxEY/Screenshot%202021-06-21%20at%2013.14.28.png\"]}",
"parent_author": "",
"parent_permlink": "blockchain",
"permlink": "bitshares-drama",
"title": "Bitshares Drama"
}
],
"op_in_trx": 0,
"timestamp": "2021-06-21T11:38:30",
"trx_id": "b228d5fbe7ea0eb3e682f7a42047f5b449af5c42",
"trx_in_block": 3,
"virtual_op": false
}luueetangunvoted witness @blockchained2021/04/03 05:39:18
luueetangunvoted witness @blockchained
2021/04/03 05:39:18
| account | luueetang |
| approve | false |
| witness | blockchained |
| Transaction Info | Block #52694902/Trx 4378387ceae5fbad8d99547f5f49e420bf987e0c |
View Raw JSON Data
{
"block": 52694902,
"op": [
"account_witness_vote",
{
"account": "luueetang",
"approve": false,
"witness": "blockchained"
}
],
"op_in_trx": 0,
"timestamp": "2021-04-03T05:39:18",
"trx_id": "4378387ceae5fbad8d99547f5f49e420bf987e0c",
"trx_in_block": 19,
"virtual_op": false
}2021/01/16 02:23:39
2021/01/16 02:23:39
| author | hivebuzz |
| body | Congratulations @blockchained! You received a personal badge! <table><tr><td>https://images.hive.blog/70x70/http://hivebuzz.me/badges/birthday-4.png</td><td>Happy Hive Birthday! You are on the Hive blockchain for 4 years!</td></tr></table> <sub>_You can view your badges on [your board](https://hivebuzz.me/@blockchained) and compare yourself to others in the [Ranking](https://hivebuzz.me/ranking)_</sub> |
| json metadata | {"image":["http://hivebuzz.me/notify.t6.png"]} |
| parent author | blockchained |
| parent permlink | graphene-lottery-end-announcement |
| permlink | hivebuzz-notify-blockchained-20210116t022338000z |
| title | |
| Transaction Info | Block #50477851/Trx 47b88e36dcf4d5845ae77fb260f2852cc98dfd31 |
View Raw JSON Data
{
"block": 50477851,
"op": [
"comment",
{
"author": "hivebuzz",
"body": "Congratulations @blockchained! You received a personal badge!\n\n<table><tr><td>https://images.hive.blog/70x70/http://hivebuzz.me/badges/birthday-4.png</td><td>Happy Hive Birthday! You are on the Hive blockchain for 4 years!</td></tr></table>\n\n<sub>_You can view your badges on [your board](https://hivebuzz.me/@blockchained) and compare yourself to others in the [Ranking](https://hivebuzz.me/ranking)_</sub>\n",
"json_metadata": "{\"image\":[\"http://hivebuzz.me/notify.t6.png\"]}",
"parent_author": "blockchained",
"parent_permlink": "graphene-lottery-end-announcement",
"permlink": "hivebuzz-notify-blockchained-20210116t022338000z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2021-01-16T02:23:39",
"trx_id": "47b88e36dcf4d5845ae77fb260f2852cc98dfd31",
"trx_in_block": 11,
"virtual_op": false
}blockchainedupdated payout for graphene-lottery-end-announcement2020/12/30 20:51:30
blockchainedupdated payout for graphene-lottery-end-announcement
2020/12/30 20:51:30
| author | blockchained |
| permlink | graphene-lottery-end-announcement |
| Transaction Info | Block #50011301/Virtual Operation 4294967295:6 |
View Raw JSON Data
{
"block": 50011301,
"op": [
"comment_payout_update",
{
"author": "blockchained",
"permlink": "graphene-lottery-end-announcement"
}
],
"op_in_trx": 6,
"timestamp": "2020-12-30T20:51:30",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": true
}blockchainedreceived 0.059 HBD reward share for graphene-lottery-end-announcement2020/12/30 20:51:30
blockchainedreceived 0.059 HBD reward share for graphene-lottery-end-announcement
2020/12/30 20:51:30
| author | blockchained |
| author rewards | 261 |
| beneficiary payout value | 0.000 HBD |
| curator payout value | 0.029 HBD |
| payout | 0.059 HBD |
| permlink | graphene-lottery-end-announcement |
| total payout value | 0.028 HBD |
| Transaction Info | Block #50011301/Virtual Operation 4294967295:5 |
View Raw JSON Data
{
"block": 50011301,
"op": [
"comment_reward",
{
"author": "blockchained",
"author_rewards": 261,
"beneficiary_payout_value": "0.000 HBD",
"curator_payout_value": "0.029 HBD",
"payout": "0.059 HBD",
"permlink": "graphene-lottery-end-announcement",
"total_payout_value": "0.028 HBD"
}
],
"op_in_trx": 5,
"timestamp": "2020-12-30T20:51:30",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": true
}blockchainedreceived 0.014 HBD, 0.154 HP author reward for @blockchained / graphene-lottery-end-announcement2020/12/30 20:51:30
blockchainedreceived 0.014 HBD, 0.154 HP author reward for @blockchained / graphene-lottery-end-announcement
2020/12/30 20:51:30
| author | blockchained |
| curators vesting payout | 494.594988 VESTS |
| hbd payout | 0.014 HBD |
| hive payout | 0.000 HIVE |
| payout must be claimed | true |
| permlink | graphene-lottery-end-announcement |
| vesting payout | 250.161944 VESTS |
| Transaction Info | Block #50011301/Virtual Operation 4294967295:4 |
View Raw JSON Data
{
"block": 50011301,
"op": [
"author_reward",
{
"author": "blockchained",
"curators_vesting_payout": "494.594988 VESTS",
"hbd_payout": "0.014 HBD",
"hive_payout": "0.000 HIVE",
"payout_must_be_claimed": true,
"permlink": "graphene-lottery-end-announcement",
"vesting_payout": "250.161944 VESTS"
}
],
"op_in_trx": 4,
"timestamp": "2020-12-30T20:51:30",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": true
}yury-vaseffective vote applied for @blockchained / graphene-lottery-end-announcement2020/12/27 19:30:54
yury-vaseffective vote applied for @blockchained / graphene-lottery-end-announcement
2020/12/27 19:30:54
| author | blockchained |
| pending payout | 0.059 HBD |
| permlink | graphene-lottery-end-announcement |
| rshares | 240689419566 |
| total vote weight | 241928 |
| voter | yury-vas |
| weight | 109705 |
| Transaction Info | Block #49923519/Trx 0676749398ba39d7cffb15d37a0c40c1ef3ed631 |
View Raw JSON Data
{
"block": 49923519,
"op": [
"effective_comment_vote",
{
"author": "blockchained",
"pending_payout": "0.059 HBD",
"permlink": "graphene-lottery-end-announcement",
"rshares": 240689419566,
"total_vote_weight": 241928,
"voter": "yury-vas",
"weight": 109705
}
],
"op_in_trx": 1,
"timestamp": "2020-12-27T19:30:54",
"trx_id": "0676749398ba39d7cffb15d37a0c40c1ef3ed631",
"trx_in_block": 2,
"virtual_op": true
}yury-vasupvoted (100.00%) @blockchained / graphene-lottery-end-announcement2020/12/27 19:30:54
yury-vasupvoted (100.00%) @blockchained / graphene-lottery-end-announcement
2020/12/27 19:30:54
| author | blockchained |
| permlink | graphene-lottery-end-announcement |
| voter | yury-vas |
| weight | 10000 (100.00%) |
| Transaction Info | Block #49923519/Trx 0676749398ba39d7cffb15d37a0c40c1ef3ed631 |
View Raw JSON Data
{
"block": 49923519,
"op": [
"vote",
{
"author": "blockchained",
"permlink": "graphene-lottery-end-announcement",
"voter": "yury-vas",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2020-12-27T19:30:54",
"trx_id": "0676749398ba39d7cffb15d37a0c40c1ef3ed631",
"trx_in_block": 2,
"virtual_op": false
}suonghuynheffective vote applied for @blockchained / graphene-lottery-end-announcement2020/12/24 21:47:45
suonghuynheffective vote applied for @blockchained / graphene-lottery-end-announcement
2020/12/24 21:47:45
| author | blockchained |
| pending payout | 0.032 HBD |
| permlink | graphene-lottery-end-announcement |
| rshares | 10405841 |
| total vote weight | 132223 |
| voter | suonghuynh |
| weight | 5 (0.05%) |
| Transaction Info | Block #49840057/Trx ad521cf721cd3915166aa0ec5f8c3bd8f68f7f50 |
View Raw JSON Data
{
"block": 49840057,
"op": [
"effective_comment_vote",
{
"author": "blockchained",
"pending_payout": "0.032 HBD",
"permlink": "graphene-lottery-end-announcement",
"rshares": 10405841,
"total_vote_weight": 132223,
"voter": "suonghuynh",
"weight": 5
}
],
"op_in_trx": 1,
"timestamp": "2020-12-24T21:47:45",
"trx_id": "ad521cf721cd3915166aa0ec5f8c3bd8f68f7f50",
"trx_in_block": 20,
"virtual_op": true
}suonghuynhupvoted (2.29%) @blockchained / graphene-lottery-end-announcement2020/12/24 21:47:45
suonghuynhupvoted (2.29%) @blockchained / graphene-lottery-end-announcement
2020/12/24 21:47:45
| author | blockchained |
| permlink | graphene-lottery-end-announcement |
| voter | suonghuynh |
| weight | 229 (2.29%) |
| Transaction Info | Block #49840057/Trx ad521cf721cd3915166aa0ec5f8c3bd8f68f7f50 |
View Raw JSON Data
{
"block": 49840057,
"op": [
"vote",
{
"author": "blockchained",
"permlink": "graphene-lottery-end-announcement",
"voter": "suonghuynh",
"weight": 229
}
],
"op_in_trx": 0,
"timestamp": "2020-12-24T21:47:45",
"trx_id": "ad521cf721cd3915166aa0ec5f8c3bd8f68f7f50",
"trx_in_block": 20,
"virtual_op": false
}proctologiceffective vote applied for @blockchained / graphene-lottery-end-announcement2020/12/24 21:46:51
proctologiceffective vote applied for @blockchained / graphene-lottery-end-announcement
2020/12/24 21:46:51
| author | blockchained |
| pending payout | 0.032 HBD |
| permlink | graphene-lottery-end-announcement |
| rshares | 273351827658 |
| total vote weight | 132218 |
| voter | proctologic |
| weight | 132218 |
| Transaction Info | Block #49840039/Trx 58b3d7f443005d61a8e01a0dbb2233973b8f97ac |
View Raw JSON Data
{
"block": 49840039,
"op": [
"effective_comment_vote",
{
"author": "blockchained",
"pending_payout": "0.032 HBD",
"permlink": "graphene-lottery-end-announcement",
"rshares": 273351827658,
"total_vote_weight": 132218,
"voter": "proctologic",
"weight": 132218
}
],
"op_in_trx": 1,
"timestamp": "2020-12-24T21:46:51",
"trx_id": "58b3d7f443005d61a8e01a0dbb2233973b8f97ac",
"trx_in_block": 12,
"virtual_op": true
}proctologicupvoted (100.00%) @blockchained / graphene-lottery-end-announcement2020/12/24 21:46:51
proctologicupvoted (100.00%) @blockchained / graphene-lottery-end-announcement
2020/12/24 21:46:51
| author | blockchained |
| permlink | graphene-lottery-end-announcement |
| voter | proctologic |
| weight | 10000 (100.00%) |
| Transaction Info | Block #49840039/Trx 58b3d7f443005d61a8e01a0dbb2233973b8f97ac |
View Raw JSON Data
{
"block": 49840039,
"op": [
"vote",
{
"author": "blockchained",
"permlink": "graphene-lottery-end-announcement",
"voter": "proctologic",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2020-12-24T21:46:51",
"trx_id": "58b3d7f443005d61a8e01a0dbb2233973b8f97ac",
"trx_in_block": 12,
"virtual_op": false
}blockchainedpublished a new post: graphene-lottery-end-announcement2020/12/23 20:51:33
blockchainedpublished a new post: graphene-lottery-end-announcement
2020/12/23 20:51:33
| author | blockchained |
| body |  Yuletide greetings to all! As you all know, in our last post we announced the lottery to select genesis stake participants in the upcoming Graphene blockchain. We would like to thank everyone, who supported this experiment and registered tickets — you've passed the census, welcome to the club! As a new years present, we are returning 100% of BTC spent on registration. You heard us right: all your funds will be returned back to the accounts that were used to register the tickets. More information about the bonuses and the projects future you can learn by visiting the [Graphene community forum](https://forum.gph.ai/main-graphene/@blockchained/what-next), that was started today over the Golos blockchain. Join the forum discussion, and we wish you the best in the coming New Year! - Team RuDEX |
| json metadata | {"app":"peakd/2020.12.3","format":"markdown","description":"Graphene Lottery End Announcement","tags":["blockchain"],"users":["blockchained"],"links":["https://forum.gph.ai/main-graphene/@blockchained/what-next"],"image":["https://cdn.steemitimages.com/DQmQdP5a3C7hEwWoUDKtx2tFP4hXcoK1JLFUDQf2xjF3j8e/image.png"]} |
| parent author | |
| parent permlink | blockchain |
| permlink | graphene-lottery-end-announcement |
| title | Graphene Lottery End Announcement |
| Transaction Info | Block #49810205/Trx 1ebb2723da65fe6d160a00a420c5d5ccf4ce80a5 |
View Raw JSON Data
{
"block": 49810205,
"op": [
"comment",
{
"author": "blockchained",
"body": "\n\nYuletide greetings to all!\n\nAs you all know, in our last post we announced the lottery to select genesis stake participants in the upcoming Graphene blockchain.\n\nWe would like to thank everyone, who supported this experiment and registered tickets — you've passed the census, welcome to the club!\n\nAs a new years present, we are returning 100% of BTC spent on registration. You heard us right: all your funds will be returned back to the accounts that were used to register the tickets.\n\nMore information about the bonuses and the projects future you can learn by visiting the [Graphene community forum](https://forum.gph.ai/main-graphene/@blockchained/what-next), that was started today over the Golos blockchain.\n\n\nJoin the forum discussion, and we wish you the best in the coming New Year!\n\n- Team RuDEX",
"json_metadata": "{\"app\":\"peakd/2020.12.3\",\"format\":\"markdown\",\"description\":\"Graphene Lottery End Announcement\",\"tags\":[\"blockchain\"],\"users\":[\"blockchained\"],\"links\":[\"https://forum.gph.ai/main-graphene/@blockchained/what-next\"],\"image\":[\"https://cdn.steemitimages.com/DQmQdP5a3C7hEwWoUDKtx2tFP4hXcoK1JLFUDQf2xjF3j8e/image.png\"]}",
"parent_author": "",
"parent_permlink": "blockchain",
"permlink": "graphene-lottery-end-announcement",
"title": "Graphene Lottery End Announcement"
}
],
"op_in_trx": 0,
"timestamp": "2020-12-23T20:51:33",
"trx_id": "1ebb2723da65fe6d160a00a420c5d5ccf4ce80a5",
"trx_in_block": 8,
"virtual_op": false
}Manabar
Voting Power100.00%
Downvote Power100.00%
Resource Credits100.00%
Reputation Progress0.00%
{
"voting_manabar": {
"current_mana": 129041550266,
"last_update_time": 1745955345
},
"downvote_manabar": {
"current_mana": 32260387567,
"last_update_time": 1745955345
},
"rc_account": {
"account": "blockchained",
"delegated_rc": 0,
"max_rc": 131062299239,
"max_rc_creation_adjustment": {
"amount": "2020748973",
"nai": "@@000000037",
"precision": 6
},
"rc_manabar": {
"current_mana": 130586357290,
"last_update_time": 1745955345
},
"received_delegated_rc": 0
}
}Account Metadata
| POSTING JSON METADATA | |
| profile | {"profile_image":"https://i.imgur.com/RJjW8VP.png","name":"BLOCKCHAINED","about":"Decentralization is a product","website":"https://rudex.org/"} |
| JSON METADATA | |
| profile | {"website":"https://golos.id/@blockchained"} |
{
"posting_json_metadata": {
"profile": {
"profile_image": "https://i.imgur.com/RJjW8VP.png",
"name": "BLOCKCHAINED",
"about": "Decentralization is a product",
"website": "https://rudex.org/"
}
},
"json_metadata": {
"profile": {
"website": "https://golos.id/@blockchained"
}
}
}Auth Keys
Owner
Single Signature
Public Keys
STM88v4ckBjZsKJ5vjhM1PcyPp2QVVTvGeVXNy99MgqXX9idHXcXv1/1
Active
Single Signature
Public Keys
STM7NDcAdmUXdep3T1sRJLi6JWXBrc1651LRZ1ty5pveUdmsXR7Qi1/1
Posting
Single Signature
Public Keys
STM6szSXTRJECqeA5Wb2jXD26ocvB88R5ZyiFo2YkSdm5cCBpQNR51/1
Memo
STM8FzhiboKEgeeMkvp8SPuXCy9cb8TiuykztSQdzCB4ZTkqzhNgx
{
"owner": {
"account_auths": [],
"key_auths": [
[
"STM88v4ckBjZsKJ5vjhM1PcyPp2QVVTvGeVXNy99MgqXX9idHXcXv",
1
]
],
"weight_threshold": 1
},
"active": {
"account_auths": [],
"key_auths": [
[
"STM7NDcAdmUXdep3T1sRJLi6JWXBrc1651LRZ1ty5pveUdmsXR7Qi",
1
]
],
"weight_threshold": 1
},
"posting": {
"account_auths": [
[
"busy.app",
1
],
[
"dlive.app",
1
],
[
"dmania.app",
1
],
[
"memestagram-app",
1
],
[
"peakd.app",
1
],
[
"steempeak.app",
1
],
[
"streemian",
1
],
[
"utopian.app",
1
]
],
"key_auths": [
[
"STM6szSXTRJECqeA5Wb2jXD26ocvB88R5ZyiFo2YkSdm5cCBpQNR5",
1
]
],
"weight_threshold": 1
},
"memo": "STM8FzhiboKEgeeMkvp8SPuXCy9cb8TiuykztSQdzCB4ZTkqzhNgx"
}Witness Info
| id | 13197 |
| owner | blockchained |
| signing key | STM1111111111111111111111111111111114T1Anm |
| created | 2017-01-20T13:08:03 |
| url | quit |
| votes (HP) | 0.000 |
| virtual last update | 978779459453797039709604222 |
| virtual position | 108668563721703129770255632516018933677 |
| virtual scheduled time | 231613803200214113152572771955458882000 |
| total missed | 54 |
| last aslot | 29,194,784 |
| last confirmed block num | 29,098,727 |
| running version | 0.20.8 |
| hardfork version vote | 0.20.0 |
| hardfork time vote | 2018-09-25T15:00:00 |
| available witness account subsidies | 0 |
| props | |
| account_creation_fee | 3.000 HIVE |
| maximum_block_size | 65,536 |
| account_subsidy_budget | 797 |
| account_subsidy_decay | 347321 |
| hbd_interest_rate | 0 |
| hbd_exchange_rate | |
| base | 0.270 HBD |
| quote | 1.000 HIVE |
| pow_worker | 0 |
| last_hbd_exchange_update | 2019-02-07T05:00:06 |
{
"available_witness_account_subsidies": 0,
"created": "2017-01-20T13:08:03",
"hardfork_time_vote": "2018-09-25T15:00:00",
"hardfork_version_vote": "0.20.0",
"hbd_exchange_rate": {
"base": "0.270 HBD",
"quote": "1.000 HIVE"
},
"id": 13197,
"last_aslot": 29194784,
"last_confirmed_block_num": 29098727,
"last_hbd_exchange_update": "2019-02-07T05:00:06",
"last_work": "0000000000000000000000000000000000000000000000000000000000000000",
"owner": "blockchained",
"pow_worker": 0,
"props": {
"account_creation_fee": "3.000 HIVE",
"account_subsidy_budget": 797,
"account_subsidy_decay": 347321,
"hbd_interest_rate": 0,
"maximum_block_size": 65536
},
"running_version": "0.20.8",
"signing_key": "STM1111111111111111111111111111111114T1Anm",
"total_missed": 54,
"url": "quit",
"virtual_last_update": "978779459453797039709604222",
"virtual_position": "108668563721703129770255632516018933677",
"virtual_scheduled_time": "231613803200214113152572771955458882000",
"votes": 0
}Witness Votes
0 / 30
No active witness votes.
[]
