VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS0.00%
Net Worth
0.037USD
STEEM
0.001STEEM
SBD
0.000SBD
Effective Power
5.007SP
├── Own SP
0.632SP
└── Incoming DelegationsDeleg
+4.375SP
Detailed Balance
| STEEM | ||
| balance | 0.001STEEM | STEEM |
| market_balance | 0.000STEEM | STEEM |
| savings_balance | 0.000STEEM | STEEM |
| reward_steem_balance | 0.000STEEM | STEEM |
| STEEM POWER | ||
| Own SP | 0.632SP | SP |
| Delegated Out | 0.000SP | SP |
| Delegation In | 4.375SP | SP |
| Effective Power | 5.007SP | SP |
| Reward SP (pending) | 0.000SP | 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.000SBD | SBD |
{
"balance": "0.001 STEEM",
"savings_balance": "0.000 STEEM",
"reward_steem_balance": "0.000 STEEM",
"vesting_shares": "1028.177082 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "7115.482724 VESTS",
"sbd_balance": "0.000 SBD",
"savings_sbd_balance": "0.000 SBD",
"reward_sbd_balance": "0.000 SBD",
"conversions": []
}Account Info
| name | buddhasource |
| id | 421321 |
| rank | 1,355,644 |
| reputation | 113112106 |
| created | 2017-10-24T03:08:15 |
| recovery_account | steem |
| proxy | None |
| post_count | 4 |
| comment_count | 0 |
| lifetime_vote_count | 0 |
| witnesses_voted_for | 0 |
| last_post | 2019-05-27T04:21:00 |
| last_root_post | 2019-05-27T04:21:00 |
| last_vote_time | 2017-10-25T02:48:48 |
| proxied_vsf_votes | 0, 0, 0, 0 |
| can_vote | 1 |
| voting_power | 0 |
| delayed_votes | 0 |
| balance | 0.001 STEEM |
| savings_balance | 0.000 STEEM |
| sbd_balance | 0.000 SBD |
| savings_sbd_balance | 0.000 SBD |
| vesting_shares | 1028.177082 VESTS |
| delegated_vesting_shares | 0.000000 VESTS |
| received_vesting_shares | 7115.482724 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 | 2018-06-04T04:59:42 |
| mined | No |
| sbd_seconds | 0 |
| sbd_last_interest_payment | 1970-01-01T00:00:00 |
| savings_sbd_last_interest_payment | 1970-01-01T00:00:00 |
{
"active": {
"account_auths": [],
"key_auths": [
[
"STM79b76pgLcNb3cy8YzFmdJzrPsDUZTw3WQoCxPxjkvaoiNWkaF8",
1
]
],
"weight_threshold": 1
},
"balance": "0.001 STEEM",
"can_vote": true,
"comment_count": 0,
"created": "2017-10-24T03:08:15",
"curation_rewards": 0,
"delegated_vesting_shares": "0.000000 VESTS",
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779056544
},
"guest_bloggers": [],
"id": 421321,
"json_metadata": "{\"profile\":{\"profile_image\":\"https://cdn.steemitimages.com/DQmWKTjiypsojHPLJb1u3u18xmBWXjx4KYofH4Mmvf38fVJ/bull-wallpaper-4.jpg\"}}",
"last_account_recovery": "1970-01-01T00:00:00",
"last_account_update": "2018-06-04T04:59:42",
"last_owner_update": "1970-01-01T00:00:00",
"last_post": "2019-05-27T04:21:00",
"last_root_post": "2019-05-27T04:21:00",
"last_vote_time": "2017-10-25T02:48:48",
"lifetime_vote_count": 0,
"market_history": [],
"memo_key": "STM7bV77qkD7scJShyXmnXffBRjE76M9etsdRDsPbRMfWoYJPyeTK",
"mined": false,
"name": "buddhasource",
"next_vesting_withdrawal": "1969-12-31T23:59:59",
"other_history": [],
"owner": {
"account_auths": [],
"key_auths": [
[
"STM5GUKYgufEMufw8qUCRwNQrKw5fTsV6xwNCtqvSud4zrGjFLhri",
1
]
],
"weight_threshold": 1
},
"pending_claimed_accounts": 0,
"post_bandwidth": 0,
"post_count": 4,
"post_history": [],
"posting": {
"account_auths": [],
"key_auths": [
[
"STM8LKoGzHMUgwRFhS4zYVMvgTAenuRNtZpXAN1VPv3f9vbrb6FP6",
1
]
],
"weight_threshold": 1
},
"posting_json_metadata": "{\"profile\":{\"profile_image\":\"https://cdn.steemitimages.com/DQmWKTjiypsojHPLJb1u3u18xmBWXjx4KYofH4Mmvf38fVJ/bull-wallpaper-4.jpg\"}}",
"posting_rewards": 0,
"proxied_vsf_votes": [
0,
0,
0,
0
],
"proxy": "",
"received_vesting_shares": "7115.482724 VESTS",
"recovery_account": "steem",
"reputation": 113112106,
"reset_account": "null",
"reward_sbd_balance": "0.000 SBD",
"reward_steem_balance": "0.000 STEEM",
"reward_vesting_balance": "0.000000 VESTS",
"reward_vesting_steem": "0.000 STEEM",
"savings_balance": "0.000 STEEM",
"savings_sbd_balance": "0.000 SBD",
"savings_sbd_last_interest_payment": "1970-01-01T00:00:00",
"savings_sbd_seconds": "0",
"savings_sbd_seconds_last_update": "1970-01-01T00:00:00",
"savings_withdraw_requests": 0,
"sbd_balance": "0.000 SBD",
"sbd_last_interest_payment": "1970-01-01T00:00:00",
"sbd_seconds": "0",
"sbd_seconds_last_update": "1970-01-01T00:00:00",
"tags_usage": [],
"to_withdraw": 0,
"transfer_history": [],
"vesting_balance": "0.000 STEEM",
"vesting_shares": "1028.177082 VESTS",
"vesting_withdraw_rate": "0.000000 VESTS",
"vote_history": [],
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779056544
},
"voting_power": 0,
"withdraw_routes": 0,
"withdrawn": 0,
"witness_votes": [],
"witnesses_voted_for": 0,
"rank": 1355644
}Withdraw Routes
| Incoming | Outgoing |
|---|---|
Empty | Empty |
{
"incoming": [],
"outgoing": []
}From Date
To Date
steemdelegated 4.375 SP to @buddhasource2026/05/17 22:22:24
steemdelegated 4.375 SP to @buddhasource
2026/05/17 22:22:24
| delegatee | buddhasource |
| delegator | steem |
| vesting shares | 7115.482724 VESTS |
| Transaction Info | Block #106141202/Trx 7de10a152260fe7970b910c0029fc1de74a2289b |
View Raw JSON Data
{
"block": 106141202,
"op": [
"delegate_vesting_shares",
{
"delegatee": "buddhasource",
"delegator": "steem",
"vesting_shares": "7115.482724 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2026-05-17T22:22:24",
"trx_id": "7de10a152260fe7970b910c0029fc1de74a2289b",
"trx_in_block": 1,
"virtual_op": 0
}steemdelegated 2.707 SP to @buddhasource2026/05/11 20:21:12
steemdelegated 2.707 SP to @buddhasource
2026/05/11 20:21:12
| delegatee | buddhasource |
| delegator | steem |
| vesting shares | 4403.272319 VESTS |
| Transaction Info | Block #105966752/Trx 33d93cb3aa1125784129c575fe43014cbdd50089 |
View Raw JSON Data
{
"block": 105966752,
"op": [
"delegate_vesting_shares",
{
"delegatee": "buddhasource",
"delegator": "steem",
"vesting_shares": "4403.272319 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2026-05-11T20:21:12",
"trx_id": "33d93cb3aa1125784129c575fe43014cbdd50089",
"trx_in_block": 1,
"virtual_op": 0
}steemdelegated 4.383 SP to @buddhasource2026/04/25 21:46:12
steemdelegated 4.383 SP to @buddhasource
2026/04/25 21:46:12
| delegatee | buddhasource |
| delegator | steem |
| vesting shares | 7127.998480 VESTS |
| Transaction Info | Block #105508907/Trx 0f0d6e39dbc88738a697876fb240a0ab582dba24 |
View Raw JSON Data
{
"block": 105508907,
"op": [
"delegate_vesting_shares",
{
"delegatee": "buddhasource",
"delegator": "steem",
"vesting_shares": "7127.998480 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2026-04-25T21:46:12",
"trx_id": "0f0d6e39dbc88738a697876fb240a0ab582dba24",
"trx_in_block": 4,
"virtual_op": 0
}steemdelegated 2.733 SP to @buddhasource2026/01/23 02:50:54
steemdelegated 2.733 SP to @buddhasource
2026/01/23 02:50:54
| delegatee | buddhasource |
| delegator | steem |
| vesting shares | 4444.819138 VESTS |
| Transaction Info | Block #102845883/Trx 60ad482cad87dc70d806e3f877f6ee0ee7e30606 |
View Raw JSON Data
{
"block": 102845883,
"op": [
"delegate_vesting_shares",
{
"delegatee": "buddhasource",
"delegator": "steem",
"vesting_shares": "4444.819138 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2026-01-23T02:50:54",
"trx_id": "60ad482cad87dc70d806e3f877f6ee0ee7e30606",
"trx_in_block": 6,
"virtual_op": 0
}steemdelegated 2.834 SP to @buddhasource2024/12/16 22:10:24
steemdelegated 2.834 SP to @buddhasource
2024/12/16 22:10:24
| delegatee | buddhasource |
| delegator | steem |
| vesting shares | 4609.038335 VESTS |
| Transaction Info | Block #91292292/Trx bad5ebf72279eedbf8f016b432b516806dc2772a |
View Raw JSON Data
{
"block": 91292292,
"op": [
"delegate_vesting_shares",
{
"delegatee": "buddhasource",
"delegator": "steem",
"vesting_shares": "4609.038335 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2024-12-16T22:10:24",
"trx_id": "bad5ebf72279eedbf8f016b432b516806dc2772a",
"trx_in_block": 4,
"virtual_op": 0
}steemdelegated 2.938 SP to @buddhasource2023/11/13 13:55:27
steemdelegated 2.938 SP to @buddhasource
2023/11/13 13:55:27
| delegatee | buddhasource |
| delegator | steem |
| vesting shares | 4778.171867 VESTS |
| Transaction Info | Block #79846554/Trx d49c95c2bc5619322b8e7c7e3d406ba106703316 |
View Raw JSON Data
{
"block": 79846554,
"op": [
"delegate_vesting_shares",
{
"delegatee": "buddhasource",
"delegator": "steem",
"vesting_shares": "4778.171867 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2023-11-13T13:55:27",
"trx_id": "d49c95c2bc5619322b8e7c7e3d406ba106703316",
"trx_in_block": 2,
"virtual_op": 0
}steemdelegated 4.744 SP to @buddhasource2023/09/21 19:38:51
steemdelegated 4.744 SP to @buddhasource
2023/09/21 19:38:51
| delegatee | buddhasource |
| delegator | steem |
| vesting shares | 7715.450653 VESTS |
| Transaction Info | Block #78345223/Trx 033a607017c0aa498bebcebfc5a575ba6e350aa4 |
View Raw JSON Data
{
"block": 78345223,
"op": [
"delegate_vesting_shares",
{
"delegatee": "buddhasource",
"delegator": "steem",
"vesting_shares": "7715.450653 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2023-09-21T19:38:51",
"trx_id": "033a607017c0aa498bebcebfc5a575ba6e350aa4",
"trx_in_block": 0,
"virtual_op": 0
}steemdelegated 4.880 SP to @buddhasource2022/11/03 09:41:09
steemdelegated 4.880 SP to @buddhasource
2022/11/03 09:41:09
| delegatee | buddhasource |
| delegator | steem |
| vesting shares | 7937.132091 VESTS |
| Transaction Info | Block #69110852/Trx c3f0658caa091d19ac8510b1bf96d735dc282d1f |
View Raw JSON Data
{
"block": 69110852,
"op": [
"delegate_vesting_shares",
{
"delegatee": "buddhasource",
"delegator": "steem",
"vesting_shares": "7937.132091 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2022-11-03T09:41:09",
"trx_id": "c3f0658caa091d19ac8510b1bf96d735dc282d1f",
"trx_in_block": 0,
"virtual_op": 0
}steemdelegated 5.016 SP to @buddhasource2022/01/17 09:06:51
steemdelegated 5.016 SP to @buddhasource
2022/01/17 09:06:51
| delegatee | buddhasource |
| delegator | steem |
| vesting shares | 8157.665322 VESTS |
| Transaction Info | Block #60807218/Trx 75d6240f85532bd3eb73eca3f1ade840dcae69db |
View Raw JSON Data
{
"block": 60807218,
"op": [
"delegate_vesting_shares",
{
"delegatee": "buddhasource",
"delegator": "steem",
"vesting_shares": "8157.665322 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2022-01-17T09:06:51",
"trx_id": "75d6240f85532bd3eb73eca3f1ade840dcae69db",
"trx_in_block": 2,
"virtual_op": 0
}steemdelegated 5.129 SP to @buddhasource2021/06/13 23:06:42
steemdelegated 5.129 SP to @buddhasource
2021/06/13 23:06:42
| delegatee | buddhasource |
| delegator | steem |
| vesting shares | 8341.433980 VESTS |
| Transaction Info | Block #54605699/Trx 31785d471e03efe3276f019ddaa19faf1e33c017 |
View Raw JSON Data
{
"block": 54605699,
"op": [
"delegate_vesting_shares",
{
"delegatee": "buddhasource",
"delegator": "steem",
"vesting_shares": "8341.433980 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2021-06-13T23:06:42",
"trx_id": "31785d471e03efe3276f019ddaa19faf1e33c017",
"trx_in_block": 3,
"virtual_op": 0
}steemdelegated 5.244 SP to @buddhasource2020/12/11 09:27:57
steemdelegated 5.244 SP to @buddhasource
2020/12/11 09:27:57
| delegatee | buddhasource |
| delegator | steem |
| vesting shares | 8528.855954 VESTS |
| Transaction Info | Block #49353223/Trx 37bd94748fd68e454fd24d5573f46f6804c18d5c |
View Raw JSON Data
{
"block": 49353223,
"op": [
"delegate_vesting_shares",
{
"delegatee": "buddhasource",
"delegator": "steem",
"vesting_shares": "8528.855954 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-12-11T09:27:57",
"trx_id": "37bd94748fd68e454fd24d5573f46f6804c18d5c",
"trx_in_block": 9,
"virtual_op": 0
}steemdelegated 1.176 SP to @buddhasource2020/12/06 03:05:27
steemdelegated 1.176 SP to @buddhasource
2020/12/06 03:05:27
| delegatee | buddhasource |
| delegator | steem |
| vesting shares | 1912.543513 VESTS |
| Transaction Info | Block #49204795/Trx 6029e7bfd1d1cb65b31d224ef52d90bf7962b09b |
View Raw JSON Data
{
"block": 49204795,
"op": [
"delegate_vesting_shares",
{
"delegatee": "buddhasource",
"delegator": "steem",
"vesting_shares": "1912.543513 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-12-06T03:05:27",
"trx_id": "6029e7bfd1d1cb65b31d224ef52d90bf7962b09b",
"trx_in_block": 0,
"virtual_op": 0
}steemdelegated 5.248 SP to @buddhasource2020/12/05 11:02:18
steemdelegated 5.248 SP to @buddhasource
2020/12/05 11:02:18
| delegatee | buddhasource |
| delegator | steem |
| vesting shares | 8535.222593 VESTS |
| Transaction Info | Block #49185898/Trx 5be82006aa6f7b4146f0f8df03a63f331a67cd72 |
View Raw JSON Data
{
"block": 49185898,
"op": [
"delegate_vesting_shares",
{
"delegatee": "buddhasource",
"delegator": "steem",
"vesting_shares": "8535.222593 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-12-05T11:02:18",
"trx_id": "5be82006aa6f7b4146f0f8df03a63f331a67cd72",
"trx_in_block": 25,
"virtual_op": 0
}steemdelegated 1.181 SP to @buddhasource2020/11/02 12:00:12
steemdelegated 1.181 SP to @buddhasource
2020/11/02 12:00:12
| delegatee | buddhasource |
| delegator | steem |
| vesting shares | 1920.017158 VESTS |
| Transaction Info | Block #48253524/Trx 9116057e5aca9f7fd10798f8903e8ecd04211d0e |
View Raw JSON Data
{
"block": 48253524,
"op": [
"delegate_vesting_shares",
{
"delegatee": "buddhasource",
"delegator": "steem",
"vesting_shares": "1920.017158 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-11-02T12:00:12",
"trx_id": "9116057e5aca9f7fd10798f8903e8ecd04211d0e",
"trx_in_block": 4,
"virtual_op": 0
}steemdelegated 5.373 SP to @buddhasource2020/05/09 04:00:42
steemdelegated 5.373 SP to @buddhasource
2020/05/09 04:00:42
| delegatee | buddhasource |
| delegator | steem |
| vesting shares | 8737.869167 VESTS |
| Transaction Info | Block #43215012/Trx 05c3294d880427f6160e3a9d3c1ba9d674b99a9c |
View Raw JSON Data
{
"block": 43215012,
"op": [
"delegate_vesting_shares",
{
"delegatee": "buddhasource",
"delegator": "steem",
"vesting_shares": "8737.869167 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-05-09T04:00:42",
"trx_id": "05c3294d880427f6160e3a9d3c1ba9d674b99a9c",
"trx_in_block": 28,
"virtual_op": 0
}steemdelegated 1.201 SP to @buddhasource2020/05/08 07:21:36
steemdelegated 1.201 SP to @buddhasource
2020/05/08 07:21:36
| delegatee | buddhasource |
| delegator | steem |
| vesting shares | 1953.311140 VESTS |
| Transaction Info | Block #43190811/Trx fe5eacc1689e3b5182ea8205c681fb2b4ab4cf7f |
View Raw JSON Data
{
"block": 43190811,
"op": [
"delegate_vesting_shares",
{
"delegatee": "buddhasource",
"delegator": "steem",
"vesting_shares": "1953.311140 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-05-08T07:21:36",
"trx_id": "fe5eacc1689e3b5182ea8205c681fb2b4ab4cf7f",
"trx_in_block": 5,
"virtual_op": 0
}2019/10/24 05:02:42
2019/10/24 05:02:42
| author | steemitboard |
| body | Congratulations @buddhasource! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@buddhasource/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/@buddhasource) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=buddhasource)_</sub> **Do not miss the last post from @steemitboard:** <table><tr><td><a href="https://steemit.com/steemfest/@steemitboard/steemfest-commemorative-badge-refactored"><img src="https://steemitimages.com/64x128/https://files.steempeak.com/file/steempeak/arcange/YqQV5Tbj-image.png"></a></td><td><a href="https://steemit.com/steemfest/@steemitboard/steemfest-commemorative-badge-refactored">SteemFest⁴ commemorative badge refactored</a></td></tr></table> ###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| parent author | buddhasource |
| parent permlink | how-to-build-a-p2p-crypto-exchange-successfully |
| permlink | steemitboard-notify-buddhasource-20191024t050242000z |
| title | |
| Transaction Info | Block #37554896/Trx e9665438e7b8294be39f61197c61b1cd97c65099 |
View Raw JSON Data
{
"block": 37554896,
"op": [
"comment",
{
"author": "steemitboard",
"body": "Congratulations @buddhasource! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@buddhasource/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/@buddhasource) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=buddhasource)_</sub>\n\n\n**Do not miss the last post from @steemitboard:**\n<table><tr><td><a href=\"https://steemit.com/steemfest/@steemitboard/steemfest-commemorative-badge-refactored\"><img src=\"https://steemitimages.com/64x128/https://files.steempeak.com/file/steempeak/arcange/YqQV5Tbj-image.png\"></a></td><td><a href=\"https://steemit.com/steemfest/@steemitboard/steemfest-commemorative-badge-refactored\">SteemFest⁴ commemorative badge refactored</a></td></tr></table>\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}",
"parent_author": "buddhasource",
"parent_permlink": "how-to-build-a-p2p-crypto-exchange-successfully",
"permlink": "steemitboard-notify-buddhasource-20191024t050242000z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2019-10-24T05:02:42",
"trx_id": "e9665438e7b8294be39f61197c61b1cd97c65099",
"trx_in_block": 10,
"virtual_op": 0
}steemdelegated 5.462 SP to @buddhasource2019/08/26 06:18:42
steemdelegated 5.462 SP to @buddhasource
2019/08/26 06:18:42
| delegatee | buddhasource |
| delegator | steem |
| vesting shares | 8883.944841 VESTS |
| Transaction Info | Block #35882628/Trx 21cd95f3fa6459b0b3f150c49120b02cf6ad5fbe |
View Raw JSON Data
{
"block": 35882628,
"op": [
"delegate_vesting_shares",
{
"delegatee": "buddhasource",
"delegator": "steem",
"vesting_shares": "8883.944841 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2019-08-26T06:18:42",
"trx_id": "21cd95f3fa6459b0b3f150c49120b02cf6ad5fbe",
"trx_in_block": 4,
"virtual_op": 0
}steemdelegated 17.751 SP to @buddhasource2019/05/27 05:47:33
steemdelegated 17.751 SP to @buddhasource
2019/05/27 05:47:33
| delegatee | buddhasource |
| delegator | steem |
| vesting shares | 28870.028918 VESTS |
| Transaction Info | Block #33266263/Trx bed9d0152c831bb2ea8c2fca1751c0d7bf330d66 |
View Raw JSON Data
{
"block": 33266263,
"op": [
"delegate_vesting_shares",
{
"delegatee": "buddhasource",
"delegator": "steem",
"vesting_shares": "28870.028918 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2019-05-27T05:47:33",
"trx_id": "bed9d0152c831bb2ea8c2fca1751c0d7bf330d66",
"trx_in_block": 4,
"virtual_op": 0
}hiroyamagishisent 0.001 STEEM to @buddhasource- "
We will support people who will watch our video topic explained by Brother Eli. We have dedicated 24,000 Steem Power to vote for all of your comment. Comment the summary of what we understand on the ..."2019/05/27 04:21:06
hiroyamagishisent 0.001 STEEM to @buddhasource- "
We will support people who will watch our video topic explained by Brother Eli. We have dedicated 24,000 Steem Power to vote for all of your comment. Comment the summary of what we understand on the ..."
2019/05/27 04:21:06
| amount | 0.001 STEEM |
| from | hiroyamagishi |
| memo | We will support people who will watch our video topic explained by Brother Eli. We have dedicated 24,000 Steem Power to vote for all of your comment. Comment the summary of what we understand on the topic of the day. We invite you to also join our Discord chat. https://discord.gg/vzHFNd6 |
| to | buddhasource |
| Transaction Info | Block #33264535/Trx 46c384629a879aad471a3c50992cea13606a6895 |
View Raw JSON Data
{
"block": 33264535,
"op": [
"transfer",
{
"amount": "0.001 STEEM",
"from": "hiroyamagishi",
"memo": "\nWe will support people who will watch our video topic explained by Brother Eli. We have dedicated 24,000 Steem Power to vote for all of your comment. Comment the summary of what we understand on the topic of the day.\nWe invite you to also join our Discord chat.\nhttps://discord.gg/vzHFNd6\n",
"to": "buddhasource"
}
],
"op_in_trx": 0,
"timestamp": "2019-05-27T04:21:06",
"trx_id": "46c384629a879aad471a3c50992cea13606a6895",
"trx_in_block": 11,
"virtual_op": 0
}buddhasourcepublished a new post: how-to-build-a-p2p-crypto-exchange-successfully2019/05/27 04:21:00
buddhasourcepublished a new post: how-to-build-a-p2p-crypto-exchange-successfully
2019/05/27 04:21:00
| author | buddhasource |
| body |  The RBI had just decided to turn their heads on traders during the boom of crypto trading in India; done by enforcing a ban on banks, barring everyone from trading in cryptocurrencies with INR. Traders were hit hard, the market dipped in fear. We had to find a way to overcome this unprecedented blow to our traders, and this is how we did it! We built the first auto order matching P2P system in the world, integrated into WazirX. More on what we have achieved & how we built this. ## Our Progress so far * Record-breaking for any P2P — Average trade time is just~17 mins. (Order placed → Bank Transfer → Confirmation) * We achieved 166cr INR (24 million USDT) in trading so far. * Auto order matching with the open order book, first in the world * Highest liquidity. * Oh and we built & launched this in 16 days  Our Goals with P2P When we started planning for P2P we laid down some important goals. This kept us razer focused on the problem we were solving. Below I will list these goals and a brief of how we achieved them. * Solving high liquidity * Instant and Simple * Safe ## Crypto Economics: Solving liquidity The tricky bit. We had some hard decisions to make. ### The INR liquidity problem After the banking ban, there was no way to increase INR reserves which meant the overall liquidity of the market will have a cap. We wanted unlimited liquidity as a cap is bad for a marketplace. A market’s volume is also directly proportionate to the liquidity of the currency, buying power. A growing market needs a growing chart of quote currency that is INR. An example, if the total INR reserves in WazirX is 1Cr INR then the maximum liquidity if everyone is active is 1Cr INR. Considering human behavior, not everyone will be active thereby further reducing the circulating supply. ### Evaluating INR / INR for P2P We had to make a decision whether to keep INR as a quote or introduce USDT market to keep growing our liquidity. The only way to keep INR quote is to increase our INR reserves or swap INR using INR / INR P2P. A major challenge about INR / INR P2P liquidity is the exchange heavily dependents on INR holders who are active. And this number goes down in the bear market, hence there’s a bottleneck. The other way to increase INR liquidity is by extrapolating INR reserves, if done ethically, this can be done by incentivizing peers to hold INR in their bank reserves on exchange’s behalf, with this an Exchange which has 1Cr INR can extrapolate to say 3Cr INR or more. However, this whole process lacks transparency and the exchange is risking its solvency. Some exchange might claim to safeguard its solvency by taking crypto as collateral, during crisis converting collateral Crypto → INR is another problem, they will have to use local-bitcoins or other ways to convert to INR, all this is subjected to external liquidity. This is too risky for an exchange and its users. ### Why USDT / INR works Considering many such risky and ethical aspects we introduced USDT/INR and not INR/INR for P2P. Here the USDT liquidity is not capped, plus peers are in full control of their fiat-INR, decentralizing fiat. The exchange is not depended on peers to keep the solvency. All this ultimately helped us take no risk as an exchange, less dependency on dormant traders and no cap on liquidity. We chose a stable coin USDT over BTC/INR since volatility won’t discourage trades. ## Auto-matching vs Listing? Simplicity When I was considering P2P, I wasn’t really happy with what was out there. The most popular model was like a classified listing, decisions like price, volume, reputation, last active, etc were to be considered before making the trade. This created friction. We wanted a simpler process, closer to existing trading behavior, eliminating the tricky stuff. The best businesses eat their customer’s complexity. So we build this P2P market place like an exchange with auto-matching orders, this was the world’s first, it was quite a challenge. What we built was sexy and an instant hit. As a trader, you don’t have to worry about reputations or volume split per trader. The system does that for you and simply presents you with a list of folks to make payments to. The demand and supply are automatically sorted by price so we don’t control the market premiums/discounts, it regulates itself, no tips, no bonus, no fuel, no new fancy terms, just basic trading. Over time we learned a lot of things and incorporated algorithms to make sure trading is instant and simple. ### Trade in USDT or INR in India? Most of us have tracked Bitcoin in INR than in USD. While we picked USDT as the logical market to grow post ban, we knew it would be very difficult to get Indian traders to get used to USDT market over INR. Some speculated crypto-crypto is not for India, but there is always a first time for everything. We then built “ Trade in USDT & BTC markets with INR ”. It was some engineering and product marvel, our traders loved it, we eased folks into trading in USDT and BTC markets while maintaining the comfort zone of INR. All the USDT and BTC value are converted to equivalent INR in real time, we made it easy. The buy/sell form also had a mode where you can enter INR price which will later be equated to USDT or BTC.  ## Security, Safety When we started this project all I could think of is stories of various scams on localbitcoin.com and few other sites. Safe and secure transactions were one of the most important goals, there are various algorithms and gamified economic models to keep things safe. Features like collateral for buyers has brought in more trust in the system, we make sure at any point of transaction your funds are safe. ## Conclusion We introduced distinct patterns and changed the game for P2P trading. In the process, we learned quite a bit and had a lot of fun doing it. Today in India it is possible to buy and sell large volumes of BTC in a few hours, some say it is better than non-ban days. Note WazirX P2P is also a decentralized fiat exchange with auto order matching, traders have full control of their fiat funds. If you have any questions or feedback feel free to tweet out to me. My DMs are open. We are working hard to make P2P better every day for you. Cheers! - Siddharth Menon Twitter http://twitter.com/buddhasource |
| json metadata | {"tags":["p2p","crypto","localbitcoin","wazirx","india"],"image":["https://cdn.steemitimages.com/DQmdQCwKpGH42eJMQTL4K61gfjmz4dFJqcw9DFxLCFXyf6x/image.png","https://cdn.steemitimages.com/DQmScJfH792JXzScC56XE3oW1W6a6fJ8iALPNJDMMeFHsRB/image.png","https://cdn.steemitimages.com/DQmS8vPBh4w5ETLrgDqN225zCGtXJ6sn1KxorGvMAr7ZXce/image.png"],"links":["http://twitter.com/buddhasource"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | p2p |
| permlink | how-to-build-a-p2p-crypto-exchange-successfully |
| title | How to build a P2P crypto exchange successfully |
| Transaction Info | Block #33264533/Trx 6b9606ae209f3dbe106c887cf5742820798dd30b |
View Raw JSON Data
{
"block": 33264533,
"op": [
"comment",
{
"author": "buddhasource",
"body": "\nThe RBI had just decided to turn their heads on traders during the boom of crypto trading in India; done by enforcing a ban on banks, barring everyone from trading in cryptocurrencies with INR.\n\nTraders were hit hard, the market dipped in fear. We had to find a way to overcome this unprecedented blow to our traders, and this is how we did it!\n\nWe built the first auto order matching P2P system in the world, integrated into WazirX. More on what we have achieved & how we built this.\n\n## Our Progress so far\n* Record-breaking for any P2P — Average trade time is just~17 mins.\n (Order placed → Bank Transfer → Confirmation)\n* We achieved 166cr INR (24 million USDT) in trading so far.\n* Auto order matching with the open order book, first in the world\n* Highest liquidity.\n* Oh and we built & launched this in 16 days\n\n\n\nOur Goals with P2P\nWhen we started planning for P2P we laid down some important goals. This kept us razer focused on the problem we were solving. Below I will list these goals and a brief of how we achieved them.\n\n* Solving high liquidity\n* Instant and Simple\n* Safe\n\n## Crypto Economics: Solving liquidity\nThe tricky bit. We had some hard decisions to make.\n\n### The INR liquidity problem\nAfter the banking ban, there was no way to increase INR reserves which meant the overall liquidity of the market will have a cap. We wanted unlimited liquidity as a cap is bad for a marketplace.\n\nA market’s volume is also directly proportionate to the liquidity of the currency, buying power. A growing market needs a growing chart of quote currency that is INR.\n\nAn example, if the total INR reserves in WazirX is 1Cr INR then the maximum liquidity if everyone is active is 1Cr INR. Considering human behavior, not everyone will be active thereby further reducing the circulating supply.\n\n### Evaluating INR / INR for P2P\nWe had to make a decision whether to keep INR as a quote or introduce USDT market to keep growing our liquidity. The only way to keep INR quote is to increase our INR reserves or swap INR using INR / INR P2P.\n\nA major challenge about INR / INR P2P liquidity is the exchange heavily dependents on INR holders who are active. And this number goes down in the bear market, hence there’s a bottleneck.\n\nThe other way to increase INR liquidity is by extrapolating INR reserves, if done ethically, this can be done by incentivizing peers to hold INR in their bank reserves on exchange’s behalf, with this an Exchange which has 1Cr INR can extrapolate to say 3Cr INR or more. \n \nHowever, this whole process lacks transparency and the exchange is risking its solvency. Some exchange might claim to safeguard its solvency by taking crypto as collateral, during crisis converting collateral Crypto → INR is another problem, they will have to use local-bitcoins or other ways to convert to INR, all this is subjected to external liquidity.\n\nThis is too risky for an exchange and its users.\n\n### Why USDT / INR works\nConsidering many such risky and ethical aspects we introduced USDT/INR and not INR/INR for P2P. Here the USDT liquidity is not capped, plus peers are in full control of their fiat-INR, decentralizing fiat. The exchange is not depended on peers to keep the solvency.\n\nAll this ultimately helped us take no risk as an exchange, less dependency on dormant traders and no cap on liquidity. We chose a stable coin USDT over BTC/INR since volatility won’t discourage trades.\n\n## Auto-matching vs Listing? Simplicity\nWhen I was considering P2P, I wasn’t really happy with what was out there. The most popular model was like a classified listing, decisions like price, volume, reputation, last active, etc were to be considered before making the trade. This created friction.\n\nWe wanted a simpler process, closer to existing trading behavior, eliminating the tricky stuff.\n\nThe best businesses eat their customer’s complexity.\nSo we build this P2P market place like an exchange with auto-matching orders, this was the world’s first, it was quite a challenge.\n\nWhat we built was sexy and an instant hit. As a trader, you don’t have to worry about reputations or volume split per trader. The system does that for you and simply presents you with a list of folks to make payments to.\n\nThe demand and supply are automatically sorted by price so we don’t control the market premiums/discounts, it regulates itself, no tips, no bonus, no fuel, no new fancy terms, just basic trading.\n\nOver time we learned a lot of things and incorporated algorithms to make sure trading is instant and simple.\n\n### Trade in USDT or INR in India?\nMost of us have tracked Bitcoin in INR than in USD. While we picked USDT as the logical market to grow post ban, we knew it would be very difficult to get Indian traders to get used to USDT market over INR.\n\nSome speculated crypto-crypto is not for India, but there is always a first time for everything.\n\nWe then built “ Trade in USDT & BTC markets with INR ”. It was some engineering and product marvel, our traders loved it, we eased folks into trading in USDT and BTC markets while maintaining the comfort zone of INR.\n\nAll the USDT and BTC value are converted to equivalent INR in real time, we made it easy. The buy/sell form also had a mode where you can enter INR price which will later be equated to USDT or BTC.\n\n\n\n## Security, Safety\nWhen we started this project all I could think of is stories of various scams on localbitcoin.com and few other sites. Safe and secure transactions were one of the most important goals, there are various algorithms and gamified economic models to keep things safe.\n\nFeatures like collateral for buyers has brought in more trust in the system, we make sure at any point of transaction your funds are safe.\n\n## Conclusion\nWe introduced distinct patterns and changed the game for P2P trading. In the process, we learned quite a bit and had a lot of fun doing it. Today in India it is possible to buy and sell large volumes of BTC in a few hours, some say it is better than non-ban days.\n\nNote WazirX P2P is also a decentralized fiat exchange with auto order matching, traders have full control of their fiat funds.\n\nIf you have any questions or feedback feel free to tweet out to me. My DMs are open. We are working hard to make P2P better every day for you. Cheers!\n\n- Siddharth Menon\nTwitter http://twitter.com/buddhasource",
"json_metadata": "{\"tags\":[\"p2p\",\"crypto\",\"localbitcoin\",\"wazirx\",\"india\"],\"image\":[\"https://cdn.steemitimages.com/DQmdQCwKpGH42eJMQTL4K61gfjmz4dFJqcw9DFxLCFXyf6x/image.png\",\"https://cdn.steemitimages.com/DQmScJfH792JXzScC56XE3oW1W6a6fJ8iALPNJDMMeFHsRB/image.png\",\"https://cdn.steemitimages.com/DQmS8vPBh4w5ETLrgDqN225zCGtXJ6sn1KxorGvMAr7ZXce/image.png\"],\"links\":[\"http://twitter.com/buddhasource\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "p2p",
"permlink": "how-to-build-a-p2p-crypto-exchange-successfully",
"title": "How to build a P2P crypto exchange successfully"
}
],
"op_in_trx": 0,
"timestamp": "2019-05-27T04:21:00",
"trx_id": "6b9606ae209f3dbe106c887cf5742820798dd30b",
"trx_in_block": 25,
"virtual_op": 0
}2019/05/27 04:13:21
2019/05/27 04:13:21
| author | buddhasource |
| permlink | bitcoin-legacy-vs-segwit-wallet-address-what-is-the-difference |
| voter | buddhasource |
| weight | 10000 (100.00%) |
| Transaction Info | Block #33264380/Trx c73ea38aed16f128b4e194f98e1d9604506498a6 |
View Raw JSON Data
{
"block": 33264380,
"op": [
"vote",
{
"author": "buddhasource",
"permlink": "bitcoin-legacy-vs-segwit-wallet-address-what-is-the-difference",
"voter": "buddhasource",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2019-05-27T04:13:21",
"trx_id": "c73ea38aed16f128b4e194f98e1d9604506498a6",
"trx_in_block": 19,
"virtual_op": 0
}2018/10/24 13:18:57
2018/10/24 13:18:57
| author | steemitboard |
| body | Congratulations @buddhasource! You have received a personal award! [](http://steemitboard.com/@buddhasource) 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/steemitboard/@steemitboard/steemitboard-ranking-update-resteem-and-resteemed-added"><img src="https://steemitimages.com/64x128/https://cdn.steemitimages.com/DQmfRVpHQhLDhnjDtqck8GPv9NPvNKPfMsDaAFDE1D9Er2Z/header_ranking.png"></a></td><td><a href="https://steemit.com/steemitboard/@steemitboard/steemitboard-ranking-update-resteem-and-resteemed-added">SteemitBoard Ranking update - Resteem and Resteemed added</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"]} |
| parent author | buddhasource |
| parent permlink | bitcoin-legacy-vs-segwit-wallet-address-what-is-the-difference |
| permlink | steemitboard-notify-buddhasource-20181024t131856000z |
| title | |
| Transaction Info | Block #27089161/Trx d3317da0427851b5d5047540be584a795c13df70 |
View Raw JSON Data
{
"block": 27089161,
"op": [
"comment",
{
"author": "steemitboard",
"body": "Congratulations @buddhasource! You have received a personal award!\n\n[](http://steemitboard.com/@buddhasource) 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/steemitboard/@steemitboard/steemitboard-ranking-update-resteem-and-resteemed-added\"><img src=\"https://steemitimages.com/64x128/https://cdn.steemitimages.com/DQmfRVpHQhLDhnjDtqck8GPv9NPvNKPfMsDaAFDE1D9Er2Z/header_ranking.png\"></a></td><td><a href=\"https://steemit.com/steemitboard/@steemitboard/steemitboard-ranking-update-resteem-and-resteemed-added\">SteemitBoard Ranking update - Resteem and Resteemed added</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\"]}",
"parent_author": "buddhasource",
"parent_permlink": "bitcoin-legacy-vs-segwit-wallet-address-what-is-the-difference",
"permlink": "steemitboard-notify-buddhasource-20181024t131856000z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2018-10-24T13:18:57",
"trx_id": "d3317da0427851b5d5047540be584a795c13df70",
"trx_in_block": 2,
"virtual_op": 0
}steemdelegated 5.588 SP to @buddhasource2018/09/03 06:56:39
steemdelegated 5.588 SP to @buddhasource
2018/09/03 06:56:39
| delegatee | buddhasource |
| delegator | steem |
| vesting shares | 9087.423455 VESTS |
| Transaction Info | Block #25629381/Trx d740d2bf2033a462620cee3e2be453025e14b305 |
View Raw JSON Data
{
"block": 25629381,
"op": [
"delegate_vesting_shares",
{
"delegatee": "buddhasource",
"delegator": "steem",
"vesting_shares": "9087.423455 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2018-09-03T06:56:39",
"trx_id": "d740d2bf2033a462620cee3e2be453025e14b305",
"trx_in_block": 19,
"virtual_op": 0
}2018/06/04 04:59:45
2018/06/04 04:59:45
| author | buddhasource |
| permlink | bitcoin-legacy-vs-segwit-wallet-address-what-is-the-difference |
| voter | swagger |
| weight | 3 (0.03%) |
| Transaction Info | Block #23018213/Trx 9f72902e249123e0ce2c3882528cda4176f0f8db |
View Raw JSON Data
{
"block": 23018213,
"op": [
"vote",
{
"author": "buddhasource",
"permlink": "bitcoin-legacy-vs-segwit-wallet-address-what-is-the-difference",
"voter": "swagger",
"weight": 3
}
],
"op_in_trx": 0,
"timestamp": "2018-06-04T04:59:45",
"trx_id": "9f72902e249123e0ce2c3882528cda4176f0f8db",
"trx_in_block": 66,
"virtual_op": 0
}buddhasourceupdated their account properties2018/06/04 04:59:42
buddhasourceupdated their account properties
2018/06/04 04:59:42
| account | buddhasource |
| json metadata | {"profile":{"profile_image":"https://cdn.steemitimages.com/DQmWKTjiypsojHPLJb1u3u18xmBWXjx4KYofH4Mmvf38fVJ/bull-wallpaper-4.jpg"}} |
| memo key | STM7bV77qkD7scJShyXmnXffBRjE76M9etsdRDsPbRMfWoYJPyeTK |
| Transaction Info | Block #23018212/Trx ca7f69806089356bdbb913e73fcc275ad452b6bf |
View Raw JSON Data
{
"block": 23018212,
"op": [
"account_update",
{
"account": "buddhasource",
"json_metadata": "{\"profile\":{\"profile_image\":\"https://cdn.steemitimages.com/DQmWKTjiypsojHPLJb1u3u18xmBWXjx4KYofH4Mmvf38fVJ/bull-wallpaper-4.jpg\"}}",
"memo_key": "STM7bV77qkD7scJShyXmnXffBRjE76M9etsdRDsPbRMfWoYJPyeTK"
}
],
"op_in_trx": 0,
"timestamp": "2018-06-04T04:59:42",
"trx_id": "ca7f69806089356bdbb913e73fcc275ad452b6bf",
"trx_in_block": 12,
"virtual_op": 0
}buddhasourcepublished a new post: bitcoin-legacy-vs-segwit-wallet-address-what-is-the-difference2018/06/04 04:58:36
buddhasourcepublished a new post: bitcoin-legacy-vs-segwit-wallet-address-what-is-the-difference
2018/06/04 04:58:36
| author | buddhasource |
| body | @@ -255,16 +255,17 @@ ich.%0A%0A## - + 1. So wh @@ -739,16 +739,17 @@ res.%0A%0A## - + 2. What @@ -1104,16 +1104,17 @@ ork.%0A%0A## - + 3. Is my @@ -1570,16 +1570,17 @@ yet.%0A%0A## + 4. Can i @@ -1714,16 +1714,17 @@ ble.%0A%0A## + 5. Does @@ -1906,16 +1906,17 @@ put.%0A%0A## - + 6. Is Si @@ -2048,16 +2048,17 @@ ble.%0A%0A## - + 7. What |
| json metadata | {"tags":["segwit","wallet","bitcoin","address"],"app":"steemit/0.1","format":"markdown","image":["https://cdn.steemitimages.com/DQme5nktKYvbVut1tWFhobxY9gEASGcGPjyvaSURfD7GR67/image.png"]} |
| parent author | |
| parent permlink | segwit |
| permlink | bitcoin-legacy-vs-segwit-wallet-address-what-is-the-difference |
| title | Bitcoin Legacy vs SegWit wallet address. What is the difference? |
| Transaction Info | Block #23018190/Trx 00915933aa00008dd4efd9c071be09030d711f46 |
View Raw JSON Data
{
"block": 23018190,
"op": [
"comment",
{
"author": "buddhasource",
"body": "@@ -255,16 +255,17 @@\n ich.%0A%0A##\n-\n \n+ \n 1. So wh\n@@ -739,16 +739,17 @@\n res.%0A%0A##\n-\n \n+ \n 2. What \n@@ -1104,16 +1104,17 @@\n ork.%0A%0A##\n-\n \n+ \n 3. Is my\n@@ -1570,16 +1570,17 @@\n yet.%0A%0A##\n+ \n 4. Can i\n@@ -1714,16 +1714,17 @@\n ble.%0A%0A##\n+ \n 5. Does \n@@ -1906,16 +1906,17 @@\n put.%0A%0A##\n-\n \n+ \n 6. Is Si\n@@ -2048,16 +2048,17 @@\n ble.%0A%0A##\n-\n \n+ \n 7. What \n",
"json_metadata": "{\"tags\":[\"segwit\",\"wallet\",\"bitcoin\",\"address\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\",\"image\":[\"https://cdn.steemitimages.com/DQme5nktKYvbVut1tWFhobxY9gEASGcGPjyvaSURfD7GR67/image.png\"]}",
"parent_author": "",
"parent_permlink": "segwit",
"permlink": "bitcoin-legacy-vs-segwit-wallet-address-what-is-the-difference",
"title": "Bitcoin Legacy vs SegWit wallet address. What is the difference?"
}
],
"op_in_trx": 0,
"timestamp": "2018-06-04T04:58:36",
"trx_id": "00915933aa00008dd4efd9c071be09030d711f46",
"trx_in_block": 32,
"virtual_op": 0
}buddhasourcepublished a new post: bitcoin-legacy-vs-segwit-wallet-address-what-is-the-difference2018/06/04 04:57:54
buddhasourcepublished a new post: bitcoin-legacy-vs-segwit-wallet-address-what-is-the-difference
2018/06/04 04:57:54
| author | buddhasource |
| body | @@ -1,8 +1,100 @@ +!%5B%5D(https://cdn.steemitimages.com/DQme5nktKYvbVut1tWFhobxY9gEASGcGPjyvaSURfD7GR67/image.png) I am try @@ -253,16 +253,18 @@ rich.%0A%0A +## 1. So wh @@ -736,16 +736,18 @@ tures.%0A%0A - +## 2. What @@ -1100,16 +1100,18 @@ twork.%0A%0A - +## 3. Is my @@ -1565,16 +1565,18 @@ t yet.%0A%0A - +## 4. Can i @@ -1708,16 +1708,18 @@ tible.%0A%0A - +## 5. Does @@ -1899,16 +1899,18 @@ utput.%0A%0A - +## 6. Is Si @@ -2040,16 +2040,18 @@ tible.%0A%0A - +## 7. What @@ -2232,16 +2232,17 @@ uestions - +, do ask |
| json metadata | {"tags":["segwit","wallet","bitcoin","address"],"app":"steemit/0.1","format":"markdown","image":["https://cdn.steemitimages.com/DQme5nktKYvbVut1tWFhobxY9gEASGcGPjyvaSURfD7GR67/image.png"]} |
| parent author | |
| parent permlink | segwit |
| permlink | bitcoin-legacy-vs-segwit-wallet-address-what-is-the-difference |
| title | Bitcoin Legacy vs SegWit wallet address. What is the difference? |
| Transaction Info | Block #23018176/Trx b8fe31c271cb2a0326e6a8c8341f82ed86293c56 |
View Raw JSON Data
{
"block": 23018176,
"op": [
"comment",
{
"author": "buddhasource",
"body": "@@ -1,8 +1,100 @@\n+!%5B%5D(https://cdn.steemitimages.com/DQme5nktKYvbVut1tWFhobxY9gEASGcGPjyvaSURfD7GR67/image.png)\n I am try\n@@ -253,16 +253,18 @@\n rich.%0A%0A\n+##\n 1. So wh\n@@ -736,16 +736,18 @@\n tures.%0A%0A\n-\n \n+##\n 2. What \n@@ -1100,16 +1100,18 @@\n twork.%0A%0A\n-\n \n+##\n 3. Is my\n@@ -1565,16 +1565,18 @@\n t yet.%0A%0A\n-\n \n+##\n 4. Can i\n@@ -1708,16 +1708,18 @@\n tible.%0A%0A\n-\n \n+##\n 5. Does \n@@ -1899,16 +1899,18 @@\n utput.%0A%0A\n-\n \n+##\n 6. Is Si\n@@ -2040,16 +2040,18 @@\n tible.%0A%0A\n-\n \n+##\n 7. What \n@@ -2232,16 +2232,17 @@\n uestions\n-\n \n+,\n do ask \n",
"json_metadata": "{\"tags\":[\"segwit\",\"wallet\",\"bitcoin\",\"address\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\",\"image\":[\"https://cdn.steemitimages.com/DQme5nktKYvbVut1tWFhobxY9gEASGcGPjyvaSURfD7GR67/image.png\"]}",
"parent_author": "",
"parent_permlink": "segwit",
"permlink": "bitcoin-legacy-vs-segwit-wallet-address-what-is-the-difference",
"title": "Bitcoin Legacy vs SegWit wallet address. What is the difference?"
}
],
"op_in_trx": 0,
"timestamp": "2018-06-04T04:57:54",
"trx_id": "b8fe31c271cb2a0326e6a8c8341f82ed86293c56",
"trx_in_block": 22,
"virtual_op": 0
}steemdelegated 18.119 SP to @buddhasource2018/06/02 10:20:42
steemdelegated 18.119 SP to @buddhasource
2018/06/02 10:20:42
| delegatee | buddhasource |
| delegator | steem |
| vesting shares | 29468.055595 VESTS |
| Transaction Info | Block #22967045/Trx 76de15f3ea503a189924524fb4247d7304380fd5 |
View Raw JSON Data
{
"block": 22967045,
"op": [
"delegate_vesting_shares",
{
"delegatee": "buddhasource",
"delegator": "steem",
"vesting_shares": "29468.055595 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2018-06-02T10:20:42",
"trx_id": "76de15f3ea503a189924524fb4247d7304380fd5",
"trx_in_block": 43,
"virtual_op": 0
}2018/06/02 06:50:48
2018/06/02 06:50:48
| author | cheetah |
| body | Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in: https://coin5s.com/content/bitcoin-legacy-vs-segwit-wallet-address-what-difference |
| json metadata | |
| parent author | buddhasource |
| parent permlink | bitcoin-legacy-vs-segwit-wallet-address-what-is-the-difference |
| permlink | cheetah-re-buddhasourcebitcoin-legacy-vs-segwit-wallet-address-what-is-the-difference |
| title | |
| Transaction Info | Block #22962851/Trx 15ad49c4ae544bcc0b6a83719437cf8677089a47 |
View Raw JSON Data
{
"block": 22962851,
"op": [
"comment",
{
"author": "cheetah",
"body": "Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in:\nhttps://coin5s.com/content/bitcoin-legacy-vs-segwit-wallet-address-what-difference",
"json_metadata": "",
"parent_author": "buddhasource",
"parent_permlink": "bitcoin-legacy-vs-segwit-wallet-address-what-is-the-difference",
"permlink": "cheetah-re-buddhasourcebitcoin-legacy-vs-segwit-wallet-address-what-is-the-difference",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2018-06-02T06:50:48",
"trx_id": "15ad49c4ae544bcc0b6a83719437cf8677089a47",
"trx_in_block": 16,
"virtual_op": 0
}2018/06/02 06:50:42
2018/06/02 06:50:42
| author | buddhasource |
| permlink | bitcoin-legacy-vs-segwit-wallet-address-what-is-the-difference |
| voter | cheetah |
| weight | 8 (0.08%) |
| Transaction Info | Block #22962849/Trx 48f4b69ff20369aa81b0973318ae6edf2dc4aa07 |
View Raw JSON Data
{
"block": 22962849,
"op": [
"vote",
{
"author": "buddhasource",
"permlink": "bitcoin-legacy-vs-segwit-wallet-address-what-is-the-difference",
"voter": "cheetah",
"weight": 8
}
],
"op_in_trx": 0,
"timestamp": "2018-06-02T06:50:42",
"trx_id": "48f4b69ff20369aa81b0973318ae6edf2dc4aa07",
"trx_in_block": 28,
"virtual_op": 0
}2018/06/02 06:50:39
2018/06/02 06:50:39
| author | buddhasource |
| permlink | bitcoin-legacy-vs-segwit-wallet-address-what-is-the-difference |
| voter | ax3 |
| weight | 100 (1.00%) |
| Transaction Info | Block #22962848/Trx a45dfb4fb38f0aa5c7a7512014cd5ea593e49acb |
View Raw JSON Data
{
"block": 22962848,
"op": [
"vote",
{
"author": "buddhasource",
"permlink": "bitcoin-legacy-vs-segwit-wallet-address-what-is-the-difference",
"voter": "ax3",
"weight": 100
}
],
"op_in_trx": 0,
"timestamp": "2018-06-02T06:50:39",
"trx_id": "a45dfb4fb38f0aa5c7a7512014cd5ea593e49acb",
"trx_in_block": 42,
"virtual_op": 0
}buddhasourcepublished a new post: bitcoin-legacy-vs-segwit-wallet-address-what-is-the-difference2018/06/02 06:50:30
buddhasourcepublished a new post: bitcoin-legacy-vs-segwit-wallet-address-what-is-the-difference
2018/06/02 06:50:30
| author | buddhasource |
| body | I am trying to help all those folks who are confused about this topic. You may be making money in Crypto world but it is good to know bit of tech that makes you rich. 1. So what is SegWit ? In a nutshell it is an improvement over the current bitcoin blockchain which reduces the size needed to store transactions in a block. This is done by removing certain signature with counting serialised witness data as one unit and core block data as four units. The name stands for Segregated Witness. Segregate means to separate, and Witnesses are the transaction signatures. Hence, Segregated Witness in short, means to separate transaction signatures. 2. What are the benefit of SegWit? The increased capacity to store more transactions means lower transaction fee, more transactions per block = faster transactions. In addition to that it would also fixes transaction malleability, an attack that lets a person change a Bitcoin transaction’s unique ID before the transaction is confirmed on the Bitcoin network. 3. Is my wallet address Legacy or SegWit? How to find out? If you have Legacy address then it means that you will be using addresses starting form 1… SegWit address means that you will be using addresses starting form 3… or bc1… (one is for P2SH nested SegWit and the other is for native SegWit). Note that 3… addresses are for P2SH addresses in general and are not just for SegWit. bc1… addresses are for SegWit specifically but not all wallets support it yet. 4. Can i transfer my BTC from Legacy to SegWit address as a normal BTC transfer ? Yes, SigWit is a soft fork and it is backward compatible. 5. Does it make a difference where i hold my bitcoins ? Yes. When you want to send money, transaction fees for spending a SegWit output will likely be lower from spending a legacy output. 6. Is SigWit on a different chain? No, there are no two chains. SegWit is activated on the Bitcoin blockchain. It is backward compatible. 7. What is SigWit2x ? SigWit2x stands for SigWit + 2X block size = 2MB. This fork was due to launch in 2017 but later cancelled as not many miners supported this. If you have more questions do ask them below, I will try to cover it above. |
| json metadata | {"tags":["segwit","wallet","bitcoin","address"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | segwit |
| permlink | bitcoin-legacy-vs-segwit-wallet-address-what-is-the-difference |
| title | Bitcoin Legacy vs SegWit wallet address. What is the difference? |
| Transaction Info | Block #22962845/Trx 9c2295fb1f6b14ae7b17275bf83741821aa23353 |
View Raw JSON Data
{
"block": 22962845,
"op": [
"comment",
{
"author": "buddhasource",
"body": "I am trying to help all those folks who are confused about this topic. You may be making money in Crypto world but it is good to know bit of tech that makes you rich.\n\n1. So what is SegWit ?\nIn a nutshell it is an improvement over the current bitcoin blockchain which reduces the size needed to store transactions in a block. This is done by removing certain signature with counting serialised witness data as one unit and core block data as four units.\n\nThe name stands for Segregated Witness. Segregate means to separate, and Witnesses are the transaction signatures. Hence, Segregated Witness in short, means to separate transaction signatures.\n\n2. What are the benefit of SegWit?\nThe increased capacity to store more transactions means lower transaction fee, more transactions per block = faster transactions. In addition to that it would also fixes transaction malleability, an attack that lets a person change a Bitcoin transaction’s unique ID before the transaction is confirmed on the Bitcoin network.\n\n3. Is my wallet address Legacy or SegWit? How to find out?\nIf you have Legacy address then it means that you will be using addresses starting form 1… SegWit address means that you will be using addresses starting form 3… or bc1… (one is for P2SH nested SegWit and the other is for native SegWit). Note that 3… addresses are for P2SH addresses in general and are not just for SegWit. bc1… addresses are for SegWit specifically but not all wallets support it yet.\n\n4. Can i transfer my BTC from Legacy to SegWit address as a normal BTC transfer ?\nYes, SigWit is a soft fork and it is backward compatible.\n\n5. Does it make a difference where i hold my bitcoins ?\nYes. When you want to send money, transaction fees for spending a SegWit output will likely be lower from spending a legacy output.\n\n6. Is SigWit on a different chain?\nNo, there are no two chains. SegWit is activated on the Bitcoin blockchain. It is backward compatible.\n\n7. What is SigWit2x ?\nSigWit2x stands for SigWit + 2X block size = 2MB. This fork was due to launch in 2017 but later cancelled as not many miners supported this.\n\nIf you have more questions do ask them below, I will try to cover it above.",
"json_metadata": "{\"tags\":[\"segwit\",\"wallet\",\"bitcoin\",\"address\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "segwit",
"permlink": "bitcoin-legacy-vs-segwit-wallet-address-what-is-the-difference",
"title": "Bitcoin Legacy vs SegWit wallet address. What is the difference?"
}
],
"op_in_trx": 0,
"timestamp": "2018-06-02T06:50:30",
"trx_id": "9c2295fb1f6b14ae7b17275bf83741821aa23353",
"trx_in_block": 31,
"virtual_op": 0
}steemdelegated 5.624 SP to @buddhasource2018/05/16 20:09:30
steemdelegated 5.624 SP to @buddhasource
2018/05/16 20:09:30
| delegatee | buddhasource |
| delegator | steem |
| vesting shares | 9146.021826 VESTS |
| Transaction Info | Block #22489691/Trx 9e02eaebb42e5fe81adefa5b2286d359cdef79e6 |
View Raw JSON Data
{
"block": 22489691,
"op": [
"delegate_vesting_shares",
{
"delegatee": "buddhasource",
"delegator": "steem",
"vesting_shares": "9146.021826 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2018-05-16T20:09:30",
"trx_id": "9e02eaebb42e5fe81adefa5b2286d359cdef79e6",
"trx_in_block": 18,
"virtual_op": 0
}steemdelegated 18.159 SP to @buddhasource2018/04/21 20:39:51
steemdelegated 18.159 SP to @buddhasource
2018/04/21 20:39:51
| delegatee | buddhasource |
| delegator | steem |
| vesting shares | 29533.990866 VESTS |
| Transaction Info | Block #21771085/Trx bc59733b5094d153006292a1c53ef7f0cce3bf97 |
View Raw JSON Data
{
"block": 21771085,
"op": [
"delegate_vesting_shares",
{
"delegatee": "buddhasource",
"delegator": "steem",
"vesting_shares": "29533.990866 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2018-04-21T20:39:51",
"trx_id": "bc59733b5094d153006292a1c53ef7f0cce3bf97",
"trx_in_block": 37,
"virtual_op": 0
}steemdelegated 18.285 SP to @buddhasource2017/12/12 22:23:12
steemdelegated 18.285 SP to @buddhasource
2017/12/12 22:23:12
| delegatee | buddhasource |
| delegator | steem |
| vesting shares | 29737.822918 VESTS |
| Transaction Info | Block #18032647/Trx 3220e2237fc8e4713af65216c6633017721a1a4e |
View Raw JSON Data
{
"block": 18032647,
"op": [
"delegate_vesting_shares",
{
"delegatee": "buddhasource",
"delegator": "steem",
"vesting_shares": "29737.822918 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2017-12-12T22:23:12",
"trx_id": "3220e2237fc8e4713af65216c6633017721a1a4e",
"trx_in_block": 20,
"virtual_op": 0
}siddharthgopiupvoted (100.00%) @buddhasource / the-making-of-tailored-posts2017/10/25 05:49:00
siddharthgopiupvoted (100.00%) @buddhasource / the-making-of-tailored-posts
2017/10/25 05:49:00
| author | buddhasource |
| permlink | the-making-of-tailored-posts |
| voter | siddharthgopi |
| weight | 10000 (100.00%) |
| Transaction Info | Block #16631035/Trx d2e361de053b6d1018641d238d1cd69aa6fa07ef |
View Raw JSON Data
{
"block": 16631035,
"op": [
"vote",
{
"author": "buddhasource",
"permlink": "the-making-of-tailored-posts",
"voter": "siddharthgopi",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-10-25T05:49:00",
"trx_id": "d2e361de053b6d1018641d238d1cd69aa6fa07ef",
"trx_in_block": 1,
"virtual_op": 0
}buddhasourceupvoted (100.00%) @siddharthgopi / how-i-deal-with-differences-in-opinion2017/10/25 02:48:48
buddhasourceupvoted (100.00%) @siddharthgopi / how-i-deal-with-differences-in-opinion
2017/10/25 02:48:48
| author | siddharthgopi |
| permlink | how-i-deal-with-differences-in-opinion |
| voter | buddhasource |
| weight | 10000 (100.00%) |
| Transaction Info | Block #16627431/Trx a4544b96b8969c92b4592904f23b9527706c4180 |
View Raw JSON Data
{
"block": 16627431,
"op": [
"vote",
{
"author": "siddharthgopi",
"permlink": "how-i-deal-with-differences-in-opinion",
"voter": "buddhasource",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-10-25T02:48:48",
"trx_id": "a4544b96b8969c92b4592904f23b9527706c4180",
"trx_in_block": 5,
"virtual_op": 0
}2017/10/24 05:49:03
2017/10/24 05:49:03
| author | buddhasource |
| body | Yes, that post is by me. |
| json metadata | {"tags":["product"],"app":"steemit/0.1"} |
| parent author | cheetah |
| parent permlink | cheetah-re-buddhasourcethe-making-of-tailored-posts |
| permlink | re-cheetah-cheetah-re-buddhasourcethe-making-of-tailored-posts-20171024t054904603z |
| title | |
| Transaction Info | Block #16602240/Trx c401a437181b8ba1753cbde46dcf57bbb3f5ee32 |
View Raw JSON Data
{
"block": 16602240,
"op": [
"comment",
{
"author": "buddhasource",
"body": "Yes, that post is by me.",
"json_metadata": "{\"tags\":[\"product\"],\"app\":\"steemit/0.1\"}",
"parent_author": "cheetah",
"parent_permlink": "cheetah-re-buddhasourcethe-making-of-tailored-posts",
"permlink": "re-cheetah-cheetah-re-buddhasourcethe-making-of-tailored-posts-20171024t054904603z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2017-10-24T05:49:03",
"trx_id": "c401a437181b8ba1753cbde46dcf57bbb3f5ee32",
"trx_in_block": 19,
"virtual_op": 0
}irbotupvoted (50.00%) @buddhasource / the-making-of-tailored-posts2017/10/24 04:11:00
irbotupvoted (50.00%) @buddhasource / the-making-of-tailored-posts
2017/10/24 04:11:00
| author | buddhasource |
| permlink | the-making-of-tailored-posts |
| voter | irbot |
| weight | 5000 (50.00%) |
| Transaction Info | Block #16600279/Trx 8f932baadf183a828d5cf898c3e8ec5f49bb4b2d |
View Raw JSON Data
{
"block": 16600279,
"op": [
"vote",
{
"author": "buddhasource",
"permlink": "the-making-of-tailored-posts",
"voter": "irbot",
"weight": 5000
}
],
"op_in_trx": 0,
"timestamp": "2017-10-24T04:11:00",
"trx_id": "8f932baadf183a828d5cf898c3e8ec5f49bb4b2d",
"trx_in_block": 6,
"virtual_op": 0
}squbeupvoted (1.00%) @buddhasource / the-making-of-tailored-posts2017/10/24 04:05:18
squbeupvoted (1.00%) @buddhasource / the-making-of-tailored-posts
2017/10/24 04:05:18
| author | buddhasource |
| permlink | the-making-of-tailored-posts |
| voter | sqube |
| weight | 100 (1.00%) |
| Transaction Info | Block #16600165/Trx 2e5e7c9b2ab04430694672692c685ea115fb7849 |
View Raw JSON Data
{
"block": 16600165,
"op": [
"vote",
{
"author": "buddhasource",
"permlink": "the-making-of-tailored-posts",
"voter": "sqube",
"weight": 100
}
],
"op_in_trx": 0,
"timestamp": "2017-10-24T04:05:18",
"trx_id": "2e5e7c9b2ab04430694672692c685ea115fb7849",
"trx_in_block": 24,
"virtual_op": 0
}2017/10/24 03:40:39
2017/10/24 03:40:39
| author | cheetah |
| body | Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in: https://blog.usejournal.com/the-making-of-tailored-posts-5004751f5ca0 |
| json metadata | |
| parent author | buddhasource |
| parent permlink | the-making-of-tailored-posts |
| permlink | cheetah-re-buddhasourcethe-making-of-tailored-posts |
| title | |
| Transaction Info | Block #16599672/Trx e363f1838636d26367c1eedb2658bfbe5069f70c |
View Raw JSON Data
{
"block": 16599672,
"op": [
"comment",
{
"author": "cheetah",
"body": "Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in:\nhttps://blog.usejournal.com/the-making-of-tailored-posts-5004751f5ca0",
"json_metadata": "",
"parent_author": "buddhasource",
"parent_permlink": "the-making-of-tailored-posts",
"permlink": "cheetah-re-buddhasourcethe-making-of-tailored-posts",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2017-10-24T03:40:39",
"trx_id": "e363f1838636d26367c1eedb2658bfbe5069f70c",
"trx_in_block": 2,
"virtual_op": 0
}cheetahupvoted (0.50%) @buddhasource / the-making-of-tailored-posts2017/10/24 03:40:33
cheetahupvoted (0.50%) @buddhasource / the-making-of-tailored-posts
2017/10/24 03:40:33
| author | buddhasource |
| permlink | the-making-of-tailored-posts |
| voter | cheetah |
| weight | 50 (0.50%) |
| Transaction Info | Block #16599670/Trx f5a6dca374032a6a19f6751a5c648c5d553024a7 |
View Raw JSON Data
{
"block": 16599670,
"op": [
"vote",
{
"author": "buddhasource",
"permlink": "the-making-of-tailored-posts",
"voter": "cheetah",
"weight": 50
}
],
"op_in_trx": 0,
"timestamp": "2017-10-24T03:40:33",
"trx_id": "f5a6dca374032a6a19f6751a5c648c5d553024a7",
"trx_in_block": 13,
"virtual_op": 0
}buddhasourcepublished a new post: the-making-of-tailored-posts2017/10/24 03:40:18
buddhasourcepublished a new post: the-making-of-tailored-posts
2017/10/24 03:40:18
| author | buddhasource |
| body | Best possible post for each network; smart and effortless.  Crowdfire is continuously and rapidly evolving into a smart, personalised assistant poised to give creators the growth their creation deserves. A few months back we announced the launch of our latest feature — Tailored Posts. It is the most polished product of our do-it-for-me strategy. Tailored Post solves the problem of sharing content on each network, smartly and effortlessly. It auto-tailors perfect social posts for each network based on what you are sharing. You can see how it works below:  When you share your content, it tailors for each network in the best possible way with a preview! Three years ago we launched Publish, a scheduling feature, quite like Buffer or HootSuite with a USP, “ auto-post at best time for maximum engagement ”. This took away a load of deciding when to post away from users and kept things quite simple to one button. Everybody loved it. Publish took care of the ‘When’ to post for our users. Digging deeper into Content Marketing. Content marketing is also What, Where, When and How to post. # **Coming to ‘What’ to post.** This past one year, we focused our energy on bringing post ideas that are — more relevant to the user, drive more traffic to his creations and keep his timeline engaged. We built daily Smart Posts — sharing content that you create (like videos, blog posts, products on your online store), recycled smartly and evenly distributed to drive more traffic. We also built article recommendations which are based on your twitter trends, topics you want to be famous for. Our users loved it, soon they drove more traffic to their creations, promoting their content multiple times, their timelines were not empty anymore, We saved them a lot of time. This contributed to a major shift in metrics for publishes from self compose to recommended articles. We are now in business of post ideas. ## *Answering the ‘How’ to post question.* While working on how to help creators share their content everywhere smartly, I felt the experience of how to post different content for each network was also broken in this world. >A perfect for each social network — was now our responsibility since we were also recommending content to our users. Any passably good social media manager would tell you that what works for marketing on one social network does not work for another. For example, you can get away with posting over a dozen times a day on Twitter, but the same’s not true of Facebook. Or if you create a video on Youtube, you could share it right away on Facebook but would have to create a shorter teaser version for Instagram. Also, some posts work well with multiple photos. So, a great social media manager would actually spend time tailoring a post for each of the different social media networks its audience is on. They will add in the correct hashtags, write up the perfect copy, create accompanying creatives that would garner the most engagement, schedule them for the right times and so on. But, if a business owner were to do it by themselves, they can’t-do the tailoring — which is, clearly, a full-time job. You see, when you are building your business from the ground up online, whether you are a YouTuber, an Etsy seller, a Blogger, a Freelancer contractor or any other form of one-man or few-men army, you have one goal and that is to build your business. You are focused on creating your next big video or crafting a trendy product for your store. This takes up almost all of your time— as it should. >Marketing your content should not be your full-time job. # Meet, Tailored Posts 🎯 An elegant solution to our problems. We imagined it be like a pro-active assistant which detects your latest YouTube upload and recommends you a smartly tailored social post for each network. It could have a teaser video for Instagram, a 140 (or 280 soon!) character tweet for Twitter and relevant hashtags to go with each post — all you have to do is tap on a button to send the post across all your networks. ## UX Challenges The vision of creating the perfect post for each network sounded great, but it was very challenging to keep things simple for our users. Our goal was to get this complex problem solved in least number of steps. The ideal Minimum Viable Flow for Tailored Posts would go something like this: >Crowdfire: “Siddharth, should I promote your latest video?” >Siddharth: “Yes. Thanks!” End of story. Beyond this one response, the user shouldn’t have to do anything and Crowdfire would promote that video by crafting the perfect post for each network and scheduling it for the right time. However, AI is not intelligent enough yet to understand every person and we needed an interim step where the user can preview how Crowdfire will do the promotion with an option to edit the posts Crowdfire created. Hence we adopted our UX philosophy as preview and share, this is different from review and share … which feels like more work each time. The difference is huge, one is more like a preview of what is going to happen while other is review of each action. This is unnecessary in most cases. Other challenge was also to consider giving user good control over his actions. So, here’s how it works right now:  Seems simple enough right? However, step 2 & 3 is where the magic and challenge lie. Every social network has it’s own posting and marketing strategy. So, how do you create perfectly tailored posts from one piece of content? And when you do, how do we present all the different crafted posts to the users, such that they can easily preview and approve? # First , The Design  It is fast, simple with fluidic gesture interactions and most important just one tap publish. Once we craft the posts for each network, previews for all the audience networks are easily accessible by a simple swipe gesture. This is a big step as we really wanted to avoid buttons / tab navigation. 1. The tailoring is clearly visible and tailoring is prioritised over manual editing. 1. If you notice the posts above, some are just link-shares with open graph cards and some are photo posts. This is based on the content you are sharing and the network you are sharing to. 1. The suggested method of scheduling a post (mostly 2 times this month) is highlighted while also allowing an access to the other scheduling options. 1. While users can visually distinguish which networks are already selected, it also encourages them to connect newer networks by showing a preview, with an overlay button to connect. As a result, we’ve seen an increase in the number of networks a user posts on. This answers the question ‘Where to post’ (Refer the first gif on top and check out Pinterest preview card). ## In The Preview Card:  Each card is designed to give the user an idea of how the post will look on different platform. This is important since we are composing the post for the user. Each platform has its own way of interpreting a post and we simulate all such cases. Typically each preview card has over 16 cases to handle like image post, text only, text with a link, video post, error states etc. # Under the Hood, the intelligence  Our tailoring logic happens on the server side and front end clients merely simulate post previews for each network based on the content params; views also adapt when the user edits a post. Much of the tailoring of each post depends on the source of the content. It matters if the content is a YouTube video, WordPress blog post, Tumblr post, SoundCloud track or an Etsy/Shopify product. So, how did we define the perfect post for each source? Let’s take YouTube. We started by documenting social media post styles of new and famous YouTubers, borrowing from their experience on how social posts should be. Turns out there are many ways of sharing a YouTube video. You could do an image post, where you share the thumbnail of the video and post it on Facebook and Twitter with a link, but in this case, the YouTube player is not embedded so it does not play within Facebook or Twitter. But, if you share it as a link with no accompanying image then it plays within the network. The posting strategy is different for Instagram as well, where posting a teaser video might get you more viewership to your YouTube video. The least you could do is create a thumbnail for Instagram and post. We studied the click-throughs from different post format through experiments until we arrived at ideal posts for each of the social networks. So, > *No. of experiments = Multiple content sources x Multiple social networks x Multiple types of posts* This has been a tediously manual task to begin with. We plan to automate this with machine learning for other networks & sources we integrate into Crowdfire, but for now we needed a logical start for our training models.  Medium, YouTube, Wordpress, RSS blogs, Etsy, Shopify and more are supported by Tailored Post. # The Tailoring We classified the tailoring of the posts: by type, by content, for growth, and by frequency. ## Tailoring by Type:  This is the first step in the tailoring process. This step defines how the post should look on the network it is being posted to. Essentially, we create a model of cases mapping to the source of the content. Major factors that decide tailoring here are the source of this content, the social networks it has to be posted on and the types of posts possible on that social network.  Example of Wordpress and Twitter tailoring rules, left are the cases for Wordpress blog post and right are the respective rules for Twitter posts based on the source. ## Tailoring by Content:  Next, we focus on the content itself. The objective here is to make the post interesting enough to attract clicks. This is an intensive process that took weeks of experimentation, iterations, and engineering to achieve. This is where we: * Create captions based on context (for eg: if it’s a new post, the tailored caption/tweet will usually start with “Best seller … ”, “My latest blog..”, “ Throwback ..” “Thursday posts..”, “This time last year..” etc.) * Tailor more descriptive captions for IG since it is not easy to post links there. If the source is blog, most of the blog post can be part of the description, this increases readership and chances of reading more on the blog. * Create an accompanying smart creative image for the post, if no image exists: say if a blog has no image then we create an image for Instagram and Pinterest with overlaying text. * Pick the right image to share from Etsy/Shopify, if that’s the content source. * Multilingual of the caption is also part of tailored by content. *Tailoring for growth*: We go on to tailor the post such that it would garner maximum engagement. This includes analysing it and including network-specific hashtags that would work best and increase discoverability. You will see a lot of improvement here in coming months. *Tailoring by frequency*: Here we decide how often this content should be shared across the different networks. For instance, if it is your new blog post, you would want to share it more often this month (once a week) while all your old evergreen content can be shared 2 times a month. This is a powerful feature which deserves a post by itself, I will share more about this next time. For now, you can read more about it here. And, there you have it! The perfectly tailored post is ready for the user’s purview. This five-step tailoring process and the segregation of the sources, networks, types of content, frequency and the final post makes this feature extremely agile and scaleable. I feel good that the product, design, and engineering came together to solve a problem elegantly. Tailored post has simplified the mechanics of publishing content everywhere. That was easy? Do share your thoughts and suggestions below and take a go at Tailored Posts by downloading our iOS or Android app. Don’t forget to connect your Medium blog on Crowdfire. To shoot the breeze with me about products or product designs, hit me up [@BuddhaSource ](http://twitter.com/buddhasource)— DMs are open. PS : Could not have done it without my awesome team, specially Abhishek on product design. |
| json metadata | {"tags":["product","management","ux","design","social"],"image":["https://steemitimages.com/DQmdr43kiTRcUor1L2mPq6s6LXv1mBhjy4CxVfnZu3caWJb/image.png","https://steemitimages.com/DQmYnRvceywf3uiH3KLvyB2ZiEEiWxwVhCQP1P4muodLrVn/Tailored-Post-compressed%202.gif","https://steemitimages.com/DQmXP52srVtDz5E7837UijHn2EiA1JX4yvU8hBfR9GCG5jG/image.png","https://steemitimages.com/DQmcxPrUaqKn3UmhjTU8bJUpeg5Sr3LgMtpcLP1fP6ipXFQ/Tailored-Post-compressed.gif","https://steemitimages.com/DQmR1MMXUbi3dc5BEDAvnrhiaWguZKRHxtuPDqX6Sripv3j/image.png","https://steemitimages.com/DQmZNmRu1yEvN3mFbKqxBt73PRUpGwjSdu4q5LHGjXP8zh7/image.png","https://steemitimages.com/DQmWyxJTfyE41Sn2djVd3EFYnybuFtFG8hj1dCZF2Yku2M6/image.png","https://steemitimages.com/DQmatYLcj9Bq8K3bmHVNZwJY4Yd36rRjZNFhEHw3WmMuqdJ/image.png","https://steemitimages.com/DQmSCVn3ib51k63RDbVPWkCp32fQNst1svuYZQLHDEjeonG/image.png","https://steemitimages.com/DQmaGf5RcUEkVRDC1awuPLXrj9iayou4FgwWUgvNN1BggXj/image.png"],"links":["http://twitter.com/buddhasource"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | product |
| permlink | the-making-of-tailored-posts |
| title | The Making of Tailored Posts |
| Transaction Info | Block #16599665/Trx ebcfbf90028016501260ef0c6280313e23bd6bae |
View Raw JSON Data
{
"block": 16599665,
"op": [
"comment",
{
"author": "buddhasource",
"body": "Best possible post for each network; smart and effortless.\n\n\n\nCrowdfire is continuously and rapidly evolving into a smart, personalised assistant poised to give creators the growth their creation deserves. A few months back we announced the launch of our latest feature — Tailored Posts. It is the most polished product of our do-it-for-me strategy.\n\nTailored Post solves the problem of sharing content on each network, smartly and effortlessly. It auto-tailors perfect social posts for each network based on what you are sharing.\nYou can see how it works below: \n\n\nWhen you share your content, it tailors for each network in the best possible way with a preview!\n\nThree years ago we launched Publish, a scheduling feature, quite like Buffer or HootSuite with a USP, “ auto-post at best time for maximum engagement ”. This took away a load of deciding when to post away from users and kept things quite simple to one button. Everybody loved it. Publish took care of the ‘When’ to post for our users. Digging deeper into Content Marketing.\nContent marketing is also What, Where, When and How to post.\n\n# **Coming to ‘What’ to post.**\n\nThis past one year, we focused our energy on bringing post ideas that are — more relevant to the user, drive more traffic to his creations and keep his timeline engaged. We built daily Smart Posts — sharing content that you create (like videos, blog posts, products on your online store), recycled smartly and evenly distributed to drive more traffic. We also built article recommendations which are based on your twitter trends, topics you want to be famous for. Our users loved it, soon they drove more traffic to their creations, promoting their content multiple times, their timelines were not empty anymore, We saved them a lot of time. This contributed to a major shift in metrics for publishes from self compose to recommended articles. We are now in business of post ideas.\n\n## *Answering the ‘How’ to post question.*\nWhile working on how to help creators share their content everywhere smartly, I felt the experience of how to post different content for each network was also broken in this world.\n\n>A perfect for each social network — was now our responsibility since we were also recommending content to our users.\n\nAny passably good social media manager would tell you that what works for marketing on one social network does not work for another. For example, you can get away with posting over a dozen times a day on Twitter, but the same’s not true of Facebook. Or if you create a video on Youtube, you could share it right away on Facebook but would have to create a shorter teaser version for Instagram. Also, some posts work well with multiple photos.\n\nSo, a great social media manager would actually spend time tailoring a post for each of the different social media networks its audience is on. They will add in the correct hashtags, write up the perfect copy, create accompanying creatives that would garner the most engagement, schedule them for the right times and so on. But, if a business owner were to do it by themselves, they can’t-do the tailoring — which is, clearly, a full-time job.\nYou see, when you are building your business from the ground up online, whether you are a YouTuber, an Etsy seller, a Blogger, a Freelancer contractor or any other form of one-man or few-men army, you have one goal and that is to build your business. You are focused on creating your next big video or crafting a trendy product for your store. This takes up almost all of your time— as it should.\n\n>Marketing your content should not be your full-time job.\n\n# Meet, Tailored Posts 🎯\nAn elegant solution to our problems.\n\nWe imagined it be like a pro-active assistant which detects your latest YouTube upload and recommends you a smartly tailored social post for each network. It could have a teaser video for Instagram, a 140 (or 280 soon!) character tweet for Twitter and relevant hashtags to go with each post — all you have to do is tap on a button to send the post across all your networks.\n\n## UX Challenges\nThe vision of creating the perfect post for each network sounded great, but it was very challenging to keep things simple for our users.\nOur goal was to get this complex problem solved in least number of steps. The ideal Minimum Viable Flow for Tailored Posts would go something like this:\n\n>Crowdfire: “Siddharth, should I promote your latest video?”\n>Siddharth: “Yes. Thanks!”\n\nEnd of story. Beyond this one response, the user shouldn’t have to do anything and Crowdfire would promote that video by crafting the perfect post for each network and scheduling it for the right time.\n\nHowever, AI is not intelligent enough yet to understand every person and we needed an interim step where the user can preview how Crowdfire will do the promotion with an option to edit the posts Crowdfire created.\n\nHence we adopted our UX philosophy as preview and share, this is different from review and share … which feels like more work each time. The difference is huge, one is more like a preview of what is going to happen while other is review of each action. This is unnecessary in most cases. Other challenge was also to consider giving user good control over his actions.\n\nSo, here’s how it works right now:\n\n\nSeems simple enough right? However, step 2 & 3 is where the magic and challenge lie.\nEvery social network has it’s own posting and marketing strategy. So, how do you create perfectly tailored posts from one piece of content?\nAnd when you do, how do we present all the different crafted posts to the users, such that they can easily preview and approve?\n\n# First , The Design\n\nIt is fast, simple with fluidic gesture interactions and most important just one tap publish.\n\nOnce we craft the posts for each network, previews for all the audience networks are easily accessible by a simple swipe gesture. This is a big step as we really wanted to avoid buttons / tab navigation.\n\n1. The tailoring is clearly visible and tailoring is prioritised over manual editing.\n\n1. If you notice the posts above, some are just link-shares with open graph cards and some are photo posts. This is based on the content you are sharing and the network you are sharing to.\n\n1. The suggested method of scheduling a post (mostly 2 times this month) is highlighted while also allowing an access to the other scheduling options.\n\n1. While users can visually distinguish which networks are already selected, it also encourages them to connect newer networks by showing a preview, with an overlay button to connect. As a result, we’ve seen an increase in the number of networks a user posts on. This answers the question ‘Where to post’ (Refer the first gif on top and check out Pinterest preview card).\n\n## In The Preview Card:\n\n\nEach card is designed to give the user an idea of how the post will look on different platform. This is important since we are composing the post for the user. Each platform has its own way of interpreting a post and we simulate all such cases. Typically each preview card has over 16 cases to handle like image post, text only, text with a link, video post, error states etc.\n\n# Under the Hood, the intelligence\n\n\nOur tailoring logic happens on the server side and front end clients merely simulate post previews for each network based on the content params; views also adapt when the user edits a post. Much of the tailoring of each post depends on the source of the content. It matters if the content is a YouTube video, WordPress blog post, Tumblr post, SoundCloud track or an Etsy/Shopify product.\n\nSo, how did we define the perfect post for each source?\nLet’s take YouTube. We started by documenting social media post styles of new and famous YouTubers, borrowing from their experience on how social posts should be.\n\nTurns out there are many ways of sharing a YouTube video. You could do an image post, where you share the thumbnail of the video and post it on Facebook and Twitter with a link, but in this case, the YouTube player is not embedded so it does not play within Facebook or Twitter. But, if you share it as a link with no accompanying image then it plays within the network.\nThe posting strategy is different for Instagram as well, where posting a teaser video might get you more viewership to your YouTube video. The least you could do is create a thumbnail for Instagram and post.\nWe studied the click-throughs from different post format through experiments until we arrived at ideal posts for each of the social networks.\nSo,\n> *No. of experiments = Multiple content sources x Multiple social networks x Multiple types of posts*\n\nThis has been a tediously manual task to begin with. We plan to automate this with machine learning for other networks & sources we integrate into Crowdfire, but for now we needed a logical start for our training models.\n\nMedium, YouTube, Wordpress, RSS blogs, Etsy, Shopify and more are supported by Tailored Post.\n\n# The Tailoring\nWe classified the tailoring of the posts: by type, by content, for growth, and by frequency.\n## Tailoring by Type:\n\nThis is the first step in the tailoring process. This step defines how the post should look on the network it is being posted to. Essentially, we create a model of cases mapping to the source of the content.\nMajor factors that decide tailoring here are the source of this content, the social networks it has to be posted on and the types of posts possible on that social network.\n\nExample of Wordpress and Twitter tailoring rules, left are the cases for Wordpress blog post and right are the respective rules for Twitter posts based on the source.\n\n## Tailoring by Content:\n\n\nNext, we focus on the content itself. The objective here is to make the post interesting enough to attract clicks. This is an intensive process that took weeks of experimentation, iterations, and engineering to achieve.\nThis is where we:\n* Create captions based on context (for eg: if it’s a new post, the tailored caption/tweet will usually start with “Best seller … ”, “My latest blog..”, “ Throwback ..” “Thursday posts..”, “This time last year..” etc.)\n* Tailor more descriptive captions for IG since it is not easy to post links there. If the source is blog, most of the blog post can be part of the description, this increases readership and chances of reading more on the blog.\n* Create an accompanying smart creative image for the post, if no image exists: say if a blog has no image then we create an image for Instagram and Pinterest with overlaying text.\n* Pick the right image to share from Etsy/Shopify, if that’s the content source.\n* Multilingual of the caption is also part of tailored by content.\n\n*Tailoring for growth*: We go on to tailor the post such that it would garner maximum engagement. This includes analysing it and including network-specific hashtags that would work best and increase discoverability. You will see a lot of improvement here in coming months.\n\n*Tailoring by frequency*: Here we decide how often this content should be shared across the different networks. For instance, if it is your new blog post, you would want to share it more often this month (once a week) while all your old evergreen content can be shared 2 times a month. This is a powerful feature which deserves a post by itself, I will share more about this next time. For now, you can read more about it here.\n\nAnd, there you have it! The perfectly tailored post is ready for the user’s purview.\nThis five-step tailoring process and the segregation of the sources, networks, types of content, frequency and the final post makes this feature extremely agile and scaleable. I feel good that the product, design, and engineering came together to solve a problem elegantly.\n\nTailored post has simplified the mechanics of publishing content everywhere.\nThat was easy? Do share your thoughts and suggestions below and take a go at Tailored Posts by downloading our iOS or Android app. Don’t forget to connect your Medium blog on Crowdfire.\nTo shoot the breeze with me about products or product designs, hit me up [@BuddhaSource ](http://twitter.com/buddhasource)— DMs are open.\n\nPS : Could not have done it without my awesome team, specially Abhishek on product design.",
"json_metadata": "{\"tags\":[\"product\",\"management\",\"ux\",\"design\",\"social\"],\"image\":[\"https://steemitimages.com/DQmdr43kiTRcUor1L2mPq6s6LXv1mBhjy4CxVfnZu3caWJb/image.png\",\"https://steemitimages.com/DQmYnRvceywf3uiH3KLvyB2ZiEEiWxwVhCQP1P4muodLrVn/Tailored-Post-compressed%202.gif\",\"https://steemitimages.com/DQmXP52srVtDz5E7837UijHn2EiA1JX4yvU8hBfR9GCG5jG/image.png\",\"https://steemitimages.com/DQmcxPrUaqKn3UmhjTU8bJUpeg5Sr3LgMtpcLP1fP6ipXFQ/Tailored-Post-compressed.gif\",\"https://steemitimages.com/DQmR1MMXUbi3dc5BEDAvnrhiaWguZKRHxtuPDqX6Sripv3j/image.png\",\"https://steemitimages.com/DQmZNmRu1yEvN3mFbKqxBt73PRUpGwjSdu4q5LHGjXP8zh7/image.png\",\"https://steemitimages.com/DQmWyxJTfyE41Sn2djVd3EFYnybuFtFG8hj1dCZF2Yku2M6/image.png\",\"https://steemitimages.com/DQmatYLcj9Bq8K3bmHVNZwJY4Yd36rRjZNFhEHw3WmMuqdJ/image.png\",\"https://steemitimages.com/DQmSCVn3ib51k63RDbVPWkCp32fQNst1svuYZQLHDEjeonG/image.png\",\"https://steemitimages.com/DQmaGf5RcUEkVRDC1awuPLXrj9iayou4FgwWUgvNN1BggXj/image.png\"],\"links\":[\"http://twitter.com/buddhasource\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "product",
"permlink": "the-making-of-tailored-posts",
"title": "The Making of Tailored Posts"
}
],
"op_in_trx": 0,
"timestamp": "2017-10-24T03:40:18",
"trx_id": "ebcfbf90028016501260ef0c6280313e23bd6bae",
"trx_in_block": 18,
"virtual_op": 0
}steemcreated a new account: @buddhasource2017/10/24 03:08:15
steemcreated a new account: @buddhasource
2017/10/24 03:08:15
| active | {"account_auths":[],"key_auths":[["STM79b76pgLcNb3cy8YzFmdJzrPsDUZTw3WQoCxPxjkvaoiNWkaF8",1]],"weight_threshold":1} |
| creator | steem |
| delegation | 57000.000000 VESTS |
| extensions | [] |
| fee | 0.500 STEEM |
| json metadata | |
| memo key | STM7bV77qkD7scJShyXmnXffBRjE76M9etsdRDsPbRMfWoYJPyeTK |
| new account name | buddhasource |
| owner | {"account_auths":[],"key_auths":[["STM5GUKYgufEMufw8qUCRwNQrKw5fTsV6xwNCtqvSud4zrGjFLhri",1]],"weight_threshold":1} |
| posting | {"account_auths":[],"key_auths":[["STM8LKoGzHMUgwRFhS4zYVMvgTAenuRNtZpXAN1VPv3f9vbrb6FP6",1]],"weight_threshold":1} |
| Transaction Info | Block #16599024/Trx 7f7ced041c3c4e7ba3d5db9c61ffaaae779b42fd |
View Raw JSON Data
{
"block": 16599024,
"op": [
"account_create_with_delegation",
{
"active": {
"account_auths": [],
"key_auths": [
[
"STM79b76pgLcNb3cy8YzFmdJzrPsDUZTw3WQoCxPxjkvaoiNWkaF8",
1
]
],
"weight_threshold": 1
},
"creator": "steem",
"delegation": "57000.000000 VESTS",
"extensions": [],
"fee": "0.500 STEEM",
"json_metadata": "",
"memo_key": "STM7bV77qkD7scJShyXmnXffBRjE76M9etsdRDsPbRMfWoYJPyeTK",
"new_account_name": "buddhasource",
"owner": {
"account_auths": [],
"key_auths": [
[
"STM5GUKYgufEMufw8qUCRwNQrKw5fTsV6xwNCtqvSud4zrGjFLhri",
1
]
],
"weight_threshold": 1
},
"posting": {
"account_auths": [],
"key_auths": [
[
"STM8LKoGzHMUgwRFhS4zYVMvgTAenuRNtZpXAN1VPv3f9vbrb6FP6",
1
]
],
"weight_threshold": 1
}
}
],
"op_in_trx": 0,
"timestamp": "2017-10-24T03:08:15",
"trx_id": "7f7ced041c3c4e7ba3d5db9c61ffaaae779b42fd",
"trx_in_block": 24,
"virtual_op": 0
}Manabar
Voting Power100.00%
Downvote Power100.00%
Resource Credits100.00%
Reputation Progress0.00%
{
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779056544
},
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779056544
},
"rc_account": {
"account": "buddhasource",
"max_rc": "10164408779",
"max_rc_creation_adjustment": {
"amount": "2020748973",
"nai": "@@000000037",
"precision": 6
},
"rc_manabar": {
"current_mana": "10164408779",
"last_update_time": 1779056544
}
}
}Account Metadata
| POSTING JSON METADATA | |
| profile | {"profile_image":"https://cdn.steemitimages.com/DQmWKTjiypsojHPLJb1u3u18xmBWXjx4KYofH4Mmvf38fVJ/bull-wallpaper-4.jpg"} |
| JSON METADATA | |
| profile | {"profile_image":"https://cdn.steemitimages.com/DQmWKTjiypsojHPLJb1u3u18xmBWXjx4KYofH4Mmvf38fVJ/bull-wallpaper-4.jpg"} |
{
"posting_json_metadata": {
"profile": {
"profile_image": "https://cdn.steemitimages.com/DQmWKTjiypsojHPLJb1u3u18xmBWXjx4KYofH4Mmvf38fVJ/bull-wallpaper-4.jpg"
}
},
"json_metadata": {
"profile": {
"profile_image": "https://cdn.steemitimages.com/DQmWKTjiypsojHPLJb1u3u18xmBWXjx4KYofH4Mmvf38fVJ/bull-wallpaper-4.jpg"
}
}
}Auth Keys
Owner
Single Signature
Public Keys
STM5GUKYgufEMufw8qUCRwNQrKw5fTsV6xwNCtqvSud4zrGjFLhri1/1
Active
Single Signature
Public Keys
STM79b76pgLcNb3cy8YzFmdJzrPsDUZTw3WQoCxPxjkvaoiNWkaF81/1
Posting
Single Signature
Public Keys
STM8LKoGzHMUgwRFhS4zYVMvgTAenuRNtZpXAN1VPv3f9vbrb6FP61/1
Memo
STM7bV77qkD7scJShyXmnXffBRjE76M9etsdRDsPbRMfWoYJPyeTK
{
"owner": {
"account_auths": [],
"key_auths": [
[
"STM5GUKYgufEMufw8qUCRwNQrKw5fTsV6xwNCtqvSud4zrGjFLhri",
1
]
],
"weight_threshold": 1
},
"active": {
"account_auths": [],
"key_auths": [
[
"STM79b76pgLcNb3cy8YzFmdJzrPsDUZTw3WQoCxPxjkvaoiNWkaF8",
1
]
],
"weight_threshold": 1
},
"posting": {
"account_auths": [],
"key_auths": [
[
"STM8LKoGzHMUgwRFhS4zYVMvgTAenuRNtZpXAN1VPv3f9vbrb6FP6",
1
]
],
"weight_threshold": 1
},
"memo": "STM7bV77qkD7scJShyXmnXffBRjE76M9etsdRDsPbRMfWoYJPyeTK"
}Witness Votes
0 / 30
No active witness votes.
[]