VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS79.29%
Net Worth
0.258USD
STEEM
0.000STEEM
SBD
0.454SBD
Effective Power
5.001SP
├── Own SP
0.631SP
└── Incoming DelegationsDeleg
+4.370SP
Detailed Balance
| STEEM | ||
| balance | 0.000STEEM | STEEM |
| market_balance | 0.000STEEM | STEEM |
| savings_balance | 0.000STEEM | STEEM |
| reward_steem_balance | 0.000STEEM | STEEM |
| STEEM POWER | ||
| Own SP | 0.631SP | SP |
| Delegated Out | 0.000SP | SP |
| Delegation In | 4.370SP | SP |
| Effective Power | 5.001SP | SP |
| Reward SP (pending) | 0.218SP | SP |
| SBD | ||
| sbd_balance | 0.000SBD | SBD |
| sbd_conversions | 0.000SBD | SBD |
| sbd_market_balance | 0.000SBD | SBD |
| savings_sbd_balance | 0.000SBD | SBD |
| reward_sbd_balance | 0.454SBD | SBD |
{
"balance": "0.000 STEEM",
"savings_balance": "0.000 STEEM",
"reward_steem_balance": "0.000 STEEM",
"vesting_shares": "1027.996263 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "7115.663543 VESTS",
"sbd_balance": "0.000 SBD",
"savings_sbd_balance": "0.000 SBD",
"reward_sbd_balance": "0.454 SBD",
"conversions": []
}Account Info
| name | rickmanelius |
| id | 427367 |
| rank | 1,427,424 |
| reputation | 4402110074 |
| created | 2017-10-27T13:20:03 |
| recovery_account | steem |
| proxy | None |
| post_count | 4 |
| comment_count | 0 |
| lifetime_vote_count | 0 |
| witnesses_voted_for | 0 |
| last_post | 2018-05-03T03:00:33 |
| last_root_post | 2018-05-03T03:00:33 |
| last_vote_time | 2017-12-13T03:09:57 |
| proxied_vsf_votes | 0, 0, 0, 0 |
| can_vote | 1 |
| voting_power | 0 |
| delayed_votes | 0 |
| balance | 0.000 STEEM |
| savings_balance | 0.000 STEEM |
| sbd_balance | 0.000 SBD |
| savings_sbd_balance | 0.000 SBD |
| vesting_shares | 1027.996263 VESTS |
| delegated_vesting_shares | 0.000000 VESTS |
| received_vesting_shares | 7115.663543 VESTS |
| reward_vesting_balance | 447.031559 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 | 2017-12-11T02:16:27 |
| 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": 427367,
"name": "rickmanelius",
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM8Bf9vbZTzd59ciEKuFKFK6ucjPSuGB7v5tMWTMQJa9ncZfybGo",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5YPa4PwggzY1Yj1FDx2CSdf3q9tbJrQxDwh4AvpQiVmKoq2RHs",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5wcBspXgYSqdaNwausZUP4Npiq8EdJmgCWxcnFjuqKGtxW3bC7",
1
]
]
},
"memo_key": "STM6G42mm22WrqWkAWaevdjDsYK8KP3AvAhXAj5B2yqZMpviPAAnQ",
"json_metadata": "{\"profile\":{\"profile_image\":\"https://rickmanelius.com/sites/default/files/IMCE/theme/about3.jpg\",\"name\":\"Rick Manelius\",\"location\":\"Colorado\",\"website\":\"https://rickmanelius.com/\"}}",
"posting_json_metadata": "{\"profile\":{\"profile_image\":\"https://rickmanelius.com/sites/default/files/IMCE/theme/about3.jpg\",\"name\":\"Rick Manelius\",\"location\":\"Colorado\",\"website\":\"https://rickmanelius.com/\"}}",
"proxy": "",
"last_owner_update": "1970-01-01T00:00:00",
"last_account_update": "2017-12-11T02:16:27",
"created": "2017-10-27T13:20:03",
"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": 4,
"can_vote": true,
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779082962
},
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779082962
},
"voting_power": 0,
"balance": "0.000 STEEM",
"savings_balance": "0.000 STEEM",
"sbd_balance": "0.000 SBD",
"sbd_seconds": "0",
"sbd_seconds_last_update": "1970-01-01T00:00:00",
"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.454 SBD",
"reward_steem_balance": "0.000 STEEM",
"reward_vesting_balance": "447.031559 VESTS",
"reward_vesting_steem": "0.218 STEEM",
"vesting_shares": "1027.996263 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "7115.663543 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": 436,
"proxied_vsf_votes": [
0,
0,
0,
0
],
"witnesses_voted_for": 0,
"last_post": "2018-05-03T03:00:33",
"last_root_post": "2018-05-03T03:00:33",
"last_vote_time": "2017-12-13T03:09:57",
"post_bandwidth": 0,
"pending_claimed_accounts": 0,
"vesting_balance": "0.000 STEEM",
"reputation": "4402110074",
"transfer_history": [],
"market_history": [],
"post_history": [],
"vote_history": [],
"other_history": [],
"witness_votes": [],
"tags_usage": [],
"guest_bloggers": [],
"rank": 1427424
}Withdraw Routes
| Incoming | Outgoing |
|---|---|
Empty | Empty |
{
"incoming": [],
"outgoing": []
}From Date
To Date
steemdelegated 4.370 SP to @rickmanelius2026/05/18 05:42:42
steemdelegated 4.370 SP to @rickmanelius
2026/05/18 05:42:42
| delegator | steem |
| delegatee | rickmanelius |
| vesting shares | 7115.663543 VESTS |
| Transaction Info | Block #106149969/Trx 8a0a4fcace3724b962ab144998fc4d7d1cebdc84 |
View Raw JSON Data
{
"trx_id": "8a0a4fcace3724b962ab144998fc4d7d1cebdc84",
"block": 106149969,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-05-18T05:42:42",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "rickmanelius",
"vesting_shares": "7115.663543 VESTS"
}
]
}steemdelegated 2.704 SP to @rickmanelius2026/05/13 02:01:06
steemdelegated 2.704 SP to @rickmanelius
2026/05/13 02:01:06
| delegator | steem |
| delegatee | rickmanelius |
| vesting shares | 4403.453138 VESTS |
| Transaction Info | Block #106002264/Trx 2f7bc287d58b47093174eceb6bc52543e5b8816a |
View Raw JSON Data
{
"trx_id": "2f7bc287d58b47093174eceb6bc52543e5b8816a",
"block": 106002264,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-05-13T02:01:06",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "rickmanelius",
"vesting_shares": "4403.453138 VESTS"
}
]
}steemdelegated 4.377 SP to @rickmanelius2026/04/26 04:55:18
steemdelegated 4.377 SP to @rickmanelius
2026/04/26 04:55:18
| delegator | steem |
| delegatee | rickmanelius |
| vesting shares | 7128.179299 VESTS |
| Transaction Info | Block #105517469/Trx 3e50eec03556657a7088fe9e7f961928ef12d8fd |
View Raw JSON Data
{
"trx_id": "3e50eec03556657a7088fe9e7f961928ef12d8fd",
"block": 105517469,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-04-26T04:55:18",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "rickmanelius",
"vesting_shares": "7128.179299 VESTS"
}
]
}steemdelegated 2.730 SP to @rickmanelius2026/01/23 22:28:54
steemdelegated 2.730 SP to @rickmanelius
2026/01/23 22:28:54
| delegator | steem |
| delegatee | rickmanelius |
| vesting shares | 4444.999957 VESTS |
| Transaction Info | Block #102869399/Trx 76798297d8a696f3afea5282e5b0ec0bab7cf19d |
View Raw JSON Data
{
"trx_id": "76798297d8a696f3afea5282e5b0ec0bab7cf19d",
"block": 102869399,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-01-23T22:28:54",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "rickmanelius",
"vesting_shares": "4444.999957 VESTS"
}
]
}steemdelegated 2.831 SP to @rickmanelius2024/12/17 17:39:33
steemdelegated 2.831 SP to @rickmanelius
2024/12/17 17:39:33
| delegator | steem |
| delegatee | rickmanelius |
| vesting shares | 4609.219154 VESTS |
| Transaction Info | Block #91315625/Trx b61e6e1044e13d96f296d16414feabca6a7e87ae |
View Raw JSON Data
{
"trx_id": "b61e6e1044e13d96f296d16414feabca6a7e87ae",
"block": 91315625,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2024-12-17T17:39:33",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "rickmanelius",
"vesting_shares": "4609.219154 VESTS"
}
]
}steemdelegated 2.934 SP to @rickmanelius2023/11/14 09:20:45
steemdelegated 2.934 SP to @rickmanelius
2023/11/14 09:20:45
| delegator | steem |
| delegatee | rickmanelius |
| vesting shares | 4778.352686 VESTS |
| Transaction Info | Block #79869774/Trx eb032ad30754f480945f7aae693f565949d84baf |
View Raw JSON Data
{
"trx_id": "eb032ad30754f480945f7aae693f565949d84baf",
"block": 79869774,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2023-11-14T09:20:45",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "rickmanelius",
"vesting_shares": "4778.352686 VESTS"
}
]
}steemdelegated 4.738 SP to @rickmanelius2023/09/22 09:42:33
steemdelegated 4.738 SP to @rickmanelius
2023/09/22 09:42:33
| delegator | steem |
| delegatee | rickmanelius |
| vesting shares | 7715.261472 VESTS |
| Transaction Info | Block #78362048/Trx 4aa433df3f61f70662437a67dd0142d50e7068b4 |
View Raw JSON Data
{
"trx_id": "4aa433df3f61f70662437a67dd0142d50e7068b4",
"block": 78362048,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2023-09-22T09:42:33",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "rickmanelius",
"vesting_shares": "7715.261472 VESTS"
}
]
}steemdelegated 4.874 SP to @rickmanelius2022/11/03 17:15:30
steemdelegated 4.874 SP to @rickmanelius
2022/11/03 17:15:30
| delegator | steem |
| delegatee | rickmanelius |
| vesting shares | 7937.312910 VESTS |
| Transaction Info | Block #69119895/Trx 6a505401779cdab726e1f410bde1abd81d155fcd |
View Raw JSON Data
{
"trx_id": "6a505401779cdab726e1f410bde1abd81d155fcd",
"block": 69119895,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2022-11-03T17:15:30",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "rickmanelius",
"vesting_shares": "7937.312910 VESTS"
}
]
}steemdelegated 5.009 SP to @rickmanelius2022/01/17 22:30:48
steemdelegated 5.009 SP to @rickmanelius
2022/01/17 22:30:48
| delegator | steem |
| delegatee | rickmanelius |
| vesting shares | 8157.420511 VESTS |
| Transaction Info | Block #60823211/Trx 5774461c93935457722634c7bf34da11f2367a38 |
View Raw JSON Data
{
"trx_id": "5774461c93935457722634c7bf34da11f2367a38",
"block": 60823211,
"trx_in_block": 18,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2022-01-17T22:30:48",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "rickmanelius",
"vesting_shares": "8157.420511 VESTS"
}
]
}steemdelegated 5.123 SP to @rickmanelius2021/06/14 05:43:15
steemdelegated 5.123 SP to @rickmanelius
2021/06/14 05:43:15
| delegator | steem |
| delegatee | rickmanelius |
| vesting shares | 8341.614799 VESTS |
| Transaction Info | Block #54613568/Trx b0798d0e19f8a799dcddc892577e55c3c4ff36f2 |
View Raw JSON Data
{
"trx_id": "b0798d0e19f8a799dcddc892577e55c3c4ff36f2",
"block": 54613568,
"trx_in_block": 9,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2021-06-14T05:43:15",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "rickmanelius",
"vesting_shares": "8341.614799 VESTS"
}
]
}steemdelegated 5.238 SP to @rickmanelius2020/12/11 15:56:00
steemdelegated 5.238 SP to @rickmanelius
2020/12/11 15:56:00
| delegator | steem |
| delegatee | rickmanelius |
| vesting shares | 8529.036773 VESTS |
| Transaction Info | Block #49360848/Trx 6e628d3e690834e73cddb6574aeeaf563df2a778 |
View Raw JSON Data
{
"trx_id": "6e628d3e690834e73cddb6574aeeaf563df2a778",
"block": 49360848,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-12-11T15:56:00",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "rickmanelius",
"vesting_shares": "8529.036773 VESTS"
}
]
}steemdelegated 1.174 SP to @rickmanelius2020/12/06 09:31:57
steemdelegated 1.174 SP to @rickmanelius
2020/12/06 09:31:57
| delegator | steem |
| delegatee | rickmanelius |
| vesting shares | 1912.543513 VESTS |
| Transaction Info | Block #49212377/Trx 19cae4f3e96ae217c757a5596d3ade7215aa21ef |
View Raw JSON Data
{
"trx_id": "19cae4f3e96ae217c757a5596d3ade7215aa21ef",
"block": 49212377,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-12-06T09:31:57",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "rickmanelius",
"vesting_shares": "1912.543513 VESTS"
}
]
}steemdelegated 5.242 SP to @rickmanelius2020/12/05 19:34:03
steemdelegated 5.242 SP to @rickmanelius
2020/12/05 19:34:03
| delegator | steem |
| delegatee | rickmanelius |
| vesting shares | 8535.244627 VESTS |
| Transaction Info | Block #49195936/Trx 35ab24f1631020215e4e9fd7f5249d4d9c477af8 |
View Raw JSON Data
{
"trx_id": "35ab24f1631020215e4e9fd7f5249d4d9c477af8",
"block": 49195936,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-12-05T19:34:03",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "rickmanelius",
"vesting_shares": "8535.244627 VESTS"
}
]
}steemdelegated 1.179 SP to @rickmanelius2020/11/03 01:40:21
steemdelegated 1.179 SP to @rickmanelius
2020/11/03 01:40:21
| delegator | steem |
| delegatee | rickmanelius |
| vesting shares | 1920.017158 VESTS |
| Transaction Info | Block #48269615/Trx ed7b107435dac1391a9894c7038cafebb23187d2 |
View Raw JSON Data
{
"trx_id": "ed7b107435dac1391a9894c7038cafebb23187d2",
"block": 48269615,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-11-03T01:40:21",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "rickmanelius",
"vesting_shares": "1920.017158 VESTS"
}
]
}steemdelegated 5.366 SP to @rickmanelius2020/05/09 10:34:33
steemdelegated 5.366 SP to @rickmanelius
2020/05/09 10:34:33
| delegator | steem |
| delegatee | rickmanelius |
| vesting shares | 8738.049986 VESTS |
| Transaction Info | Block #43222698/Trx be7b3cee3d78d283e4a87431ae92ffd8c74ba6d1 |
View Raw JSON Data
{
"trx_id": "be7b3cee3d78d283e4a87431ae92ffd8c74ba6d1",
"block": 43222698,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-05-09T10:34:33",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "rickmanelius",
"vesting_shares": "8738.049986 VESTS"
}
]
}steemdelegated 1.200 SP to @rickmanelius2020/05/08 14:54:15
steemdelegated 1.200 SP to @rickmanelius
2020/05/08 14:54:15
| delegator | steem |
| delegatee | rickmanelius |
| vesting shares | 1953.311140 VESTS |
| Transaction Info | Block #43199655/Trx d6281adb34df87b561a777dd83d6246515138bf8 |
View Raw JSON Data
{
"trx_id": "d6281adb34df87b561a777dd83d6246515138bf8",
"block": 43199655,
"trx_in_block": 26,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-05-08T14:54:15",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "rickmanelius",
"vesting_shares": "1953.311140 VESTS"
}
]
}2019/10/27 14:31:18
2019/10/27 14:31:18
| parent author | rickmanelius |
| parent permlink | ecommerce-and-blockchain-an-inventory-of-all-areas-that-need-consideration |
| author | steemitboard |
| permlink | steemitboard-notify-rickmanelius-20191027t143117000z |
| title | |
| body | Congratulations @rickmanelius! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@rickmanelius/birthday2.png</td><td>Happy Birthday! - You are on the Steem blockchain for 2 years!</td></tr></table> <sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@rickmanelius) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=rickmanelius)_</sub> ###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| Transaction Info | Block #37652477/Trx 3916d7cd580a8a9702e1c2cd6d3c8df5c05b623a |
View Raw JSON Data
{
"trx_id": "3916d7cd580a8a9702e1c2cd6d3c8df5c05b623a",
"block": 37652477,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-10-27T14:31:18",
"op": [
"comment",
{
"parent_author": "rickmanelius",
"parent_permlink": "ecommerce-and-blockchain-an-inventory-of-all-areas-that-need-consideration",
"author": "steemitboard",
"permlink": "steemitboard-notify-rickmanelius-20191027t143117000z",
"title": "",
"body": "Congratulations @rickmanelius! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@rickmanelius/birthday2.png</td><td>Happy Birthday! - You are on the Steem blockchain for 2 years!</td></tr></table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@rickmanelius) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=rickmanelius)_</sub>\n\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}"
}
]
}steemdelegated 5.469 SP to @rickmanelius2019/07/20 16:06:12
steemdelegated 5.469 SP to @rickmanelius
2019/07/20 16:06:12
| delegator | steem |
| delegatee | rickmanelius |
| vesting shares | 8906.338384 VESTS |
| Transaction Info | Block #34831747/Trx 96b159c88053d8dfe7cbbd6456e3e560f0e8c06e |
View Raw JSON Data
{
"trx_id": "96b159c88053d8dfe7cbbd6456e3e560f0e8c06e",
"block": 34831747,
"trx_in_block": 47,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-07-20T16:06:12",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "rickmanelius",
"vesting_shares": "8906.338384 VESTS"
}
]
}2018/10/27 15:20:36
2018/10/27 15:20:36
| parent author | rickmanelius |
| parent permlink | ecommerce-and-blockchain-an-inventory-of-all-areas-that-need-consideration |
| author | steemitboard |
| permlink | steemitboard-notify-rickmanelius-20181027t152036000z |
| title | |
| body | Congratulations @rickmanelius! You have received a personal award! [](http://steemitboard.com/@rickmanelius) 1 Year on Steemit <sub>_Click on the badge to view your Board of Honor._</sub> **Do not miss the last post from @steemitboard:** <table><tr><td><a href="https://steemit.com/halloween/@steemitboard/trick-or-treat-publish-your-scariest-halloweeen-story-and-win-a-new-badge"><img src="https://steemitimages.com/64x128/http://i.cubeupload.com/RUyB3u.png"></a></td><td><a href="https://steemit.com/halloween/@steemitboard/trick-or-treat-publish-your-scariest-halloweeen-story-and-win-a-new-badge">Trick or Treat - Publish your scariest halloweeen story and win a new badge</a></td></tr><tr><td><a href="https://steemit.com/steemitboard/@steemitboard/steemitboard-notifications-improved"><img src="https://steemitimages.com/64x128/http://i.cubeupload.com/NgygYH.png"></a></td><td><a href="https://steemit.com/steemitboard/@steemitboard/steemitboard-notifications-improved">SteemitBoard notifications improved</a></td></tr></table> > Support [SteemitBoard's project](https://steemit.com/@steemitboard)! **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| Transaction Info | Block #27177930/Trx 891157f692f63a950addb473e401cf44fe9499df |
View Raw JSON Data
{
"trx_id": "891157f692f63a950addb473e401cf44fe9499df",
"block": 27177930,
"trx_in_block": 25,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-10-27T15:20:36",
"op": [
"comment",
{
"parent_author": "rickmanelius",
"parent_permlink": "ecommerce-and-blockchain-an-inventory-of-all-areas-that-need-consideration",
"author": "steemitboard",
"permlink": "steemitboard-notify-rickmanelius-20181027t152036000z",
"title": "",
"body": "Congratulations @rickmanelius! You have received a personal award!\n\n[](http://steemitboard.com/@rickmanelius) 1 Year on Steemit\n<sub>_Click on the badge to view your Board of Honor._</sub>\n\n\n**Do not miss the last post from @steemitboard:**\n<table><tr><td><a href=\"https://steemit.com/halloween/@steemitboard/trick-or-treat-publish-your-scariest-halloweeen-story-and-win-a-new-badge\"><img src=\"https://steemitimages.com/64x128/http://i.cubeupload.com/RUyB3u.png\"></a></td><td><a href=\"https://steemit.com/halloween/@steemitboard/trick-or-treat-publish-your-scariest-halloweeen-story-and-win-a-new-badge\">Trick or Treat - Publish your scariest halloweeen story and win a new badge</a></td></tr><tr><td><a href=\"https://steemit.com/steemitboard/@steemitboard/steemitboard-notifications-improved\"><img src=\"https://steemitimages.com/64x128/http://i.cubeupload.com/NgygYH.png\"></a></td><td><a href=\"https://steemit.com/steemitboard/@steemitboard/steemitboard-notifications-improved\">SteemitBoard notifications improved</a></td></tr></table>\n\n> Support [SteemitBoard's project](https://steemit.com/@steemitboard)! **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}"
}
]
}steemdelegated 5.591 SP to @rickmanelius2018/08/02 04:47:45
steemdelegated 5.591 SP to @rickmanelius
2018/08/02 04:47:45
| delegator | steem |
| delegatee | rickmanelius |
| vesting shares | 9105.058154 VESTS |
| Transaction Info | Block #24705603/Trx 03ac47e553d93d80ce911d65d22aab9b5999262f |
View Raw JSON Data
{
"trx_id": "03ac47e553d93d80ce911d65d22aab9b5999262f",
"block": 24705603,
"trx_in_block": 14,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-08-02T04:47:45",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "rickmanelius",
"vesting_shares": "9105.058154 VESTS"
}
]
}2018/05/03 03:55:42
2018/05/03 03:55:42
| voter | sensation |
| author | rickmanelius |
| permlink | ecommerce-and-blockchain-an-inventory-of-all-areas-that-need-consideration |
| weight | 10000 (100.00%) |
| Transaction Info | Block #22095897/Trx dda576977de7e1463e1d8a0a8a1354d34c10fe96 |
View Raw JSON Data
{
"trx_id": "dda576977de7e1463e1d8a0a8a1354d34c10fe96",
"block": 22095897,
"trx_in_block": 15,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-03T03:55:42",
"op": [
"vote",
{
"voter": "sensation",
"author": "rickmanelius",
"permlink": "ecommerce-and-blockchain-an-inventory-of-all-areas-that-need-consideration",
"weight": 10000
}
]
}2018/05/03 03:45:33
2018/05/03 03:45:33
| voter | moby-dick |
| author | rickmanelius |
| permlink | ecommerce-and-blockchain-an-inventory-of-all-areas-that-need-consideration |
| weight | 10000 (100.00%) |
| Transaction Info | Block #22095694/Trx 16986e0d39f6c0c5416c37103ed9fe8ea515ba03 |
View Raw JSON Data
{
"trx_id": "16986e0d39f6c0c5416c37103ed9fe8ea515ba03",
"block": 22095694,
"trx_in_block": 40,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-03T03:45:33",
"op": [
"vote",
{
"voter": "moby-dick",
"author": "rickmanelius",
"permlink": "ecommerce-and-blockchain-an-inventory-of-all-areas-that-need-consideration",
"weight": 10000
}
]
}2018/05/03 03:30:57
2018/05/03 03:30:57
| voter | magpielover |
| author | rickmanelius |
| permlink | ecommerce-and-blockchain-an-inventory-of-all-areas-that-need-consideration |
| weight | 10000 (100.00%) |
| Transaction Info | Block #22095402/Trx e55aca80afc26b5764a45fc379954fed9ce7dbcf |
View Raw JSON Data
{
"trx_id": "e55aca80afc26b5764a45fc379954fed9ce7dbcf",
"block": 22095402,
"trx_in_block": 43,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-03T03:30:57",
"op": [
"vote",
{
"voter": "magpielover",
"author": "rickmanelius",
"permlink": "ecommerce-and-blockchain-an-inventory-of-all-areas-that-need-consideration",
"weight": 10000
}
]
}2018/05/03 03:00:42
2018/05/03 03:00:42
| voter | ax3 |
| author | rickmanelius |
| permlink | ecommerce-and-blockchain-an-inventory-of-all-areas-that-need-consideration |
| weight | 100 (1.00%) |
| Transaction Info | Block #22094797/Trx d405b5768ed71763fd1227bb71f7db1e21e1cfe7 |
View Raw JSON Data
{
"trx_id": "d405b5768ed71763fd1227bb71f7db1e21e1cfe7",
"block": 22094797,
"trx_in_block": 24,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-03T03:00:42",
"op": [
"vote",
{
"voter": "ax3",
"author": "rickmanelius",
"permlink": "ecommerce-and-blockchain-an-inventory-of-all-areas-that-need-consideration",
"weight": 100
}
]
}rickmaneliuspublished a new post: ecommerce-and-blockchain-an-inventory-of-all-areas-that-need-consideration2018/05/03 03:00:33
rickmaneliuspublished a new post: ecommerce-and-blockchain-an-inventory-of-all-areas-that-need-consideration
2018/05/03 03:00:33
| parent author | |
| parent permlink | ecommerce |
| author | rickmanelius |
| permlink | ecommerce-and-blockchain-an-inventory-of-all-areas-that-need-consideration |
| title | eCommerce & Blockchain: An Inventory of All Areas That Need Consideration |
| body |  One of the biggest thrills of my career was the day a client launched their new online membership program. Once the marketing campaign started, 1000s of payment receipts flooded our inboxes as people joined in droves. Fast forward a few years. One of the terrifying moments of my career was when our 3rd party auditing service flagged us for not being PCI compliant, [which is a requirement]([https://github.com/rickmanelius/drupalpcicompliance) for any merchant wanting to accept credit card payments. We then had to listen in horror as were informed that we might have to shut down our online store within 30 days if we could not prove compliance by this deadline. Worse, if that happened, we would also need to refund all customers orders and payments from the previous 90 days. Yikes! These are just two of the many experiences that I’ve had over the past decade building and maintaining eCommerce experiences, which ranged from small non-profit donation sites to the front-end of a full-blown, 9-figure-a-year revenue stream for an enterprise client. During that time, I’ve had the privilege of learning the ins and outs how to run a successful storefront and back office. Yes, making it easy for a customer to find and purchase a product is paramount, but so is inventory management, securing customer data, refunds, shipping, taxes, accounting, etc. ## Enter Bitcoin & Blockchain While I didn’t initially grok how important Bitcoin would become when I first heard about it several years ago, I’ve since become an avid student of this rapidly evolving technology. Hyperbolic claims aside (and this space is full of them), I do believe that cryptocurrencies represent the future of money. This trend is particularly true on the internet because these technologies have the potential to unlock new opportunities and business models that were not previously possible or feasible with cash and credit cards alone. That said, I do believe there is still a ways to go before [the early and late majority]([https://en.wikipedia.org/wiki/Diffusion_of_innovations) eCommerce merchants adopt embrace and replace approach with swapping out credit cards with cryptocurrencies at their primary means of accepting payments. I am bullish that we will get there, but the focus cannot just be around transaction speed, privacy, security, and fees. Yes, those are all incredibly important! However, many other day-to-day operations are affected. This article is an attempt to outline as many factors that I could come up with and that I plan to research in the coming weeks/months. It would be safe to say that this isn’t comprehensive. While I have had a fair amount of eCommerce exposure, there are probably many use cases that I haven’t had direct experience with. To that end, if I missed anything glaring, please leave a comment, and I will do my best to update this! ## Key Objectives When a new technology replaces an incumbent, there are typically three categories of changes that can occur to the overall functionality: 1. Existing Functionality is Replaced. 2. Existing Functionality is No Longer Possible. 3. New Functionality is Now Possible. To use a crude example. When cars replaced horse and buggy carriages, transportation of people still occurred (existing functionality is replaced). However, the ability to use food as a source of fuel for this transportation went away (existing functionality is no longer possible) and replaced by the new requirement for gas. However, this reliance on gas allowed transportation to go faster and farther (new functionality is now possible). I did not attempt categories each area because there are shades of grey that might make one topic span multiple areas. That said, I find it helpful to keep those in mind when evaluating each bullet. ## Areas That Need Consideration In alphabetical order: * **Access Control:** Traditional eCommerce payment gateway providers provide the ability to set different roles and permissions for things like processing refunds, voiding orders, etc. Cryptocurrencies tend to rely heavily on possession of and direct access to private keys, effectively giving an all-or-none approach. * **Accounting:** Businesses must be able to integrate transactions of all types into their existing accounting systems (e.g., Quickbooks), so they can continue to operate with CPAs, tax accountants, etc. * **Card on File:** This is related to recurring billing (see below). Customers have grown accustomed to the ability to have merchants (e.g., Amazon) store their information and select the method of payment for each order. A similar UX for cryptocurrencies will help reduce friction. * **Compliance:** Merchants wanting to accept credit card payments must meet strict security standards to prove compliance, which can be cost prohibitive. Also, the privilege of accepting card credit payment and it can be revoked if they are in violation. As far as I can tell, cryptocurrencies currently lack a formalized set of best practices, standards, or compliance requirements. This appears to be by design, but merchants could still benefit from best practices. * **Corporate Accounts:** Similar to access control (see above), there will be situations where several members of an organization may need to share access to and pay with a company account. * **Customer Base:** While cryptocurrencies may represent the future, it is estimated that only 3-5% of all Americans even own cryptocurrencies with a much smaller percentage using them for payment. Effectively, we still have a long way to go before we’re fully in [the early adopter stage]([https://en.wikipedia.org/wiki/Diffusion_of_innovations) of the diffusion curve. Given this, it will take time before most merchants will push cryptocurrencies as the primary or only form of payment. * **Customer Support:** While one value proposition of Blockchain is to disintermediate 3rd parties, mistakes happen, and customer support often needs the ability to intervene to assist with submitting, refunding, or changing a payment. There may be a way to do this via smart contracts. * **Debit Cards:** A potential stepping stone solution to increase the usage of cryptocurrencies for everyday payments is by wrapping them behind a debit or credit card that triggers a currency conversion in the background. Tax implications (see below) are still a concern. * **Digital Assets:** Business opportunities like Cryptokitties (where assets can be purchased and transferred via smart contracts directly tied to payments) are significant easier, if not only possible, using cryptocurrencies. * **Exchange Rates:** Given the probability of a merchant wanting to price in fiat currency and the wide diversity of potential cryptocurrencies that customers may wish to use, crypto payments will likely need to have real-time pricing based on API calls to various exchange rate services. * **Fees:** Credit card fees are high but stable. Cryptocurrency fees can be low small but fluctuate as we’ve seen in late 2017. * **Forks:** Businesses may not be equipped to keep up with the rapidly evolving landscape as major projects sometimes hard fork into two or more chains, such as what [recently happened with Monero]([https://globalcoinreport.com/monero-xmr-splits-into-four-different-projects-post-april-4th-hard-fork/). * **Identify Verification:** While there is an admirable goal to push for privacy when using cryptocurrencies, customer support will still need to do things like verify the last four digits of an address. Without billing information tied to this, they may require other forms of verification. * **Integrations:** Over 30% of the web is powered by WordPress, Drupal, or Joomla. Additionally, there are robust PaaS solutions (e.g. Wix, Squarespace, Shopify, etc.) that represent another large percentage. Integrating with these systems will make it significantly easier for customers to begin using cryptocurrencies on a more frequent basis. * **Metered Billing:** Services (like Amazon Web Services) that offer per second pricing still only invoice and charge credit cards on a regular interval (generally monthly) versus in real time or per API call. Technologies like the Lightning Network appear to make metered or streaming pricing possible. Tax implications (see below) are still a concern, particularly if one needs to calculate gain/loss at each microtransaction. * **Mobile Experience:** The ability to balance security and ease of use for an everyday transaction will largely determine if someone in a hurry to buy their latte at the coffee shop will pull out their credit card or fire up their wallet app. * **Nodes:** Certain privacy coins require running a full node for shielding, which can represent a significant barrier to entry for people who already find it challenging to make cryptocurrency payments through services with polished interfaces, such as Coinbase. * **Pricing Volatility:** Given the cost of producing and delivering goods and services is largely based on fiat currencies, merchants wishing to have predictable profit margins are likely going to price in fiat. Additionally, may charge a premium to buffer for price volatility until their margins become more stable. * **Privacy:** While the anonymity of cryptocurrency payments is important, customer data will still likely need to be stored in the merchant database. If/when database breaches occur, this will still tie identify information to a specific address. * **Recurring Billing:** Credit cards (or a reusable token that represents them) can be stored by an eCommerce merchant. This allows them to process recurring payments that a customer has already agreed to when signing up for a particular service. Blockchain can potentially achieve a similar result through smart contracts. * **Refunds, Voids, & Cancelations:** The ability for a back office team to perform these actions will be critical. However, they need to be able to do this without direct access to private keys at a given address. * **Risk (Merchant):** If a Merchant inadvertently lost their private keys, there may be no way to get those funds back. If login credentials are lost for a traditional payment processor or merchant account, access can be restored. Additionally, there are systems in place for detecting and rejecting fraudulent payments and activity. * **Security Model:** Credit card transactions require the transmission, processing, and storage of customer information to be secured at each stage and by anything that affects the card data environment. Blockchain transactions, by contrast, are meant to be submitted to the network for processing. * **Taxes:** While both credit card and crypto payments are subject to sales tax, customers using cryptocurrencies have the additional burden of tracking the value of their currency at the time of sale and reporting on federal and state taxes as a loss or gain. This alone may prevent end-users from wanting to use cryptocurrencies frequently unless/until they are using a service that can help them track this automatically. * **Total Cost of Ownership (TCO):** Ultimately, merchants focusing on top line revenue and bottom line margins are going to want to make sure that the benefits of accepting cryptocurrency are not outweighed by the cost to support and maintain these payment methods. * **User Experience (UX):** The process of easily, quickly, and securely submitting a payment affects how many customers convert, which affects a merchants top line revenue and overall profitability. Hundreds of cryptocurrencies and tokens each with their own set of supported wallets can lead to a very convoluted set of experiences. * **Verification Time:** While some cryptocurrencies offer incredibly fast validation times, waiting up until 10 minutes before being granted access through an online paywall may be untenable for certain users in certain situations. * **Wallets:** End-users may be more comfortable carrying credit cards that have fraud detection than wallets that can be hacked/stolen without any resource. Did I miss anything? As a final reminder, I’m very bullish that the cryptocurrency space will eventually have robust solutions to address all of these areas (if they aren’t already being addressed right now). I recognize that [Coinbase Commerce]([https://commerce.coinbase.com/) is starting to move into this direction with its integration with Shopify. This is a significant step in the right direction and it will help address the needs of merchants that can meet their business needs with a PaaS solution. However, this is but a fraction of the overall market. I’m curious how many months (years?) it will be until WordPress WooCommerce or Drupal Commerce features and promote a similar solution as their defacto payment gateway. THAT will be a big day indeed. Photo by Mike Petrucci on Unsplash |
| json metadata | {"tags":["ecommerce","blockchain","merchants","cryptocurrencies"],"image":["https://steemitimages.com/DQmaG9wBy8terXT8qdeYdgVQtueofX3zhieBKBcZdbzCewa/mike-petrucci-131817-unsplash.jpg"],"links":["[https://github.com/rickmanelius/drupalpcicompliance","[https://en.wikipedia.org/wiki/Diffusion_of_innovations","[https://globalcoinreport.com/monero-xmr-splits-into-four-different-projects-post-april-4th-hard-fork/","[https://commerce.coinbase.com/"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #22094794/Trx 767c3951b3f9ebc6f5745106dd5d8026df85cce4 |
View Raw JSON Data
{
"trx_id": "767c3951b3f9ebc6f5745106dd5d8026df85cce4",
"block": 22094794,
"trx_in_block": 32,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-03T03:00:33",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "ecommerce",
"author": "rickmanelius",
"permlink": "ecommerce-and-blockchain-an-inventory-of-all-areas-that-need-consideration",
"title": "eCommerce & Blockchain: An Inventory of All Areas That Need Consideration",
"body": "\n\nOne of the biggest thrills of my career was the day a client launched their new online membership program. Once the marketing campaign started, 1000s of payment receipts flooded our inboxes as people joined in droves. Fast forward a few years. One of the terrifying moments of my career was when our 3rd party auditing service flagged us for not being PCI compliant, [which is a requirement]([https://github.com/rickmanelius/drupalpcicompliance) for any merchant wanting to accept credit card payments. We then had to listen in horror as were informed that we might have to shut down our online store within 30 days if we could not prove compliance by this deadline. Worse, if that happened, we would also need to refund all customers orders and payments from the previous 90 days. Yikes!\n\nThese are just two of the many experiences that I’ve had over the past decade building and maintaining eCommerce experiences, which ranged from small non-profit donation sites to the front-end of a full-blown, 9-figure-a-year revenue stream for an enterprise client. During that time, I’ve had the privilege of learning the ins and outs how to run a successful storefront and back office. Yes, making it easy for a customer to find and purchase a product is paramount, but so is inventory management, securing customer data, refunds, shipping, taxes, accounting, etc.\n\n## Enter Bitcoin & Blockchain\nWhile I didn’t initially grok how important Bitcoin would become when I first heard about it several years ago, I’ve since become an avid student of this rapidly evolving technology. Hyperbolic claims aside (and this space is full of them), I do believe that cryptocurrencies represent the future of money. This trend is particularly true on the internet because these technologies have the potential to unlock new opportunities and business models that were not previously possible or feasible with cash and credit cards alone.\n\nThat said, I do believe there is still a ways to go before [the early and late majority]([https://en.wikipedia.org/wiki/Diffusion_of_innovations) eCommerce merchants adopt embrace and replace approach with swapping out credit cards with cryptocurrencies at their primary means of accepting payments. I am bullish that we will get there, but the focus cannot just be around transaction speed, privacy, security, and fees. Yes, those are all incredibly important! However, many other day-to-day operations are affected.\n\nThis article is an attempt to outline as many factors that I could come up with and that I plan to research in the coming weeks/months. It would be safe to say that this isn’t comprehensive. While I have had a fair amount of eCommerce exposure, there are probably many use cases that I haven’t had direct experience with. To that end, if I missed anything glaring, please leave a comment, and I will do my best to update this!\n\n## Key Objectives\nWhen a new technology replaces an incumbent, there are typically three categories of changes that can occur to the overall functionality:\n\n1. Existing Functionality is Replaced.\n2. Existing Functionality is No Longer Possible.\n3. New Functionality is Now Possible.\n\nTo use a crude example. When cars replaced horse and buggy carriages, transportation of people still occurred (existing functionality is replaced). However, the ability to use food as a source of fuel for this transportation went away (existing functionality is no longer possible) and replaced by the new requirement for gas. However, this reliance on gas allowed transportation to go faster and farther (new functionality is now possible).\n\nI did not attempt categories each area because there are shades of grey that might make one topic span multiple areas. That said, I find it helpful to keep those in mind when evaluating each bullet.\n\n## Areas That Need Consideration\nIn alphabetical order:\n\n* **Access Control:** Traditional eCommerce payment gateway providers provide the ability to set different roles and permissions for things like processing refunds, voiding orders, etc. Cryptocurrencies tend to rely heavily on possession of and direct access to private keys, effectively giving an all-or-none approach.\n* **Accounting:** Businesses must be able to integrate transactions of all types into their existing accounting systems (e.g., Quickbooks), so they can continue to operate with CPAs, tax accountants, etc.\n* **Card on File:** This is related to recurring billing (see below). Customers have grown accustomed to the ability to have merchants (e.g., Amazon) store their information and select the method of payment for each order. A similar UX for cryptocurrencies will help reduce friction.\n* **Compliance:** Merchants wanting to accept credit card payments must meet strict security standards to prove compliance, which can be cost prohibitive. Also, the privilege of accepting card credit payment and it can be revoked if they are in violation. As far as I can tell, cryptocurrencies currently lack a formalized set of best practices, standards, or compliance requirements. This appears to be by design, but merchants could still benefit from best practices.\n* **Corporate Accounts:** Similar to access control (see above), there will be situations where several members of an organization may need to share access to and pay with a company account.\n* **Customer Base:** While cryptocurrencies may represent the future, it is estimated that only 3-5% of all Americans even own cryptocurrencies with a much smaller percentage using them for payment. Effectively, we still have a long way to go before we’re fully in [the early adopter stage]([https://en.wikipedia.org/wiki/Diffusion_of_innovations) of the diffusion curve. Given this, it will take time before most merchants will push cryptocurrencies as the primary or only form of payment.\n* **Customer Support:** While one value proposition of Blockchain is to disintermediate 3rd parties, mistakes happen, and customer support often needs the ability to intervene to assist with submitting, refunding, or changing a payment. There may be a way to do this via smart contracts.\n* **Debit Cards:** A potential stepping stone solution to increase the usage of cryptocurrencies for everyday payments is by wrapping them behind a debit or credit card that triggers a currency conversion in the background. Tax implications (see below) are still a concern.\n* **Digital Assets:** Business opportunities like Cryptokitties (where assets can be purchased and transferred via smart contracts directly tied to payments) are significant easier, if not only possible, using cryptocurrencies.\n* **Exchange Rates:** Given the probability of a merchant wanting to price in fiat currency and the wide diversity of potential cryptocurrencies that customers may wish to use, crypto payments will likely need to have real-time pricing based on API calls to various exchange rate services.\n* **Fees:** Credit card fees are high but stable. Cryptocurrency fees can be low small but fluctuate as we’ve seen in late 2017.\n* **Forks:** Businesses may not be equipped to keep up with the rapidly evolving landscape as major projects sometimes hard fork into two or more chains, such as what [recently happened with Monero]([https://globalcoinreport.com/monero-xmr-splits-into-four-different-projects-post-april-4th-hard-fork/).\n* **Identify Verification:** While there is an admirable goal to push for privacy when using cryptocurrencies, customer support will still need to do things like verify the last four digits of an address. Without billing information tied to this, they may require other forms of verification.\n* **Integrations:** Over 30% of the web is powered by WordPress, Drupal, or Joomla. Additionally, there are robust PaaS solutions (e.g. Wix, Squarespace, Shopify, etc.) that represent another large percentage. Integrating with these systems will make it significantly easier for customers to begin using cryptocurrencies on a more frequent basis.\n* **Metered Billing:** Services (like Amazon Web Services) that offer per second pricing still only invoice and charge credit cards on a regular interval (generally monthly) versus in real time or per API call. Technologies like the Lightning Network appear to make metered or streaming pricing possible. Tax implications (see below) are still a concern, particularly if one needs to calculate gain/loss at each microtransaction.\n* **Mobile Experience:** The ability to balance security and ease of use for an everyday transaction will largely determine if someone in a hurry to buy their latte at the coffee shop will pull out their credit card or fire up their wallet app.\n* **Nodes:** Certain privacy coins require running a full node for shielding, which can represent a significant barrier to entry for people who already find it challenging to make cryptocurrency payments through services with polished interfaces, such as Coinbase.\n* **Pricing Volatility:** Given the cost of producing and delivering goods and services is largely based on fiat currencies, merchants wishing to have predictable profit margins are likely going to price in fiat. Additionally, may charge a premium to buffer for price volatility until their margins become more stable.\n* **Privacy:** While the anonymity of cryptocurrency payments is important, customer data will still likely need to be stored in the merchant database. If/when database breaches occur, this will still tie identify information to a specific address.\n* **Recurring Billing:** Credit cards (or a reusable token that represents them) can be stored by an eCommerce merchant. This allows them to process recurring payments that a customer has already agreed to when signing up for a particular service. Blockchain can potentially achieve a similar result through smart contracts.\n* **Refunds, Voids, & Cancelations:** The ability for a back office team to perform these actions will be critical. However, they need to be able to do this without direct access to private keys at a given address.\n* **Risk (Merchant):** If a Merchant inadvertently lost their private keys, there may be no way to get those funds back. If login credentials are lost for a traditional payment processor or merchant account, access can be restored. Additionally, there are systems in place for detecting and rejecting fraudulent payments and activity.\n* **Security Model:** Credit card transactions require the transmission, processing, and storage of customer information to be secured at each stage and by anything that affects the card data environment. Blockchain transactions, by contrast, are meant to be submitted to the network for processing.\n* **Taxes:** While both credit card and crypto payments are subject to sales tax, customers using cryptocurrencies have the additional burden of tracking the value of their currency at the time of sale and reporting on federal and state taxes as a loss or gain. This alone may prevent end-users from wanting to use cryptocurrencies frequently unless/until they are using a service that can help them track this automatically.\n* **Total Cost of Ownership (TCO):** Ultimately, merchants focusing on top line revenue and bottom line margins are going to want to make sure that the benefits of accepting cryptocurrency are not outweighed by the cost to support and maintain these payment methods.\n* **User Experience (UX):** The process of easily, quickly, and securely submitting a payment affects how many customers convert, which affects a merchants top line revenue and overall profitability. Hundreds of cryptocurrencies and tokens each with their own set of supported wallets can lead to a very convoluted set of experiences.\n* **Verification Time:** While some cryptocurrencies offer incredibly fast validation times, waiting up until 10 minutes before being granted access through an online paywall may be untenable for certain users in certain situations.\n* **Wallets:** End-users may be more comfortable carrying credit cards that have fraud detection than wallets that can be hacked/stolen without any resource.\n\nDid I miss anything?\n\nAs a final reminder, I’m very bullish that the cryptocurrency space will eventually have robust solutions to address all of these areas (if they aren’t already being addressed right now). I recognize that [Coinbase Commerce]([https://commerce.coinbase.com/) is starting to move into this direction with its integration with Shopify. This is a significant step in the right direction and it will help address the needs of merchants that can meet their business needs with a PaaS solution. However, this is but a fraction of the overall market. I’m curious how many months (years?) it will be until WordPress WooCommerce or Drupal Commerce features and promote a similar solution as their defacto payment gateway. THAT will be a big day indeed.\n\nPhoto by Mike Petrucci on Unsplash",
"json_metadata": "{\"tags\":[\"ecommerce\",\"blockchain\",\"merchants\",\"cryptocurrencies\"],\"image\":[\"https://steemitimages.com/DQmaG9wBy8terXT8qdeYdgVQtueofX3zhieBKBcZdbzCewa/mike-petrucci-131817-unsplash.jpg\"],\"links\":[\"[https://github.com/rickmanelius/drupalpcicompliance\",\"[https://en.wikipedia.org/wiki/Diffusion_of_innovations\",\"[https://globalcoinreport.com/monero-xmr-splits-into-four-different-projects-post-april-4th-hard-fork/\",\"[https://commerce.coinbase.com/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}steemdelegated 18.137 SP to @rickmanelius2018/04/21 20:51:24
steemdelegated 18.137 SP to @rickmanelius
2018/04/21 20:51:24
| delegator | steem |
| delegatee | rickmanelius |
| vesting shares | 29534.171685 VESTS |
| Transaction Info | Block #21771316/Trx 357a029681bed54d17a3f872d9cf1da4ee30bd93 |
View Raw JSON Data
{
"trx_id": "357a029681bed54d17a3f872d9cf1da4ee30bd93",
"block": 21771316,
"trx_in_block": 41,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-21T20:51:24",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "rickmanelius",
"vesting_shares": "29534.171685 VESTS"
}
]
}rickmaneliusupvoted (100.00%) @freedomnation / lambos-and-cryptocurrencies-201778t164339689z2017/12/29 13:54:48
rickmaneliusupvoted (100.00%) @freedomnation / lambos-and-cryptocurrencies-201778t164339689z
2017/12/29 13:54:48
| voter | rickmanelius |
| author | freedomnation |
| permlink | lambos-and-cryptocurrencies-201778t164339689z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18511889/Trx cfa0b20a07b9e69dddc493ffce8428aa3234e150 |
View Raw JSON Data
{
"trx_id": "cfa0b20a07b9e69dddc493ffce8428aa3234e150",
"block": 18511889,
"trx_in_block": 40,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-29T13:54:48",
"op": [
"vote",
{
"voter": "rickmanelius",
"author": "freedomnation",
"permlink": "lambos-and-cryptocurrencies-201778t164339689z",
"weight": 10000
}
]
}rickmaneliusreceived 0.454 SBD, 0.275 SP author reward for @rickmanelius / a-lasting-ledger-legacy2017/12/18 02:21:54
rickmaneliusreceived 0.454 SBD, 0.275 SP author reward for @rickmanelius / a-lasting-ledger-legacy
2017/12/18 02:21:54
| author | rickmanelius |
| permlink | a-lasting-ledger-legacy |
| sbd payout | 0.454 SBD |
| steem payout | 0.000 STEEM |
| vesting payout | 447.031559 VESTS |
| Transaction Info | Block #18181379/Virtual Operation #8 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 18181379,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 8,
"timestamp": "2017-12-18T02:21:54",
"op": [
"author_reward",
{
"author": "rickmanelius",
"permlink": "a-lasting-ledger-legacy",
"sbd_payout": "0.454 SBD",
"steem_payout": "0.000 STEEM",
"vesting_payout": "447.031559 VESTS"
}
]
}2017/12/13 03:09:57
2017/12/13 03:09:57
| voter | rickmanelius |
| author | aggroed |
| permlink | craigslist-now-sorts-by-sellers-by-those-accepting-crypto-a-boon-to-crypto-enthusiasts-everywhere |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18038377/Trx 24eaa59662b32f863ca38e8c60baa181b38f736f |
View Raw JSON Data
{
"trx_id": "24eaa59662b32f863ca38e8c60baa181b38f736f",
"block": 18038377,
"trx_in_block": 9,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-13T03:09:57",
"op": [
"vote",
{
"voter": "rickmanelius",
"author": "aggroed",
"permlink": "craigslist-now-sorts-by-sellers-by-those-accepting-crypto-a-boon-to-crypto-enthusiasts-everywhere",
"weight": 10000
}
]
}2017/12/13 00:40:00
2017/12/13 00:40:00
| parent author | ehiboss |
| parent permlink | the-mandela-effect-proving-and-disproving-it |
| author | rickmanelius |
| permlink | re-ehiboss-the-mandela-effect-proving-and-disproving-it-20171213t003959754z |
| title | |
| body | It's possible that this effect may have several causes that bundle together to a similar outcome. One source could be related to the theory of memory construction and reconstruction described by experts like Vera Birkenbihl. The basic idea is that we as a society expect that we each have a perfect recollection of a memory we stored in our memory web, but this is false because we didn't fully perceive the data accurately in the first place. This is why eyewitness testimony is only accurate a percentage of the time because they thought they had 100% accuracy in their observation of the event but, in reality, their brains either filled in the gaps or that information was never stored in the first place. To link this back to the Mandela effect, consider a piece of information that isn't super important (such as whether or not the Monopoly man wore a monocle) and then consider that a few people may have stated or simply thought it was one way or the other. In the case of the monopoly man, it’s not a big reach to see the archetype related to someone that would potentially wear one. Once that rumor/meme/belief starts, it takes on a life of its own even though it had no basis in fact. That’s just one way. Another explanation could be based on psi phenomenon or morphic fields, although neither of these has been accepted in the standard model of physics. |
| json metadata | {"tags":["science"],"app":"steemit/0.1"} |
| Transaction Info | Block #18035380/Trx 09bdc72e88de0f10ba85d5b81fcb8f559be387c9 |
View Raw JSON Data
{
"trx_id": "09bdc72e88de0f10ba85d5b81fcb8f559be387c9",
"block": 18035380,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-13T00:40:00",
"op": [
"comment",
{
"parent_author": "ehiboss",
"parent_permlink": "the-mandela-effect-proving-and-disproving-it",
"author": "rickmanelius",
"permlink": "re-ehiboss-the-mandela-effect-proving-and-disproving-it-20171213t003959754z",
"title": "",
"body": "It's possible that this effect may have several causes that bundle together to a similar outcome. One source could be related to the theory of memory construction and reconstruction described by experts like Vera Birkenbihl. The basic idea is that we as a society expect that we each have a perfect recollection of a memory we stored in our memory web, but this is false because we didn't fully perceive the data accurately in the first place. This is why eyewitness testimony is only accurate a percentage of the time because they thought they had 100% accuracy in their observation of the event but, in reality, their brains either filled in the gaps or that information was never stored in the first place.\n\nTo link this back to the Mandela effect, consider a piece of information that isn't super important (such as whether or not the Monopoly man wore a monocle) and then consider that a few people may have stated or simply thought it was one way or the other. In the case of the monopoly man, it’s not a big reach to see the archetype related to someone that would potentially wear one. Once that rumor/meme/belief starts, it takes on a life of its own even though it had no basis in fact.\n\nThat’s just one way. Another explanation could be based on psi phenomenon or morphic fields, although neither of these has been accepted in the standard model of physics.",
"json_metadata": "{\"tags\":[\"science\"],\"app\":\"steemit/0.1\"}"
}
]
}steemdelegated 18.262 SP to @rickmanelius2017/12/12 22:22:54
steemdelegated 18.262 SP to @rickmanelius
2017/12/12 22:22:54
| delegator | steem |
| delegatee | rickmanelius |
| vesting shares | 29738.003737 VESTS |
| Transaction Info | Block #18032641/Trx fc1402fff6fde94b0b2ebdca07fd6c818a535e7f |
View Raw JSON Data
{
"trx_id": "fc1402fff6fde94b0b2ebdca07fd6c818a535e7f",
"block": 18032641,
"trx_in_block": 25,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-12T22:22:54",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "rickmanelius",
"vesting_shares": "29738.003737 VESTS"
}
]
}steemitboardupvoted (1.00%) @rickmanelius / a-lasting-ledger-legacy2017/12/12 00:15:39
steemitboardupvoted (1.00%) @rickmanelius / a-lasting-ledger-legacy
2017/12/12 00:15:39
| voter | steemitboard |
| author | rickmanelius |
| permlink | a-lasting-ledger-legacy |
| weight | 100 (1.00%) |
| Transaction Info | Block #18006106/Trx a9c6bfd190d6dbaae3939aa110cf6455356ed826 |
View Raw JSON Data
{
"trx_id": "a9c6bfd190d6dbaae3939aa110cf6455356ed826",
"block": 18006106,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-12T00:15:39",
"op": [
"vote",
{
"voter": "steemitboard",
"author": "rickmanelius",
"permlink": "a-lasting-ledger-legacy",
"weight": 100
}
]
}2017/12/12 00:15:36
2017/12/12 00:15:36
| parent author | rickmanelius |
| parent permlink | a-lasting-ledger-legacy |
| author | steemitboard |
| permlink | steemitboard-notify-rickmanelius-20171212t001556000z |
| title | |
| body | Congratulations @rickmanelius! You have completed some achievement on Steemit and have been rewarded with new badge(s) : [](http://steemitboard.com/@rickmanelius) You made your First Comment Click on any badge to view your own Board of Honor on SteemitBoard. For more information about SteemitBoard, click [here](https://steemit.com/@steemitboard) If you no longer want to receive notifications, reply to this comment with the word `STOP` > By upvoting this notification, you can help all Steemit users. Learn how [here](https://steemit.com/steemitboard/@steemitboard/http-i-cubeupload-com-7ciqeo-png)! |
| json metadata | {"image":["https://steemitboard.com/img/notifications.png"]} |
| Transaction Info | Block #18006105/Trx 71a2eb0b9ab5af932be360446c2b2a21034bec34 |
View Raw JSON Data
{
"trx_id": "71a2eb0b9ab5af932be360446c2b2a21034bec34",
"block": 18006105,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-12T00:15:36",
"op": [
"comment",
{
"parent_author": "rickmanelius",
"parent_permlink": "a-lasting-ledger-legacy",
"author": "steemitboard",
"permlink": "steemitboard-notify-rickmanelius-20171212t001556000z",
"title": "",
"body": "Congratulations @rickmanelius! You have completed some achievement on Steemit and have been rewarded with new badge(s) :\n\n[](http://steemitboard.com/@rickmanelius) You made your First Comment\n\nClick on any badge to view your own Board of Honor on SteemitBoard.\nFor more information about SteemitBoard, click [here](https://steemit.com/@steemitboard)\n\nIf you no longer want to receive notifications, reply to this comment with the word `STOP`\n\n> By upvoting this notification, you can help all Steemit users. Learn how [here](https://steemit.com/steemitboard/@steemitboard/http-i-cubeupload-com-7ciqeo-png)!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notifications.png\"]}"
}
]
}2017/12/11 19:40:57
2017/12/11 19:40:57
| parent author | be4u |
| parent permlink | re-rickmanelius-a-lasting-ledger-legacy-20171211t045415127z |
| author | rickmanelius |
| permlink | re-be4u-re-rickmanelius-a-lasting-ledger-legacy-20171211t194057767z |
| title | |
| body | Hi @be4u. Regarding the "never post content from anywhere", I assume that means content you don't own the copyright for and not just any content? Or is there a duplicate SEO penalty or just a Steemit enforced penalty if you cross post to your own blog (regardless if you properly use a canonical link)? |
| json metadata | {"tags":["introduceyourself"],"users":["be4u"],"app":"steemit/0.1"} |
| Transaction Info | Block #18000614/Trx 24f238397a2047b72b0f2093a0ddf90a3f574c05 |
View Raw JSON Data
{
"trx_id": "24f238397a2047b72b0f2093a0ddf90a3f574c05",
"block": 18000614,
"trx_in_block": 15,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-11T19:40:57",
"op": [
"comment",
{
"parent_author": "be4u",
"parent_permlink": "re-rickmanelius-a-lasting-ledger-legacy-20171211t045415127z",
"author": "rickmanelius",
"permlink": "re-be4u-re-rickmanelius-a-lasting-ledger-legacy-20171211t194057767z",
"title": "",
"body": "Hi @be4u. Regarding the \"never post content from anywhere\", I assume that means content you don't own the copyright for and not just any content? Or is there a duplicate SEO penalty or just a Steemit enforced penalty if you cross post to your own blog (regardless if you properly use a canonical link)?",
"json_metadata": "{\"tags\":[\"introduceyourself\"],\"users\":[\"be4u\"],\"app\":\"steemit/0.1\"}"
}
]
}broncnutzupvoted (11.00%) @rickmanelius / a-lasting-ledger-legacy2017/12/11 06:26:24
broncnutzupvoted (11.00%) @rickmanelius / a-lasting-ledger-legacy
2017/12/11 06:26:24
| voter | broncnutz |
| author | rickmanelius |
| permlink | a-lasting-ledger-legacy |
| weight | 1100 (11.00%) |
| Transaction Info | Block #17984727/Trx e886f2bd133442b8a43deee7d70792412c462309 |
View Raw JSON Data
{
"trx_id": "e886f2bd133442b8a43deee7d70792412c462309",
"block": 17984727,
"trx_in_block": 29,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-11T06:26:24",
"op": [
"vote",
{
"voter": "broncnutz",
"author": "rickmanelius",
"permlink": "a-lasting-ledger-legacy",
"weight": 1100
}
]
}2017/12/11 04:43:12
2017/12/11 04:43:12
| parent author | rickmanelius |
| parent permlink | a-lasting-ledger-legacy |
| author | be4u |
| permlink | re-rickmanelius-a-lasting-ledger-legacy-20171211t045415127z |
| title | |
| body | welcome to steemit world . Always Remember 5 points.. 1)Never copy paste content from any where .. 2)It can take some time but if you work hard , God will definitely give you success.. 3)Never abuse anyone or post haterade content on steemit.. 4)Daily post will increase your REPUTATION SCORE (number by the side of your name) Reputation score is mainly based on upvotes and comments . No matter what you post ,if it gets upvotes and comments then reputation score will increase Don't let anyone flag you or downvote you.. 5)Your first post should be your introduction.. I wish you success You can follow me @be4u |
| json metadata | {"tags":["introduceyourself"],"users":["be4u"],"app":"steemit/0.1"} |
| Transaction Info | Block #17982663/Trx be9680126b52b3d6d3326b886f6a12b4b10cc5c6 |
View Raw JSON Data
{
"trx_id": "be9680126b52b3d6d3326b886f6a12b4b10cc5c6",
"block": 17982663,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-11T04:43:12",
"op": [
"comment",
{
"parent_author": "rickmanelius",
"parent_permlink": "a-lasting-ledger-legacy",
"author": "be4u",
"permlink": "re-rickmanelius-a-lasting-ledger-legacy-20171211t045415127z",
"title": "",
"body": "welcome to steemit world . Always Remember 5 points..\n1)Never copy paste content from any where ..\n2)It can take some time but if you work hard , God will definitely give you success..\n3)Never abuse anyone or post haterade content on steemit..\n4)Daily post will increase your REPUTATION SCORE (number by the side of your name)\n Reputation score is mainly based on upvotes and comments .\n No matter what you post ,if it gets upvotes and comments then reputation score will increase\n Don't let anyone flag you or downvote you..\n5)Your first post should be your introduction..\n I wish you success\n You can follow me @be4u",
"json_metadata": "{\"tags\":[\"introduceyourself\"],\"users\":[\"be4u\"],\"app\":\"steemit/0.1\"}"
}
]
}cqfupvoted (1.00%) @rickmanelius / a-lasting-ledger-legacy2017/12/11 04:40:33
cqfupvoted (1.00%) @rickmanelius / a-lasting-ledger-legacy
2017/12/11 04:40:33
| voter | cqf |
| author | rickmanelius |
| permlink | a-lasting-ledger-legacy |
| weight | 100 (1.00%) |
| Transaction Info | Block #17982610/Trx 3a8ca85d59d7c988244f6111c7760022b0466659 |
View Raw JSON Data
{
"trx_id": "3a8ca85d59d7c988244f6111c7760022b0466659",
"block": 17982610,
"trx_in_block": 25,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-11T04:40:33",
"op": [
"vote",
{
"voter": "cqf",
"author": "rickmanelius",
"permlink": "a-lasting-ledger-legacy",
"weight": 100
}
]
}lopezdacruzupvoted (3.00%) @rickmanelius / a-lasting-ledger-legacy2017/12/11 02:55:12
lopezdacruzupvoted (3.00%) @rickmanelius / a-lasting-ledger-legacy
2017/12/11 02:55:12
| voter | lopezdacruz |
| author | rickmanelius |
| permlink | a-lasting-ledger-legacy |
| weight | 300 (3.00%) |
| Transaction Info | Block #17980504/Trx 764f79d009dab33814ed820e39def06491ecc7fa |
View Raw JSON Data
{
"trx_id": "764f79d009dab33814ed820e39def06491ecc7fa",
"block": 17980504,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-11T02:55:12",
"op": [
"vote",
{
"voter": "lopezdacruz",
"author": "rickmanelius",
"permlink": "a-lasting-ledger-legacy",
"weight": 300
}
]
}2017/12/11 02:55:09
2017/12/11 02:55:09
| parent author | rickmanelius |
| parent permlink | a-lasting-ledger-legacy |
| author | lopezdacruz |
| permlink | re-a-lasting-ledger-legacy-20171211t025509 |
| title | |
| body | Welcome to steemit rickmanelius I wish you success and a fun time here. |
| json metadata | |
| Transaction Info | Block #17980503/Trx 2ade12335ea268b760588d80146bab6aa24f0d00 |
View Raw JSON Data
{
"trx_id": "2ade12335ea268b760588d80146bab6aa24f0d00",
"block": 17980503,
"trx_in_block": 30,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-11T02:55:09",
"op": [
"comment",
{
"parent_author": "rickmanelius",
"parent_permlink": "a-lasting-ledger-legacy",
"author": "lopezdacruz",
"permlink": "re-a-lasting-ledger-legacy-20171211t025509",
"title": "",
"body": "Welcome to steemit rickmanelius I wish you success and a fun time here.",
"json_metadata": ""
}
]
}rickmaneliuspublished a new post: a-lasting-ledger-legacy2017/12/11 02:21:54
rickmaneliuspublished a new post: a-lasting-ledger-legacy
2017/12/11 02:21:54
| parent author | |
| parent permlink | introduceyourself |
| author | rickmanelius |
| permlink | a-lasting-ledger-legacy |
| title | A Lasting Ledger Legacy? |
| body | [I lost 200,000+ emails a year ago](https://rickmanelius.com/article/you%E2%80%99ve-lost-mail-200000-emails-be-exact%E2%80%A6). By itself, it was frustrating because I know had no practical way to retrieve important information that I occasionally needed to access or dig up. However, the bigger gut punch was it was one of the first moments in my life that I realized how much of my identity I have offloaded to technology. Yes we never memorize phone numbers anymore because our iPhones make that a pointless exercise and that’s just the beginning. We’re [literally offloading our memory to the cloud](https://www.scientificamerican.com/article/the-internet-has-become-the-external-hard-drive-for-our-memories/). And that’s amazing except when a technology or human error erases a memory we thought we could retrieve through a google search. I often wonder where our digital trails will be in 60 years. We fear that anything that is every posted online will be there forever to haunt us and yet I’ve tried to search for articles I’ve written on platforms that have since been upgraded only to find that I simply cannot pull up the record anymore. The [Way Back Machine](https://archive.org/web/) is impressive in it’s ability to save snapshots of every site it crawls and yet it too could go away the second it loses funding and can no longer pay for the servers.  I sometimes dwell about my own blog! When I upgrade, do I have to maintain it all with properly aligned 301 redirects to make sure anyone searching (even if it’s just me) can still find it? Or what happens when I simply can’t afford the time or money to maintain it and it all goes away. In short, when I call out into the internet to hear an echo from my past self, will my voice show up? This is not a theoretical question because I spent quite a bit of time making friendships and establishing myself on the Google+ platform before it basically went defunct. Yes it still exists for now, but it’s one board decision away from going away and there is nothing I can do about it except try to scrape what mattered to me and store it…. exactly where? I’m a blockchain, distributed ledger newbie for sure, but what excites me about it all is the concept that what is added to the ledger may persist along the time dimension much more strongly than our current collection of websites and social media platforms that mostly live in the here and now without much thought. Even the [Library of Congress attempted and failed at storing every Tweet](https://www.theatlantic.com/technology/archive/2016/08/can-twitter-fit-inside-the-library-of-congress/494339/) because these are hard problems that a traditional, centralized database still needs a singular entity to solve that and persist long after it loses the funding to do so. I’m not entirely sure I understand the purpose of Steem.it, but I’m very curious if and how it intends to solve this problem. Maybe I’m looking in the wrong place and I’ll find someone else of interest here to keep me coming back instead of maintaining my blog as my primary platform of choice. After all, it’s the only way I can have full control over the copyright and how long it’s accessible on the web until I find something better. Anyway, this may not be your typical introduceyourself intro, but I wanted to post my intention of joining this community in the hopes that I might find others that share that interest, or perhaps even provide me a few pointers along the way. Cheers! |
| json metadata | {"tags":["introduceyourself","legacy","identity","writing","archiving"],"image":["https://steemitimages.com/DQmUkG2SMtCcYWRhRmnhtJ19jNpmiT5hXHLJZHefT4h8WvP/wayback-machine-fund-raising.png"],"links":["https://rickmanelius.com/article/you%E2%80%99ve-lost-mail-200000-emails-be-exact%E2%80%A6","https://www.scientificamerican.com/article/the-internet-has-become-the-external-hard-drive-for-our-memories/","https://archive.org/web/","https://www.theatlantic.com/technology/archive/2016/08/can-twitter-fit-inside-the-library-of-congress/494339/"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #17979838/Trx 0bf7244f04cd6591b4c873465c1bccb07e582fed |
View Raw JSON Data
{
"trx_id": "0bf7244f04cd6591b4c873465c1bccb07e582fed",
"block": 17979838,
"trx_in_block": 18,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-11T02:21:54",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "introduceyourself",
"author": "rickmanelius",
"permlink": "a-lasting-ledger-legacy",
"title": "A Lasting Ledger Legacy?",
"body": "[I lost 200,000+ emails a year ago](https://rickmanelius.com/article/you%E2%80%99ve-lost-mail-200000-emails-be-exact%E2%80%A6). By itself, it was frustrating because I know had no practical way to retrieve important information that I occasionally needed to access or dig up. However, the bigger gut punch was it was one of the first moments in my life that I realized how much of my identity I have offloaded to technology. Yes we never memorize phone numbers anymore because our iPhones make that a pointless exercise and that’s just the beginning. We’re [literally offloading our memory to the cloud](https://www.scientificamerican.com/article/the-internet-has-become-the-external-hard-drive-for-our-memories/). And that’s amazing except when a technology or human error erases a memory we thought we could retrieve through a google search.\n\nI often wonder where our digital trails will be in 60 years. We fear that anything that is every posted online will be there forever to haunt us and yet I’ve tried to search for articles I’ve written on platforms that have since been upgraded only to find that I simply cannot pull up the record anymore. The [Way Back Machine](https://archive.org/web/) is impressive in it’s ability to save snapshots of every site it crawls and yet it too could go away the second it loses funding and can no longer pay for the servers.\n\n\n\nI sometimes dwell about my own blog! When I upgrade, do I have to maintain it all with properly aligned 301 redirects to make sure anyone searching (even if it’s just me) can still find it? Or what happens when I simply can’t afford the time or money to maintain it and it all goes away.\n\nIn short, when I call out into the internet to hear an echo from my past self, will my voice show up? This is not a theoretical question because I spent quite a bit of time making friendships and establishing myself on the Google+ platform before it basically went defunct. Yes it still exists for now, but it’s one board decision away from going away and there is nothing I can do about it except try to scrape what mattered to me and store it…. exactly where?\n\nI’m a blockchain, distributed ledger newbie for sure, but what excites me about it all is the concept that what is added to the ledger may persist along the time dimension much more strongly than our current collection of websites and social media platforms that mostly live in the here and now without much thought. Even the [Library of Congress attempted and failed at storing every Tweet](https://www.theatlantic.com/technology/archive/2016/08/can-twitter-fit-inside-the-library-of-congress/494339/) because these are hard problems that a traditional, centralized database still needs a singular entity to solve that and persist long after it loses the funding to do so.\n\nI’m not entirely sure I understand the purpose of Steem.it, but I’m very curious if and how it intends to solve this problem. Maybe I’m looking in the wrong place and I’ll find someone else of interest here to keep me coming back instead of maintaining my blog as my primary platform of choice. After all, it’s the only way I can have full control over the copyright and how long it’s accessible on the web until I find something better.\n\nAnyway, this may not be your typical introduceyourself intro, but I wanted to post my intention of joining this community in the hopes that I might find others that share that interest, or perhaps even provide me a few pointers along the way.\n\nCheers!",
"json_metadata": "{\"tags\":[\"introduceyourself\",\"legacy\",\"identity\",\"writing\",\"archiving\"],\"image\":[\"https://steemitimages.com/DQmUkG2SMtCcYWRhRmnhtJ19jNpmiT5hXHLJZHefT4h8WvP/wayback-machine-fund-raising.png\"],\"links\":[\"https://rickmanelius.com/article/you%E2%80%99ve-lost-mail-200000-emails-be-exact%E2%80%A6\",\"https://www.scientificamerican.com/article/the-internet-has-become-the-external-hard-drive-for-our-memories/\",\"https://archive.org/web/\",\"https://www.theatlantic.com/technology/archive/2016/08/can-twitter-fit-inside-the-library-of-congress/494339/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}rickmaneliusupdated their account properties2017/12/11 02:16:27
rickmaneliusupdated their account properties
2017/12/11 02:16:27
| account | rickmanelius |
| memo key | STM6G42mm22WrqWkAWaevdjDsYK8KP3AvAhXAj5B2yqZMpviPAAnQ |
| json metadata | {"profile":{"profile_image":"https://rickmanelius.com/sites/default/files/IMCE/theme/about3.jpg","name":"Rick Manelius","location":"Colorado","website":"https://rickmanelius.com/"}} |
| Transaction Info | Block #17979729/Trx af6d5e0849bddf0b9d8b5472f09a6fa2a3006ee7 |
View Raw JSON Data
{
"trx_id": "af6d5e0849bddf0b9d8b5472f09a6fa2a3006ee7",
"block": 17979729,
"trx_in_block": 19,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-11T02:16:27",
"op": [
"account_update",
{
"account": "rickmanelius",
"memo_key": "STM6G42mm22WrqWkAWaevdjDsYK8KP3AvAhXAj5B2yqZMpviPAAnQ",
"json_metadata": "{\"profile\":{\"profile_image\":\"https://rickmanelius.com/sites/default/files/IMCE/theme/about3.jpg\",\"name\":\"Rick Manelius\",\"location\":\"Colorado\",\"website\":\"https://rickmanelius.com/\"}}"
}
]
}rickmaneliusupvoted (100.00%) @firepower / steemit-chat-update-we-re-35000-active-users-now2017/12/09 05:26:21
rickmaneliusupvoted (100.00%) @firepower / steemit-chat-update-we-re-35000-active-users-now
2017/12/09 05:26:21
| voter | rickmanelius |
| author | firepower |
| permlink | steemit-chat-update-we-re-35000-active-users-now |
| weight | 10000 (100.00%) |
| Transaction Info | Block #17925938/Trx 15b40dfec3a7140661a304a341916516613b40e9 |
View Raw JSON Data
{
"trx_id": "15b40dfec3a7140661a304a341916516613b40e9",
"block": 17925938,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-09T05:26:21",
"op": [
"vote",
{
"voter": "rickmanelius",
"author": "firepower",
"permlink": "steemit-chat-update-we-re-35000-active-users-now",
"weight": 10000
}
]
}rickmaneliusupvoted (100.00%) @acidyo / why-steem-offers-one-of-the-most-secure-wallets-in-crypto2017/12/09 05:24:15
rickmaneliusupvoted (100.00%) @acidyo / why-steem-offers-one-of-the-most-secure-wallets-in-crypto
2017/12/09 05:24:15
| voter | rickmanelius |
| author | acidyo |
| permlink | why-steem-offers-one-of-the-most-secure-wallets-in-crypto |
| weight | 10000 (100.00%) |
| Transaction Info | Block #17925896/Trx bb97cd214ca246a26c962485926d67c1593fd804 |
View Raw JSON Data
{
"trx_id": "bb97cd214ca246a26c962485926d67c1593fd804",
"block": 17925896,
"trx_in_block": 8,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-09T05:24:15",
"op": [
"vote",
{
"voter": "rickmanelius",
"author": "acidyo",
"permlink": "why-steem-offers-one-of-the-most-secure-wallets-in-crypto",
"weight": 10000
}
]
}steemcreated a new account: @rickmanelius2017/10/27 13:20:03
steemcreated a new account: @rickmanelius
2017/10/27 13:20:03
| fee | 0.500 STEEM |
| delegation | 57000.000000 VESTS |
| creator | steem |
| new account name | rickmanelius |
| owner | {"weight_threshold":1,"account_auths":[],"key_auths":[["STM8Bf9vbZTzd59ciEKuFKFK6ucjPSuGB7v5tMWTMQJa9ncZfybGo",1]]} |
| active | {"weight_threshold":1,"account_auths":[],"key_auths":[["STM5YPa4PwggzY1Yj1FDx2CSdf3q9tbJrQxDwh4AvpQiVmKoq2RHs",1]]} |
| posting | {"weight_threshold":1,"account_auths":[],"key_auths":[["STM5wcBspXgYSqdaNwausZUP4Npiq8EdJmgCWxcnFjuqKGtxW3bC7",1]]} |
| memo key | STM6G42mm22WrqWkAWaevdjDsYK8KP3AvAhXAj5B2yqZMpviPAAnQ |
| json metadata | |
| extensions | [] |
| Transaction Info | Block #16697633/Trx a6f5a44584b335da10dd068a95a7b2ff0bde3dd7 |
View Raw JSON Data
{
"trx_id": "a6f5a44584b335da10dd068a95a7b2ff0bde3dd7",
"block": 16697633,
"trx_in_block": 30,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-10-27T13:20:03",
"op": [
"account_create_with_delegation",
{
"fee": "0.500 STEEM",
"delegation": "57000.000000 VESTS",
"creator": "steem",
"new_account_name": "rickmanelius",
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM8Bf9vbZTzd59ciEKuFKFK6ucjPSuGB7v5tMWTMQJa9ncZfybGo",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5YPa4PwggzY1Yj1FDx2CSdf3q9tbJrQxDwh4AvpQiVmKoq2RHs",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5wcBspXgYSqdaNwausZUP4Npiq8EdJmgCWxcnFjuqKGtxW3bC7",
1
]
]
},
"memo_key": "STM6G42mm22WrqWkAWaevdjDsYK8KP3AvAhXAj5B2yqZMpviPAAnQ",
"json_metadata": "",
"extensions": []
}
]
}Manabar
Voting Power100.00%
Downvote Power100.00%
Resource Credits100.00%
Reputation Progress79.29%
{
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779082962
},
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779082962
},
"rc_account": {
"account": "rickmanelius",
"rc_manabar": {
"current_mana": "10164408779",
"last_update_time": 1779082962
},
"max_rc_creation_adjustment": {
"amount": "2020748973",
"precision": 6,
"nai": "@@000000037"
},
"max_rc": "10164408779"
}
}Account Metadata
| POSTING JSON METADATA | |
| profile | {"profile_image":"https://rickmanelius.com/sites/default/files/IMCE/theme/about3.jpg","name":"Rick Manelius","location":"Colorado","website":"https://rickmanelius.com/"} |
| JSON METADATA | |
| profile | {"profile_image":"https://rickmanelius.com/sites/default/files/IMCE/theme/about3.jpg","name":"Rick Manelius","location":"Colorado","website":"https://rickmanelius.com/"} |
{
"posting_json_metadata": {
"profile": {
"profile_image": "https://rickmanelius.com/sites/default/files/IMCE/theme/about3.jpg",
"name": "Rick Manelius",
"location": "Colorado",
"website": "https://rickmanelius.com/"
}
},
"json_metadata": {
"profile": {
"profile_image": "https://rickmanelius.com/sites/default/files/IMCE/theme/about3.jpg",
"name": "Rick Manelius",
"location": "Colorado",
"website": "https://rickmanelius.com/"
}
}
}Auth Keys
Owner
Single Signature
Public Keys
STM8Bf9vbZTzd59ciEKuFKFK6ucjPSuGB7v5tMWTMQJa9ncZfybGo1/1
Active
Single Signature
Public Keys
STM5YPa4PwggzY1Yj1FDx2CSdf3q9tbJrQxDwh4AvpQiVmKoq2RHs1/1
Posting
Single Signature
Public Keys
STM5wcBspXgYSqdaNwausZUP4Npiq8EdJmgCWxcnFjuqKGtxW3bC71/1
Memo
STM6G42mm22WrqWkAWaevdjDsYK8KP3AvAhXAj5B2yqZMpviPAAnQ
{
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM8Bf9vbZTzd59ciEKuFKFK6ucjPSuGB7v5tMWTMQJa9ncZfybGo",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5YPa4PwggzY1Yj1FDx2CSdf3q9tbJrQxDwh4AvpQiVmKoq2RHs",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5wcBspXgYSqdaNwausZUP4Npiq8EdJmgCWxcnFjuqKGtxW3bC7",
1
]
]
},
"memo": "STM6G42mm22WrqWkAWaevdjDsYK8KP3AvAhXAj5B2yqZMpviPAAnQ"
}Witness Votes
0 / 30
No active witness votes.
[]