VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS60.24%
Net Worth
2.817USD
STEEM
0.193STEEM
SBD
0.153SBD
Own SP
47.118SP
Detailed Balance
| STEEM | ||
| balance | 0.193STEEM | STEEM |
| market_balance | 0.000STEEM | STEEM |
| savings_balance | 0.000STEEM | STEEM |
| reward_steem_balance | 0.000STEEM | STEEM |
| STEEM POWER | ||
| Own SP | 47.118SP | SP |
| Delegated Out | 0.000SP | SP |
| Delegation In | 0.000SP | SP |
| Effective Power | 47.118SP | SP |
| Reward SP (pending) | 0.000SP | SP |
| SBD | ||
| sbd_balance | 0.153SBD | SBD |
| sbd_conversions | 0.000SBD | SBD |
| sbd_market_balance | 0.000SBD | SBD |
| savings_sbd_balance | 0.000SBD | SBD |
| reward_sbd_balance | 0.000SBD | SBD |
{
"balance": "0.193 STEEM",
"savings_balance": "0.000 STEEM",
"reward_steem_balance": "0.000 STEEM",
"vesting_shares": "76626.941252 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "0.000000 VESTS",
"sbd_balance": "0.153 SBD",
"savings_sbd_balance": "0.000 SBD",
"reward_sbd_balance": "0.000 SBD",
"conversions": []
}Account Info
| name | happybeing |
| id | 10689 |
| rank | 42,638 |
| reputation | 41926828278 |
| created | 2016-06-02T10:15:06 |
| recovery_account | steem |
| proxy | None |
| post_count | 2 |
| comment_count | 0 |
| lifetime_vote_count | 0 |
| witnesses_voted_for | 0 |
| last_post | 2016-09-06T09:12:24 |
| last_root_post | 1970-01-01T00:00:00 |
| last_vote_time | 2016-08-01T17:02:33 |
| proxied_vsf_votes | 0, 0, 0, 0 |
| can_vote | 1 |
| voting_power | 9,949 |
| delayed_votes | 0 |
| balance | 0.193 STEEM |
| savings_balance | 0.000 STEEM |
| sbd_balance | 0.153 SBD |
| savings_sbd_balance | 0.000 SBD |
| vesting_shares | 76626.941252 VESTS |
| delegated_vesting_shares | 0.000000 VESTS |
| received_vesting_shares | 0.000000 VESTS |
| reward_vesting_balance | 0.000000 VESTS |
| vesting_balance | 0.000 STEEM |
| 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 | 1970-01-01T00:00:00 |
| last_account_update | 1970-01-01T00:00:00 |
| mined | No |
| sbd_seconds | 0 |
| sbd_last_interest_payment | 1970-01-01T00:00:00 |
| savings_sbd_last_interest_payment | 1970-01-01T00:00:00 |
{
"id": 10689,
"name": "happybeing",
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7gszigy2i4DgwUKx2Ms1Q2sZMV6N8WrqfXCPZfDwixMZDKWaAy",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM6N4XQz9fT3qcemvEdZWvZNBpFkoYggZqSsKALmnNPWU43YG6Cu",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7ANiBSpBBHFnDzwvM1Fk9jNEyg1f5cc8CE1LqUZHTFaKEfRkJs",
1
]
]
},
"memo_key": "STM8BJAA6pL3ouJhK3cUXAd4C6YzePnPMGYwtyRfvpD5j8HYeoYiN",
"json_metadata": "",
"posting_json_metadata": "",
"proxy": "",
"last_owner_update": "1970-01-01T00:00:00",
"last_account_update": "1970-01-01T00:00:00",
"created": "2016-06-02T10:15:06",
"mined": false,
"recovery_account": "steem",
"last_account_recovery": "1970-01-01T00:00:00",
"reset_account": "null",
"comment_count": 0,
"lifetime_vote_count": 0,
"post_count": 2,
"can_vote": true,
"voting_manabar": {
"current_mana": 9949,
"last_update_time": 1470070953
},
"downvote_manabar": {
"current_mana": 0,
"last_update_time": 1464862506
},
"voting_power": 9949,
"balance": "0.193 STEEM",
"savings_balance": "0.000 STEEM",
"sbd_balance": "0.153 SBD",
"sbd_seconds": "0",
"sbd_seconds_last_update": "2016-10-06T16:37:57",
"sbd_last_interest_payment": "1970-01-01T00:00:00",
"savings_sbd_balance": "0.000 SBD",
"savings_sbd_seconds": "0",
"savings_sbd_seconds_last_update": "1970-01-01T00:00:00",
"savings_sbd_last_interest_payment": "1970-01-01T00:00:00",
"savings_withdraw_requests": 0,
"reward_sbd_balance": "0.000 SBD",
"reward_steem_balance": "0.000 STEEM",
"reward_vesting_balance": "0.000000 VESTS",
"reward_vesting_steem": "0.000 STEEM",
"vesting_shares": "76626.941252 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "0.000000 VESTS",
"vesting_withdraw_rate": "0.000000 VESTS",
"next_vesting_withdrawal": "1969-12-31T23:59:59",
"withdrawn": 0,
"to_withdraw": 0,
"withdraw_routes": 0,
"curation_rewards": 0,
"posting_rewards": 1148,
"proxied_vsf_votes": [
0,
0,
0,
0
],
"witnesses_voted_for": 0,
"last_post": "2016-09-06T09:12:24",
"last_root_post": "1970-01-01T00:00:00",
"last_vote_time": "2016-08-01T17:02:33",
"post_bandwidth": 0,
"pending_claimed_accounts": 0,
"vesting_balance": "0.000 STEEM",
"reputation": "41926828278",
"transfer_history": [],
"market_history": [],
"post_history": [],
"vote_history": [],
"other_history": [],
"witness_votes": [],
"tags_usage": [],
"guest_bloggers": [],
"rank": 42638
}Withdraw Routes
| Incoming | Outgoing |
|---|---|
Empty | Empty |
{
"incoming": [],
"outgoing": []
}From Date
To Date
2018/01/11 21:20:33
2018/01/11 21:20:33
| voter | maidsafefan |
| author | happybeing |
| permlink | re-iainc-re-happybeing-re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160906t091222861z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18894782/Trx abf575d147e8571edc21cf6296eceed8b076f4f1 |
View Raw JSON Data
{
"trx_id": "abf575d147e8571edc21cf6296eceed8b076f4f1",
"block": 18894782,
"trx_in_block": 18,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-11T21:20:33",
"op": [
"vote",
{
"voter": "maidsafefan",
"author": "happybeing",
"permlink": "re-iainc-re-happybeing-re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160906t091222861z",
"weight": 10000
}
]
}2018/01/11 21:20:09
2018/01/11 21:20:09
| voter | maidsafefan |
| author | happybeing |
| permlink | re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18894774/Trx 733cb5bfcbe4ab16e42756468d417a8ab0da5367 |
View Raw JSON Data
{
"trx_id": "733cb5bfcbe4ab16e42756468d417a8ab0da5367",
"block": 18894774,
"trx_in_block": 29,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-11T21:20:09",
"op": [
"vote",
{
"voter": "maidsafefan",
"author": "happybeing",
"permlink": "re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z",
"weight": 10000
}
]
}2017/11/17 15:51:18
2017/11/17 15:51:18
| voter | dugcampbell |
| author | happybeing |
| permlink | re-iainc-re-happybeing-re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160906t091222861z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #17305148/Trx 8a4145485c3f0d95dcc4368d2871569bb89765ab |
View Raw JSON Data
{
"trx_id": "8a4145485c3f0d95dcc4368d2871569bb89765ab",
"block": 17305148,
"trx_in_block": 15,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-11-17T15:51:18",
"op": [
"vote",
{
"voter": "dugcampbell",
"author": "happybeing",
"permlink": "re-iainc-re-happybeing-re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160906t091222861z",
"weight": 10000
}
]
}2017/11/17 15:50:36
2017/11/17 15:50:36
| voter | dugcampbell |
| author | happybeing |
| permlink | re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #17305134/Trx c9db20b5e2e6afee8a968657ef19be0e45492438 |
View Raw JSON Data
{
"trx_id": "c9db20b5e2e6afee8a968657ef19be0e45492438",
"block": 17305134,
"trx_in_block": 22,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-11-17T15:50:36",
"op": [
"vote",
{
"voter": "dugcampbell",
"author": "happybeing",
"permlink": "re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z",
"weight": 10000
}
]
}2017/09/25 11:56:18
2017/09/25 11:56:18
| voter | dask |
| author | happybeing |
| permlink | re-iainc-re-happybeing-re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160906t091222861z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #15775255/Trx 8437d7e59194e05bbc174bc4e492c9b86157730d |
View Raw JSON Data
{
"trx_id": "8437d7e59194e05bbc174bc4e492c9b86157730d",
"block": 15775255,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-25T11:56:18",
"op": [
"vote",
{
"voter": "dask",
"author": "happybeing",
"permlink": "re-iainc-re-happybeing-re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160906t091222861z",
"weight": 10000
}
]
}2017/09/25 11:56:00
2017/09/25 11:56:00
| voter | dask |
| author | happybeing |
| permlink | re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #15775249/Trx adab12fa6afdd392a082fd4e7de99f9dd5f5c939 |
View Raw JSON Data
{
"trx_id": "adab12fa6afdd392a082fd4e7de99f9dd5f5c939",
"block": 15775249,
"trx_in_block": 27,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-25T11:56:00",
"op": [
"vote",
{
"voter": "dask",
"author": "happybeing",
"permlink": "re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z",
"weight": 10000
}
]
}2017/08/04 20:30:03
2017/08/04 20:30:03
| voter | goldlocke |
| author | happybeing |
| permlink | re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #14289463/Trx e095eeab8eb71d3feeaac8d3004f7634686b8c78 |
View Raw JSON Data
{
"trx_id": "e095eeab8eb71d3feeaac8d3004f7634686b8c78",
"block": 14289463,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-08-04T20:30:03",
"op": [
"vote",
{
"voter": "goldlocke",
"author": "happybeing",
"permlink": "re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z",
"weight": 10000
}
]
}2017/07/13 04:24:51
2017/07/13 04:24:51
| voter | bggy |
| author | happybeing |
| permlink | re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #13637294/Trx 807ad6f4e1014be6afab96b6eb4d3aa6952a96ab |
View Raw JSON Data
{
"trx_id": "807ad6f4e1014be6afab96b6eb4d3aa6952a96ab",
"block": 13637294,
"trx_in_block": 11,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-07-13T04:24:51",
"op": [
"vote",
{
"voter": "bggy",
"author": "happybeing",
"permlink": "re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z",
"weight": 10000
}
]
}2017/06/08 03:17:12
2017/06/08 03:17:12
| voter | qedqubit |
| author | happybeing |
| permlink | re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #12629603/Trx 5c914a9ff93950d0c691c484475e2b41f70e41f6 |
View Raw JSON Data
{
"trx_id": "5c914a9ff93950d0c691c484475e2b41f70e41f6",
"block": 12629603,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-06-08T03:17:12",
"op": [
"vote",
{
"voter": "qedqubit",
"author": "happybeing",
"permlink": "re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z",
"weight": 10000
}
]
}| voter | luckyluk |
| author | happybeing |
| permlink | re-iainc-re-happybeing-re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160906t091222861z |
| weight | 7400 (74.00%) |
| Transaction Info | Block #8903695/Trx 4a85021cb63a0e9617ff5ecfadd31779ceb0d131 |
View Raw JSON Data
{
"trx_id": "4a85021cb63a0e9617ff5ecfadd31779ceb0d131",
"block": 8903695,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-01-29T15:10:06",
"op": [
"vote",
{
"voter": "luckyluk",
"author": "happybeing",
"permlink": "re-iainc-re-happybeing-re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160906t091222861z",
"weight": 7400
}
]
}| voter | luckyluk |
| author | happybeing |
| permlink | re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z |
| weight | 7400 (74.00%) |
| Transaction Info | Block #8903690/Trx 8c93d29dd076fc9da2f8146099abb9396f7b9cf5 |
View Raw JSON Data
{
"trx_id": "8c93d29dd076fc9da2f8146099abb9396f7b9cf5",
"block": 8903690,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-01-29T15:09:51",
"op": [
"vote",
{
"voter": "luckyluk",
"author": "happybeing",
"permlink": "re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z",
"weight": 7400
}
]
}happybeingfollowed @johan-nygren
happybeingfollowed @johan-nygren
| required auths | [] |
| required posting auths | ["happybeing"] |
| id | follow |
| json | ["follow",{"follower":"happybeing","following":"johan-nygren","what":["blog"]}] |
| Transaction Info | Block #6038238/Trx b6232f0c2eb0a7b312a1cbfedaf70135f23edef7 |
View Raw JSON Data
{
"trx_id": "b6232f0c2eb0a7b312a1cbfedaf70135f23edef7",
"block": 6038238,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-10-21T22:36:06",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"happybeing"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"happybeing\",\"following\":\"johan-nygren\",\"what\":[\"blog\"]}]"
}
]
}happybeingreceived 0.096 STEEM, 0.076 SBD, 0.476 SP author reward for @happybeing / re-iainc-re-happybeing-re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160906t091222861z
happybeingreceived 0.096 STEEM, 0.076 SBD, 0.476 SP author reward for @happybeing / re-iainc-re-happybeing-re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160906t091222861z
| author | happybeing |
| permlink | re-iainc-re-happybeing-re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160906t091222861z |
| sbd payout | 0.076 SBD |
| steem payout | 0.096 STEEM |
| vesting payout | 773.375748 VESTS |
| Transaction Info | Block #5599325/Virtual Operation #15 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 5599325,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 15,
"timestamp": "2016-10-06T16:37:57",
"op": [
"author_reward",
{
"author": "happybeing",
"permlink": "re-iainc-re-happybeing-re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160906t091222861z",
"sbd_payout": "0.076 SBD",
"steem_payout": "0.096 STEEM",
"vesting_payout": "773.375748 VESTS"
}
]
}happybeingreceived 0.097 STEEM, 0.077 SBD, 0.481 SP author reward for @happybeing / re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z
happybeingreceived 0.097 STEEM, 0.077 SBD, 0.481 SP author reward for @happybeing / re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z
| author | happybeing |
| permlink | re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z |
| sbd payout | 0.077 SBD |
| steem payout | 0.097 STEEM |
| vesting payout | 781.488081 VESTS |
| Transaction Info | Block #5599325/Virtual Operation #7 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 5599325,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 7,
"timestamp": "2016-10-06T16:37:57",
"op": [
"author_reward",
{
"author": "happybeing",
"permlink": "re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z",
"sbd_payout": "0.077 SBD",
"steem_payout": "0.097 STEEM",
"vesting_payout": "781.488081 VESTS"
}
]
}| voter | mranderson |
| author | happybeing |
| permlink | re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4879010/Trx 58c599025f8d103a297ac2066cf769f5e62ef688 |
View Raw JSON Data
{
"trx_id": "58c599025f8d103a297ac2066cf769f5e62ef688",
"block": 4879010,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-09-11T14:23:24",
"op": [
"vote",
{
"voter": "mranderson",
"author": "happybeing",
"permlink": "re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z",
"weight": 10000
}
]
}| voter | helen.tan |
| author | happybeing |
| permlink | re-iainc-re-happybeing-re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160906t091222861z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4752628/Trx adef74c851b4e20037ffbcdf93e8b0c2c123f2bc |
View Raw JSON Data
{
"trx_id": "adef74c851b4e20037ffbcdf93e8b0c2c123f2bc",
"block": 4752628,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-09-07T04:41:18",
"op": [
"vote",
{
"voter": "helen.tan",
"author": "happybeing",
"permlink": "re-iainc-re-happybeing-re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160906t091222861z",
"weight": 10000
}
]
}| parent author | happybeing |
| parent permlink | re-iainc-re-happybeing-re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160906t091222861z |
| author | officialfuzzy |
| permlink | re-happybeing-re-iainc-re-happybeing-re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160907t044109844z |
| title | |
| body | Just to let you guys know. This thread updated me quite a bit on maidsafe. Id love to have them join our hangouts sometime to talk more about it. So if you think this little back and forth was negative in any way at least know I walked away with some good crypto value for my brain ;) |
| json metadata | {"tags":["blockchain"]} |
| Transaction Info | Block #4752627/Trx 8d4fed96373d0726a673afbfffa8391972d2429b |
View Raw JSON Data
{
"trx_id": "8d4fed96373d0726a673afbfffa8391972d2429b",
"block": 4752627,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-09-07T04:41:15",
"op": [
"comment",
{
"parent_author": "happybeing",
"parent_permlink": "re-iainc-re-happybeing-re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160906t091222861z",
"author": "officialfuzzy",
"permlink": "re-happybeing-re-iainc-re-happybeing-re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160907t044109844z",
"title": "",
"body": "Just to let you guys know. This thread updated me quite a bit on maidsafe. Id love to have them join our hangouts sometime to talk more about it. So if you think this little back and forth was negative in any way at least know I walked away with some good crypto value for my brain ;)",
"json_metadata": "{\"tags\":[\"blockchain\"]}"
}
]
}| voter | moon |
| author | happybeing |
| permlink | re-iainc-re-happybeing-re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160906t091222861z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4752627/Trx fd3f480f555ef0e88142777a615d5246359bf903 |
View Raw JSON Data
{
"trx_id": "fd3f480f555ef0e88142777a615d5246359bf903",
"block": 4752627,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-09-07T04:41:15",
"op": [
"vote",
{
"voter": "moon",
"author": "happybeing",
"permlink": "re-iainc-re-happybeing-re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160906t091222861z",
"weight": 10000
}
]
}| voter | bunny |
| author | happybeing |
| permlink | re-iainc-re-happybeing-re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160906t091222861z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4752626/Trx c43e5f56d25ea64d329ee78d86061d7fd796fb25 |
View Raw JSON Data
{
"trx_id": "c43e5f56d25ea64d329ee78d86061d7fd796fb25",
"block": 4752626,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-09-07T04:41:12",
"op": [
"vote",
{
"voter": "bunny",
"author": "happybeing",
"permlink": "re-iainc-re-happybeing-re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160906t091222861z",
"weight": 10000
}
]
}| voter | daniel.pan |
| author | happybeing |
| permlink | re-iainc-re-happybeing-re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160906t091222861z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4752625/Trx 1b64fa682f5fe9c0b04a9837ea0b2c1f3361eff5 |
View Raw JSON Data
{
"trx_id": "1b64fa682f5fe9c0b04a9837ea0b2c1f3361eff5",
"block": 4752625,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-09-07T04:41:09",
"op": [
"vote",
{
"voter": "daniel.pan",
"author": "happybeing",
"permlink": "re-iainc-re-happybeing-re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160906t091222861z",
"weight": 10000
}
]
}| voter | boy |
| author | happybeing |
| permlink | re-iainc-re-happybeing-re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160906t091222861z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4752624/Trx d1764ad5cc355789f9dd06b25b3d22faee98de52 |
View Raw JSON Data
{
"trx_id": "d1764ad5cc355789f9dd06b25b3d22faee98de52",
"block": 4752624,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-09-07T04:41:06",
"op": [
"vote",
{
"voter": "boy",
"author": "happybeing",
"permlink": "re-iainc-re-happybeing-re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160906t091222861z",
"weight": 10000
}
]
}| voter | healthcare |
| author | happybeing |
| permlink | re-iainc-re-happybeing-re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160906t091222861z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4752623/Trx 717e98f6bc206804f50714f06a9caa1820bb9339 |
View Raw JSON Data
{
"trx_id": "717e98f6bc206804f50714f06a9caa1820bb9339",
"block": 4752623,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-09-07T04:41:03",
"op": [
"vote",
{
"voter": "healthcare",
"author": "happybeing",
"permlink": "re-iainc-re-happybeing-re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160906t091222861z",
"weight": 10000
}
]
}| voter | mini |
| author | happybeing |
| permlink | re-iainc-re-happybeing-re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160906t091222861z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4752622/Trx d759e74630ee2d899c26793600bb2274b419b661 |
View Raw JSON Data
{
"trx_id": "d759e74630ee2d899c26793600bb2274b419b661",
"block": 4752622,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-09-07T04:41:00",
"op": [
"vote",
{
"voter": "mini",
"author": "happybeing",
"permlink": "re-iainc-re-happybeing-re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160906t091222861z",
"weight": 10000
}
]
}| voter | bue |
| author | happybeing |
| permlink | re-iainc-re-happybeing-re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160906t091222861z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4752621/Trx af6f9eabf1bebacca4b863f50e279075c3bc708f |
View Raw JSON Data
{
"trx_id": "af6f9eabf1bebacca4b863f50e279075c3bc708f",
"block": 4752621,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-09-07T04:40:57",
"op": [
"vote",
{
"voter": "bue",
"author": "happybeing",
"permlink": "re-iainc-re-happybeing-re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160906t091222861z",
"weight": 10000
}
]
}| voter | bue-witness |
| author | happybeing |
| permlink | re-iainc-re-happybeing-re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160906t091222861z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4752620/Trx d6574c3b91bc35f82079f59607f078989d192e64 |
View Raw JSON Data
{
"trx_id": "d6574c3b91bc35f82079f59607f078989d192e64",
"block": 4752620,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-09-07T04:40:54",
"op": [
"vote",
{
"voter": "bue-witness",
"author": "happybeing",
"permlink": "re-iainc-re-happybeing-re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160906t091222861z",
"weight": 10000
}
]
}| voter | helen.tan |
| author | happybeing |
| permlink | re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4752610/Trx 3a4e435c75a44a943b460d7f3f732d5b3210c13f |
View Raw JSON Data
{
"trx_id": "3a4e435c75a44a943b460d7f3f732d5b3210c13f",
"block": 4752610,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-09-07T04:40:24",
"op": [
"vote",
{
"voter": "helen.tan",
"author": "happybeing",
"permlink": "re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z",
"weight": 10000
}
]
}| voter | moon |
| author | happybeing |
| permlink | re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4752609/Trx 3109699df33b71fdedd17e4e294d6eafabf3a8cb |
View Raw JSON Data
{
"trx_id": "3109699df33b71fdedd17e4e294d6eafabf3a8cb",
"block": 4752609,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-09-07T04:40:21",
"op": [
"vote",
{
"voter": "moon",
"author": "happybeing",
"permlink": "re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z",
"weight": 10000
}
]
}| voter | bunny |
| author | happybeing |
| permlink | re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4752608/Trx 4750d22053f1d5f2c6a05c7dd25382fe3df28610 |
View Raw JSON Data
{
"trx_id": "4750d22053f1d5f2c6a05c7dd25382fe3df28610",
"block": 4752608,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-09-07T04:40:18",
"op": [
"vote",
{
"voter": "bunny",
"author": "happybeing",
"permlink": "re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z",
"weight": 10000
}
]
}| voter | daniel.pan |
| author | happybeing |
| permlink | re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4752607/Trx 2dd2a6330718808597d193a156ee436eb7f07e60 |
View Raw JSON Data
{
"trx_id": "2dd2a6330718808597d193a156ee436eb7f07e60",
"block": 4752607,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-09-07T04:40:15",
"op": [
"vote",
{
"voter": "daniel.pan",
"author": "happybeing",
"permlink": "re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z",
"weight": 10000
}
]
}| voter | boy |
| author | happybeing |
| permlink | re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4752606/Trx e694d3743b2fde03efe1e06899b0e3d88f871064 |
View Raw JSON Data
{
"trx_id": "e694d3743b2fde03efe1e06899b0e3d88f871064",
"block": 4752606,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-09-07T04:40:12",
"op": [
"vote",
{
"voter": "boy",
"author": "happybeing",
"permlink": "re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z",
"weight": 10000
}
]
}| voter | healthcare |
| author | happybeing |
| permlink | re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4752605/Trx fc8a577740c6c99258017a445fefdb4804ad4bec |
View Raw JSON Data
{
"trx_id": "fc8a577740c6c99258017a445fefdb4804ad4bec",
"block": 4752605,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-09-07T04:40:09",
"op": [
"vote",
{
"voter": "healthcare",
"author": "happybeing",
"permlink": "re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z",
"weight": 10000
}
]
}| voter | mini |
| author | happybeing |
| permlink | re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4752604/Trx 317a3ae14154d6db8fd1ca51c738ba7545295939 |
View Raw JSON Data
{
"trx_id": "317a3ae14154d6db8fd1ca51c738ba7545295939",
"block": 4752604,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-09-07T04:40:06",
"op": [
"vote",
{
"voter": "mini",
"author": "happybeing",
"permlink": "re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z",
"weight": 10000
}
]
}| voter | bue |
| author | happybeing |
| permlink | re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4752603/Trx 22f9ef8900406342e8678c40bcb0c840e45d2e2a |
View Raw JSON Data
{
"trx_id": "22f9ef8900406342e8678c40bcb0c840e45d2e2a",
"block": 4752603,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-09-07T04:40:03",
"op": [
"vote",
{
"voter": "bue",
"author": "happybeing",
"permlink": "re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z",
"weight": 10000
}
]
}| voter | bue-witness |
| author | happybeing |
| permlink | re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4752602/Trx d2f161862885c19dec3ceb5aa779623f038bcea6 |
View Raw JSON Data
{
"trx_id": "d2f161862885c19dec3ceb5aa779623f038bcea6",
"block": 4752602,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-09-07T04:40:00",
"op": [
"vote",
{
"voter": "bue-witness",
"author": "happybeing",
"permlink": "re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z",
"weight": 10000
}
]
}| voter | fuzzyvest |
| author | happybeing |
| permlink | re-iainc-re-happybeing-re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160906t091222861z |
| weight | 1300 (13.00%) |
| Transaction Info | Block #4752600/Trx 560dee1350df28d0148cd53af8352c6558dcbf64 |
View Raw JSON Data
{
"trx_id": "560dee1350df28d0148cd53af8352c6558dcbf64",
"block": 4752600,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-09-07T04:39:54",
"op": [
"vote",
{
"voter": "fuzzyvest",
"author": "happybeing",
"permlink": "re-iainc-re-happybeing-re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160906t091222861z",
"weight": 1300
}
]
}| voter | officialfuzzy |
| author | happybeing |
| permlink | re-iainc-re-happybeing-re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160906t091222861z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4752598/Trx 2d69749986409e59a5803cbac2eec7601d3a9acc |
View Raw JSON Data
{
"trx_id": "2d69749986409e59a5803cbac2eec7601d3a9acc",
"block": 4752598,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-09-07T04:39:48",
"op": [
"vote",
{
"voter": "officialfuzzy",
"author": "happybeing",
"permlink": "re-iainc-re-happybeing-re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160906t091222861z",
"weight": 10000
}
]
}| voter | fuzzyvest |
| author | happybeing |
| permlink | re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z |
| weight | 1300 (13.00%) |
| Transaction Info | Block #4752587/Trx 97b4cc1a16053e6a23ec4d21b28dc01da38debfc |
View Raw JSON Data
{
"trx_id": "97b4cc1a16053e6a23ec4d21b28dc01da38debfc",
"block": 4752587,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-09-07T04:39:15",
"op": [
"vote",
{
"voter": "fuzzyvest",
"author": "happybeing",
"permlink": "re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z",
"weight": 1300
}
]
}| voter | officialfuzzy |
| author | happybeing |
| permlink | re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4752584/Trx 175f61536649b7006148404e7c7fbefc5c2dc8c4 |
View Raw JSON Data
{
"trx_id": "175f61536649b7006148404e7c7fbefc5c2dc8c4",
"block": 4752584,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-09-07T04:39:06",
"op": [
"vote",
{
"voter": "officialfuzzy",
"author": "happybeing",
"permlink": "re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z",
"weight": 10000
}
]
}| voter | psybin |
| author | happybeing |
| permlink | re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4739007/Trx 4f3436190407d36398309fa0b22001d1387e5abf |
View Raw JSON Data
{
"trx_id": "4f3436190407d36398309fa0b22001d1387e5abf",
"block": 4739007,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-09-06T17:18:33",
"op": [
"vote",
{
"voter": "psybin",
"author": "happybeing",
"permlink": "re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z",
"weight": 10000
}
]
}| voter | mindposeidon |
| author | happybeing |
| permlink | re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4731468/Trx be00ac2b73b300bb1ecf3aa834fd9551df595b78 |
View Raw JSON Data
{
"trx_id": "be00ac2b73b300bb1ecf3aa834fd9551df595b78",
"block": 4731468,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-09-06T11:01:18",
"op": [
"vote",
{
"voter": "mindposeidon",
"author": "happybeing",
"permlink": "re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z",
"weight": 10000
}
]
}| parent author | iainc |
| parent permlink | re-happybeing-re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160906t075126699z |
| author | happybeing |
| permlink | re-iainc-re-happybeing-re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160906t091222861z |
| title | |
| body | And mine also from the SAFE forum :-) ... Thanks for responding Chris. I didn't mean to suggest you were negative overall, but have pointed out specific instances where I believe you give your readers a misleading or factually incorrect picture. I think those points still stand (terminology excepted which you say has been updated - thanks). For me it is not about negative or positive spin or attitude, but making statements that are consistent with the situation and the facts. For example, you made some very strong statements, highly discouraging to any developers reading, about the difficulty of developing, and made no mention that these serious difficulties were being addressed as you published. I also explained to you that things - at this point in time - are not as difficult as you seem to believe them to be which is why I mentioned the already working dynamic web apps, written in JavaScript using the *existing* API, *as well as* the imminent improvements and extensions in this area. I am not a MaidSafe developer BTW, I'm one of those "external developers" you were thinking of as you wrote, albeit one who is willing to dig around in the early stages of a project. That's how you gain commercial advantage after all. You have now explained how your personal experience has been factored into your opinion in the article, but that experience was not presented in the article which prevents the project from responding to or address those issues. Regarding the SAFE Ecosystem, which I pointed out is a major diferentiator of this project, you above take issue with one element that, with your current level of understanding, you deem impractical (pay once, store forever). We're not stupid here in this community, so we are aware that there are things about this project that appear implausible, or are hard to accept, and you are not the only person who wants to see this before believing it. It's not even close to the most contentious such issue debated here :slight_smile: I have some scepticism about this too, but I do also understand the basis for this claim and can see that it could well work. So it should not be dismissed either, and even if *you* choose to do so, you could still allude to an ecosystem of rewards that the project has designed to encourage adoption by stakeholders: users, resource and storage providers, app developers, and core developers. The project is revolutionary, and it has so much to it that nobody can be expected to understand or believe it all until it is working. Me too :slight_smile: but I don't think that's a reason to dismiss that whole section especially if you are going to make comparisons with other projects. As I said, it's up to you what you do with the feedback. I didn't assume you'd update your article, but I don't think your reasoning for what you wrote stands up and I think you do your readers a disservice in key aspects. Particularly the situation that exists for interested developers, and ignoring key features that differentiate this project. [Please be aware I'm a member of the community here, not part of MaidSafe and not a developer any more though I still tinker as mentioned. I'm a retired developer who has seen it and done it, and has dug deep into this project, and been continually impressed by it in all respects. This is why I've stuck around, and why I'll take the time to give people feedback when they request it. Of course, people don't always like my feedback or make immediate use of it, and that's perfectly fine. I gave it willingly and in good faith, so please don't take it personally, or assume that I'm expecting anything from you.] |
| json metadata | {"tags":["blockchain"]} |
| Transaction Info | Block #4729295/Trx ebd9f2cbab55be5c4f4d6e92bc10eced211a2122 |
View Raw JSON Data
{
"trx_id": "ebd9f2cbab55be5c4f4d6e92bc10eced211a2122",
"block": 4729295,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-09-06T09:12:24",
"op": [
"comment",
{
"parent_author": "iainc",
"parent_permlink": "re-happybeing-re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160906t075126699z",
"author": "happybeing",
"permlink": "re-iainc-re-happybeing-re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160906t091222861z",
"title": "",
"body": "And mine also from the SAFE forum :-) ...\n\nThanks for responding Chris. I didn't mean to suggest you were negative overall, but have pointed out specific instances where I believe you give your readers a misleading or factually incorrect picture. I think those points still stand (terminology excepted which you say has been updated - thanks). \n\nFor me it is not about negative or positive spin or attitude, but making statements that are consistent with the situation and the facts. \n\nFor example, you made some very strong statements, highly discouraging to any developers reading, about the difficulty of developing, and made no mention that these serious difficulties were being addressed as you published. I also explained to you that things - at this point in time - are not as difficult as you seem to believe them to be which is why I mentioned the already working dynamic web apps, written in JavaScript using the *existing* API, *as well as* the imminent improvements and extensions in this area. \n\nI am not a MaidSafe developer BTW, I'm one of those \"external developers\" you were thinking of as you wrote, albeit one who is willing to dig around in the early stages of a project. That's how you gain commercial advantage after all. \n\nYou have now explained how your personal experience has been factored into your opinion in the article, but that experience was not presented in the article which prevents the project from responding to or address those issues. \n\nRegarding the SAFE Ecosystem, which I pointed out is a major diferentiator of this project, you above take issue with one element that, with your current level of understanding, you deem impractical (pay once, store forever). We're not stupid here in this community, so we are aware that there are things about this project that appear implausible, or are hard to accept, and you are not the only person who wants to see this before believing it. It's not even close to the most contentious such issue debated here :slight_smile:\n\nI have some scepticism about this too, but I do also understand the basis for this claim and can see that it could well work. So it should not be dismissed either, and even if *you* choose to do so, you could still allude to an ecosystem of rewards that the project has designed to encourage adoption by stakeholders: users, resource and storage providers, app developers, and core developers. \n\nThe project is revolutionary, and it has so much to it that nobody can be expected to understand or believe it all until it is working. Me too :slight_smile: but I don't think that's a reason to dismiss that whole section especially if you are going to make comparisons with other projects. \n\nAs I said, it's up to you what you do with the feedback. I didn't assume you'd update your article, but I don't think your reasoning for what you wrote stands up and I think you do your readers a disservice in key aspects. Particularly the situation that exists for interested developers, and ignoring key features that differentiate this project.\n\n[Please be aware I'm a member of the community here, not part of MaidSafe and not a developer any more though I still tinker as mentioned. I'm a retired developer who has seen it and done it, and has dug deep into this project, and been continually impressed by it in all respects. This is why I've stuck around, and why I'll take the time to give people feedback when they request it. Of course, people don't always like my feedback or make immediate use of it, and that's perfectly fine. I gave it willingly and in good faith, so please don't take it personally, or assume that I'm expecting anything from you.]",
"json_metadata": "{\"tags\":[\"blockchain\"]}"
}
]
}| parent author | happybeing |
| parent permlink | re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z |
| author | iainc |
| permlink | re-happybeing-re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160906t075126699z |
| title | |
| body | And for the sake of keeping the discussion consistent, here is my answer from the SAFEnetwork forum: Hoping to help you understand my (outsider's) point of view by addressing the individual points you raise. - Terminology: thank you, corrected - Lack of dynamic data API: I do know that an API is in development and I mention right at the beginning of the article that a lot of good things are to be expected from the project in the near future. But for the sake of making projects comparable and understandable, I strictly write about things that exist here and now and that are accessible to a certain level, e.g. through a tutorial/getting started guide. The assumption that an outside developer will dig into RFCs and start implementing his software on an unfinished API is just not realistic. - Centralized Alpha: I clearly write that the Alpha release does store its data in a set of controlled nodes and that decentralized storage does exist, but that the two parts are not yet working together. I don't see how this can be perceived as negative, the project is in development, it's an Alpha, and that's just fine. - Testnet8: maidsafe.readme.io states "Users can’t run their own vault." I know that Testnet8 exists and tried to gain access to it, but was not able to do so within a reasonable amount of time. As a tech worker of almost 30 years I must assume that others will have a similar experience, hence the statement that only a small number of devs will manage to access it. I know that everything is out there and that everything that's out there can be made to work, but that's not what I would call accessible to the general public. Again: this is perfectly fine, I don't see why there is a need to suggest that everything is finished already. - MAID ownership and Safecoin roadmap. Here, I'm talking about some kind of economic transparency paper or another kind of summary that would allow investors to understand their investment in a simple way. There's a lot of info out there, I know, but people who are merely investing in these projects (whatever anybody might think of that) won't go scouring forums and asking questions in the long run. An ICO/crowdsale is some kind of pseudo-public listing and I hope that in the future, there will be more transparency in these processes, also to prevent the authorities from feeling compelled to enforce that transparency the hard way. As I mentioned: my doubts in this regard are very small in the case of MaidSafe, but still, a nice summary somewhere would be helpful. - Barriers of entry for devs: I know that these will be lowered soon. But again, right now, they are still high compared to the maybe 150 projects that I've worked with productively in the past 30 years. And again: I don't see why this should be negative, the SAFE network could be the future of the Internet, so it's probably worth investing a bit of time to get it right? - Incentives: In this article, I am referring to the Storj article where I discussed this kind of incentives (they are very similar in both networks). Pay once, store forever is not realistic because it's lopsided from an economic point of view: how can somebody pay once and somebody else (or the network) render a service forever? Storage providers do invest: time to get the software up and running and to keep it running and resources like bandwidth or electric power. Developer (or even user, producer, core maintainers) rewards are one of the fantastic advantages of this new kind of system that combines decentralized technology and micropayments. If we get this right, I am positive that it will literally change the world. However, to get it right, we also have to think about things that could possibly go wrong. One of the reasons why we started this article project is that I personally believe that decentralized trust technologies, combined with micro-reward systems, will drive the next big wave of technological change. I feel that we are at a similar moment in tech-time to the early years of the Internet and I made ample reference to this throughout my article, I even call MaidSafe "the next Internet" in the title. However, in the past 30 years in tech, I've also seen many things go horribly wrong, especially because we as technical people often fail to build reliable bridges to the social sphere. Pointing out the good things and those that still need improvement to make this workable for "the general public" is my way of laying maybe one single stone for this bridge. I'm sorry that my attempt at a differentiated view on the SAFE network project sounds negative to you, that was far from being the intention. |
| json metadata | {"tags":["blockchain"]} |
| Transaction Info | Block #4727680/Trx 5cf547b2a2e8d194535a4cc573280af5acc0cddc |
View Raw JSON Data
{
"trx_id": "5cf547b2a2e8d194535a4cc573280af5acc0cddc",
"block": 4727680,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-09-06T07:51:27",
"op": [
"comment",
{
"parent_author": "happybeing",
"parent_permlink": "re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z",
"author": "iainc",
"permlink": "re-happybeing-re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160906t075126699z",
"title": "",
"body": "And for the sake of keeping the discussion consistent, here is my answer from the SAFEnetwork forum:\n\nHoping to help you understand my (outsider's) point of view by addressing the individual points you raise.\n\n- Terminology: thank you, corrected\n- Lack of dynamic data API: I do know that an API is in development and I mention right at the beginning of the article that a lot of good things are to be expected from the project in the near future. But for the sake of making projects comparable and understandable, I strictly write about things that exist here and now and that are accessible to a certain level, e.g. through a tutorial/getting started guide. The assumption that an outside developer will dig into RFCs and start implementing his software on an unfinished API is just not realistic. \n- Centralized Alpha: I clearly write that the Alpha release does store its data in a set of controlled nodes and that decentralized storage does exist, but that the two parts are not yet working together. I don't see how this can be perceived as negative, the project is in development, it's an Alpha, and that's just fine.\n- Testnet8: maidsafe.readme.io states \"Users can’t run their own vault.\" I know that Testnet8 exists and tried to gain access to it, but was not able to do so within a reasonable amount of time. As a tech worker of almost 30 years I must assume that others will have a similar experience, hence the statement that only a small number of devs will manage to access it. I know that everything is out there and that everything that's out there can be made to work, but that's not what I would call accessible to the general public. Again: this is perfectly fine, I don't see why there is a need to suggest that everything is finished already.\n- MAID ownership and Safecoin roadmap. Here, I'm talking about some kind of economic transparency paper or another kind of summary that would allow investors to understand their investment in a simple way. There's a lot of info out there, I know, but people who are merely investing in these projects (whatever anybody might think of that) won't go scouring forums and asking questions in the long run. An ICO/crowdsale is some kind of pseudo-public listing and I hope that in the future, there will be more transparency in these processes, also to prevent the authorities from feeling compelled to enforce that transparency the hard way. As I mentioned: my doubts in this regard are very small in the case of MaidSafe, but still, a nice summary somewhere would be helpful. \n- Barriers of entry for devs: I know that these will be lowered soon. But again, right now, they are still high compared to the maybe 150 projects that I've worked with productively in the past 30 years. And again: I don't see why this should be negative, the SAFE network could be the future of the Internet, so it's probably worth investing a bit of time to get it right?\n- Incentives: In this article, I am referring to the Storj article where I discussed this kind of incentives (they are very similar in both networks). Pay once, store forever is not realistic because it's lopsided from an economic point of view: how can somebody pay once and somebody else (or the network) render a service forever? Storage providers do invest: time to get the software up and running and to keep it running and resources like bandwidth or electric power. Developer (or even user, producer, core maintainers) rewards are one of the fantastic advantages of this new kind of system that combines decentralized technology and micropayments. If we get this right, I am positive that it will literally change the world. However, to get it right, we also have to think about things that could possibly go wrong. \n\nOne of the reasons why we started this article project is that I personally believe that decentralized trust technologies, combined with micro-reward systems, will drive the next big wave of technological change. I feel that we are at a similar moment in tech-time to the early years of the Internet and I made ample reference to this throughout my article, I even call MaidSafe \"the next Internet\" in the title. However, in the past 30 years in tech, I've also seen many things go horribly wrong, especially because we as technical people often fail to build reliable bridges to the social sphere. Pointing out the good things and those that still need improvement to make this workable for \"the general public\" is my way of laying maybe one single stone for this bridge. I'm sorry that my attempt at a differentiated view on the SAFE network project sounds negative to you, that was far from being the intention.",
"json_metadata": "{\"tags\":[\"blockchain\"]}"
}
]
}| voter | solar |
| author | happybeing |
| permlink | re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4724147/Trx a82c324125ce4d4a1e71f42004abc5bcafddb96d |
View Raw JSON Data
{
"trx_id": "a82c324125ce4d4a1e71f42004abc5bcafddb96d",
"block": 4724147,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-09-06T04:54:27",
"op": [
"vote",
{
"voter": "solar",
"author": "happybeing",
"permlink": "re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z",
"weight": 10000
}
]
}| voter | philosopherrex |
| author | happybeing |
| permlink | re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4721022/Trx b0f6dd05dcc41716c04e58c97e8be7c7cb723ba1 |
View Raw JSON Data
{
"trx_id": "b0f6dd05dcc41716c04e58c97e8be7c7cb723ba1",
"block": 4721022,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-09-06T02:17:57",
"op": [
"vote",
{
"voter": "philosopherrex",
"author": "happybeing",
"permlink": "re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z",
"weight": 10000
}
]
}| voter | john-ferguson |
| author | happybeing |
| permlink | re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4719358/Trx daa7f16a6d9d02c5dc06192730ebb77a37d10832 |
View Raw JSON Data
{
"trx_id": "daa7f16a6d9d02c5dc06192730ebb77a37d10832",
"block": 4719358,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-09-06T00:54:42",
"op": [
"vote",
{
"voter": "john-ferguson",
"author": "happybeing",
"permlink": "re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z",
"weight": 10000
}
]
}| parent author | iainc |
| parent permlink | maidsafe-review-the-next-internet-will-be-ours |
| author | happybeing |
| permlink | re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z |
| title | |
| body | Cross posted as an alternative to the OP being updated, here is *my* feedback in response to the author's invitation to members of the SAFEnetwork forum... A very decent article, some suggestions for revision... Terminology: Not blocks, but chunks Not SAFE coin, but Safecoin Misleading: > Unfortunately, the lack of an API for dynamic data or calculations makes creating an interactive service on the SAFE network mind-bendingly difficult. [er, no, not at all!!! ] Building such a service involves the creation of an additional "service" protocol on top the existing protocol.[Nope] If you want do dig deeper into this, we recommend studying the progress of Project Decorum.[Well, not the best place to look, better to look at the proposed, close to implementation APIs] > An alternative to the native approach of solving the dynamic data problem would be to introduce a centralized instance, a regular server, for the management of the dynamic aspects of a service. [Definitely NOT. A terrible idea for security, and completely unnecessary] With this approach, we would be forcing an architecture similar to TOR, partially defying the purpose of the network's architecture [exactly]. It is not entirely unlikely that such hybrid approaches, even the creation of TOR-style exit nodes could become necessary in the early stages of network establishment.[wrong] There is already an API for dynamic data although not final or implemented, but being finalised and implemented right now. To see this and other areas that are imminent I suggest you dig into the RFCs on github. The RFCs on Immutable Data, Appendable Data and particularly Structured Data are what you need to look at, and use to revise the above which is incorrect and very misleading. Essentially, dynamic data is already possible to an extent (see my porting of RS.js apps noted shortly) and very much more powerful and part of the public alpha shortly. Also, your description of the alpha as centralised is misleading, because it is likely to read as if it does not yet involve any decentralised technology. You are technically correct in the sense that MaidSafe control the decentralised nodes that deliver it. Your description of the Testnet as being about storage suggests that the Alpha doesn't cover storage, which of course it does. Both do. What is different is that in Testnet8 end users can *contribute* storage (i.e. run vaults), whereas in the Alpha users cannot do this. Also, like the Alpha, Testnet 8 is also open to the general public, not just selected developers as you've incorrectly stated. The difference is that Testnet 8 is deliberately less stable due to testing, and so less suitable for developers or users who need something more stable to play with - for them, the Alpha network is provided. > we'd certainly wish to know a bit more about the future of the SAFE coin, the project owner's holdings and the use of the 24M coins still in the project's possession. This is all public knowledge. What you think you don't know, please ask and someone will answer or point you to the relevant topic. > We are uncertain whether the elimination of this slight nuisance really warrants the effort of a custom browser implementation and all the obvious problems that come with such a project. The SAFE Beaker Browser is being created primarily to ensure that the security of users is not compromised, rather than to make usage more convenient. SAFE Beaker Browser will become the preferred method of accessing the SAFE Web because a legacy browser that simultaneously accesses the CLEARNET, or from which cookies and other goodies are accessible, opens up a vast array of potential security vulnerabilities. By default, the SAFE browser will not allow access to anything outside SAFEnetwork, and since SAFEnetwork websites will be far far more secure from being hacked, the level of security and privacy afforded by SAFE Beaker Browser can be unprecedented, which is of course one of the primary goals of SAFEnetwork. > Technologically, the barrier of entry to create interactive applications on the SAFE network is still very high... While technically you can argue this at this precise moment, the point is far too strongly made IMO, and so does not justify the points made in the remainder of your paragraph. This is because all this is changing very rapidly. I'm just learning JavaScript, and yet, currently have three applications running in local tests that are simple ports of dynamic web applications originally written to use remoteStorage.js. I can't show these yet because the alpha network imposed a couple of security restrictions that are over zealous, and exposed a vulnerability in remoteStorage.js which that project have been working to fix over the weekend. So very soon I'll be able to show these three apps, each of which was ported in minutes, running on SAFEnetwork. :slight_smile: Not sooooooo hard. And all that without the dynamic data API (Appendable Data and Structured Data) that is in the wings right now. And I'm not a decent programmer, I'm an ex professional who is now learning JavaScript. But I know there are several very decent programmers working on far more impressive apps right now too :slight_smile: So I think you could be a bit less negative about SAFEnetwork as an application platform, if not now, then check back in a month to see what a JavaScript novice like me can get going. ### The SAFE Ecosystem You have not mentioned how various incentives for different stakeholders make adoption by users and providers very different to past projects, or those you've made comparisons with. I think this is an important omission. Please consider the effect of these on adoption: - the attractiveness of a *pay once stored forever* secure private cloud compared to existing offerings, especially when the cost will be based on spare resources, rather than enormous costly data centres with enormous energy bills - how storage providers are rewarded, how easy it is for any user to take part in both sides of the equation, and how little they need to invest (nothing) to earn Safecoin for sharing their unused, mostly already paid for, resources - how app developers are rewarded based on the use and popularity of their applications - how an App scales automatically, regardless of how many users it gains, without the developer having to rent a single server, or sell their souls to fund the growth of data centres serving it - how the network automatically generates the funds to pay developers who maintain the core - proposals to test mechanisms for rewarding the producers of popular content published on the network (i.e. *pay the producer* or PtP). Imagine the impact of this on the publishing world, or rewarding individual creativity etc. Also, consider SAFEnetwork as an internet with own built in, highly scalable, micropayment ready, totally anonymous currency, as a platform for free exchange, trading, services etc There's a lot to it! :slight_smile: You've written a decent article, better than many first attempts, but it takes some time to appreciate this project so I hope you'll be inspired to look in more depth and maybe explore the wider implications. Thanks for sharing it here and inviting comment. I hope some of this is useful, and all taken in the positive feedback way I am not so good at conveying! :slight_smile: |
| json metadata | {"tags":["blockchain"]} |
| Transaction Info | Block #4713349/Trx 05bf5d006aba09b4922c789ebfd355773dad18ad |
View Raw JSON Data
{
"trx_id": "05bf5d006aba09b4922c789ebfd355773dad18ad",
"block": 4713349,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-09-05T19:53:57",
"op": [
"comment",
{
"parent_author": "iainc",
"parent_permlink": "maidsafe-review-the-next-internet-will-be-ours",
"author": "happybeing",
"permlink": "re-iainc-maidsafe-review-the-next-internet-will-be-ours-20160905t195355998z",
"title": "",
"body": "Cross posted as an alternative to the OP being updated, here is *my* feedback in response to the author's invitation to members of the SAFEnetwork forum...\n\nA very decent article, some suggestions for revision... \n\nTerminology:\n\nNot blocks, but chunks\nNot SAFE coin, but Safecoin\n\nMisleading:\n\n> Unfortunately, the lack of an API for dynamic data or calculations makes creating an interactive service on the SAFE network mind-bendingly difficult. [er, no, not at all!!! ] Building such a service involves the creation of an additional \"service\" protocol on top the existing protocol.[Nope] If you want do dig deeper into this, we recommend studying the progress of Project Decorum.[Well, not the best place to look, better to look at the proposed, close to implementation APIs]\n\n> An alternative to the native approach of solving the dynamic data problem would be to introduce a centralized instance, a regular server, for the management of the dynamic aspects of a service. [Definitely NOT. A terrible idea for security, and completely unnecessary] With this approach, we would be forcing an architecture similar to TOR, partially defying the purpose of the network's architecture [exactly]. It is not entirely unlikely that such hybrid approaches, even the creation of TOR-style exit nodes could become necessary in the early stages of network establishment.[wrong]\n\nThere is already an API for dynamic data although not final or implemented, but being finalised and implemented right now. To see this and other areas that are imminent I suggest you dig into the RFCs on github. The RFCs on Immutable Data, Appendable Data and particularly Structured Data are what you need to look at, and use to revise the above which is incorrect and very misleading. \n\nEssentially, dynamic data is already possible to an extent (see my porting of RS.js apps noted shortly) and very much more powerful and part of the public alpha shortly. \n\nAlso, your description of the alpha as centralised is misleading, because it is likely to read as if it does not yet involve any decentralised technology. You are technically correct in the sense that MaidSafe control the decentralised nodes that deliver it. \n\nYour description of the Testnet as being about storage suggests that the Alpha doesn't cover storage, which of course it does. Both do. What is different is that in Testnet8 end users can *contribute* storage (i.e. run vaults), whereas in the Alpha users cannot do this. \n\nAlso, like the Alpha, Testnet 8 is also open to the general public, not just selected developers as you've incorrectly stated. The difference is that Testnet 8 is deliberately less stable due to testing, and so less suitable for developers or users who need something more stable to play with - for them, the Alpha network is provided. \n\n> we'd certainly wish to know a bit more about the future of the SAFE coin, the project owner's holdings and the use of the 24M coins still in the project's possession.\n\nThis is all public knowledge. What you think you don't know, please ask and someone will answer or point you to the relevant topic. \n\n> We are uncertain whether the elimination of this slight nuisance really warrants the effort of a custom browser implementation and all the obvious problems that come with such a project.\n\nThe SAFE Beaker Browser is being created primarily to ensure that the security of users is not compromised, rather than to make usage more convenient. SAFE Beaker Browser will become the preferred method of accessing the SAFE Web because a legacy browser that simultaneously accesses the CLEARNET, or from which cookies and other goodies are accessible, opens up a vast array of potential security vulnerabilities. \n\nBy default, the SAFE browser will not allow access to anything outside SAFEnetwork, and since SAFEnetwork websites will be far far more secure from being hacked, the level of security and privacy afforded by SAFE Beaker Browser can be unprecedented, which is of course one of the primary goals of SAFEnetwork. \n\n> Technologically, the barrier of entry to create interactive applications on the SAFE network is still very high...\n\nWhile technically you can argue this at this precise moment, the point is far too strongly made IMO, and so does not justify the points made in the remainder of your paragraph. \n\nThis is because all this is changing very rapidly. I'm just learning JavaScript, and yet, currently have three applications running in local tests that are simple ports of dynamic web applications originally written to use remoteStorage.js. \n\nI can't show these yet because the alpha network imposed a couple of security restrictions that are over zealous, and exposed a vulnerability in remoteStorage.js which that project have been working to fix over the weekend. So very soon I'll be able to show these three apps, each of which was ported in minutes, running on SAFEnetwork. :slight_smile: Not sooooooo hard. And all that without the dynamic data API (Appendable Data and Structured Data) that is in the wings right now. And I'm not a decent programmer, I'm an ex professional who is now learning JavaScript. But I know there are several very decent programmers working on far more impressive apps right now too :slight_smile: \n\nSo I think you could be a bit less negative about SAFEnetwork as an application platform, if not now, then check back in a month to see what a JavaScript novice like me can get going. \n\n### The SAFE Ecosystem \n\nYou have not mentioned how various incentives for different stakeholders make adoption by users and providers very different to past projects, or those you've made comparisons with. I think this is an important omission. Please consider the effect of these on adoption:\n\n- the attractiveness of a *pay once stored forever* secure private cloud compared to existing offerings, especially when the cost will be based on spare resources, rather than enormous costly data centres with enormous energy bills\n- how storage providers are rewarded, how easy it is for any user to take part in both sides of the equation, and how little they need to invest (nothing) to earn Safecoin for sharing their unused, mostly already paid for, resources\n- how app developers are rewarded based on the use and popularity of their applications\n- how an App scales automatically, regardless of how many users it gains, without the developer having to rent a single server, or sell their souls to fund the growth of data centres serving it\n- how the network automatically generates the funds to pay developers who maintain the core\n- proposals to test mechanisms for rewarding the producers of popular content published on the network (i.e. *pay the producer* or PtP). Imagine the impact of this on the publishing world, or rewarding individual creativity etc. \n\nAlso, consider SAFEnetwork as an internet with own built in, highly scalable, micropayment ready, totally anonymous currency, as a platform for free exchange, trading, services etc\n\nThere's a lot to it! :slight_smile: \n\nYou've written a decent article, better than many first attempts, but it takes some time to appreciate this project so I hope you'll be inspired to look in more depth and maybe explore the wider implications. \n\nThanks for sharing it here and inviting comment. I hope some of this is useful, and all taken in the positive feedback way I am not so good at conveying! :slight_smile:",
"json_metadata": "{\"tags\":[\"blockchain\"]}"
}
]
}| voter | happybeing |
| author | mranderson |
| permlink | steemaway-vote-and-receive-original-fine-art-worth-thousands-of-dollars-delivered-free-to-your-door |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3707626/Trx 71bba7f0d61863ac82df75cfbf4625817dce6c0b |
View Raw JSON Data
{
"trx_id": "71bba7f0d61863ac82df75cfbf4625817dce6c0b",
"block": 3707626,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-01T17:02:33",
"op": [
"vote",
{
"voter": "happybeing",
"author": "mranderson",
"permlink": "steemaway-vote-and-receive-original-fine-art-worth-thousands-of-dollars-delivered-free-to-your-door",
"weight": 10000
}
]
}| voter | happybeing |
| author | remington-art |
| permlink | painter-grandfather-steemer-first-professional-artist-on-steemit |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3671256/Trx fc1da112b1fc2e5ab7efce1770e850097cf9ffc2 |
View Raw JSON Data
{
"trx_id": "fc1da112b1fc2e5ab7efce1770e850097cf9ffc2",
"block": 3671256,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-31T10:35:12",
"op": [
"vote",
{
"voter": "happybeing",
"author": "remington-art",
"permlink": "painter-grandfather-steemer-first-professional-artist-on-steemit",
"weight": 10000
}
]
}happybeingupvoted (100.00%) @mranderson / steemaway-win-share-the-love-and-love-to-share-everyone-wins
happybeingupvoted (100.00%) @mranderson / steemaway-win-share-the-love-and-love-to-share-everyone-wins
| voter | happybeing |
| author | mranderson |
| permlink | steemaway-win-share-the-love-and-love-to-share-everyone-wins |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3671151/Trx d2611e597b456940aaa1080e63cee3cc30fe7c89 |
View Raw JSON Data
{
"trx_id": "d2611e597b456940aaa1080e63cee3cc30fe7c89",
"block": 3671151,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-31T10:29:57",
"op": [
"vote",
{
"voter": "happybeing",
"author": "mranderson",
"permlink": "steemaway-win-share-the-love-and-love-to-share-everyone-wins",
"weight": 10000
}
]
}steemcreated a new account: @happybeing
steemcreated a new account: @happybeing
| fee | 10.000 STEEM |
| creator | steem |
| new account name | happybeing |
| owner | {"weight_threshold":1,"account_auths":[],"key_auths":[["STM7gszigy2i4DgwUKx2Ms1Q2sZMV6N8WrqfXCPZfDwixMZDKWaAy",1]]} |
| active | {"weight_threshold":1,"account_auths":[],"key_auths":[["STM6N4XQz9fT3qcemvEdZWvZNBpFkoYggZqSsKALmnNPWU43YG6Cu",1]]} |
| posting | {"weight_threshold":1,"account_auths":[],"key_auths":[["STM7ANiBSpBBHFnDzwvM1Fk9jNEyg1f5cc8CE1LqUZHTFaKEfRkJs",1]]} |
| memo key | STM8BJAA6pL3ouJhK3cUXAd4C6YzePnPMGYwtyRfvpD5j8HYeoYiN |
| json metadata | |
| Transaction Info | Block #1983548/Trx 25bcb03e9eda5fb5579752efda179de5ca44914a |
View Raw JSON Data
{
"trx_id": "25bcb03e9eda5fb5579752efda179de5ca44914a",
"block": 1983548,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-06-02T10:15:06",
"op": [
"account_create",
{
"fee": "10.000 STEEM",
"creator": "steem",
"new_account_name": "happybeing",
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7gszigy2i4DgwUKx2Ms1Q2sZMV6N8WrqfXCPZfDwixMZDKWaAy",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM6N4XQz9fT3qcemvEdZWvZNBpFkoYggZqSsKALmnNPWU43YG6Cu",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7ANiBSpBBHFnDzwvM1Fk9jNEyg1f5cc8CE1LqUZHTFaKEfRkJs",
1
]
]
},
"memo_key": "STM8BJAA6pL3ouJhK3cUXAd4C6YzePnPMGYwtyRfvpD5j8HYeoYiN",
"json_metadata": ""
}
]
}Manabar
Voting Power100.00%
Downvote Power100.00%
Resource Credits100.00%
Reputation Progress60.24%
{
"voting_manabar": {
"current_mana": 9949,
"last_update_time": 1470070953
},
"downvote_manabar": {
"current_mana": 0,
"last_update_time": 1464862506
},
"rc_account": {
"account": "happybeing",
"rc_manabar": {
"current_mana": "78647690225",
"last_update_time": 1537887600
},
"max_rc_creation_adjustment": {
"amount": "2020748973",
"precision": 6,
"nai": "@@000000037"
},
"max_rc": "78647690225"
}
}Account Metadata
| POSTING JSON METADATA | |
| None | |
| JSON METADATA | |
| None |
{
"posting_json_metadata": {},
"json_metadata": {}
}Auth Keys
Owner
Single Signature
Public Keys
STM7gszigy2i4DgwUKx2Ms1Q2sZMV6N8WrqfXCPZfDwixMZDKWaAy1/1
Active
Single Signature
Public Keys
STM6N4XQz9fT3qcemvEdZWvZNBpFkoYggZqSsKALmnNPWU43YG6Cu1/1
Posting
Single Signature
Public Keys
STM7ANiBSpBBHFnDzwvM1Fk9jNEyg1f5cc8CE1LqUZHTFaKEfRkJs1/1
Memo
STM8BJAA6pL3ouJhK3cUXAd4C6YzePnPMGYwtyRfvpD5j8HYeoYiN
{
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7gszigy2i4DgwUKx2Ms1Q2sZMV6N8WrqfXCPZfDwixMZDKWaAy",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM6N4XQz9fT3qcemvEdZWvZNBpFkoYggZqSsKALmnNPWU43YG6Cu",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7ANiBSpBBHFnDzwvM1Fk9jNEyg1f5cc8CE1LqUZHTFaKEfRkJs",
1
]
]
},
"memo": "STM8BJAA6pL3ouJhK3cUXAd4C6YzePnPMGYwtyRfvpD5j8HYeoYiN"
}Witness Votes
0 / 30
No active witness votes.
[]