VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS0.00%
Net Worth
0.026USD
STEEM
0.000STEEM
SBD
0.040SBD
Effective Power
5.007SP
├── Own SP
0.125SP
└── Incoming DelegationsDeleg
+4.882SP
Detailed Balance
| STEEM | ||
| balance | 0.000STEEM | STEEM |
| market_balance | 0.000STEEM | STEEM |
| savings_balance | 0.000STEEM | STEEM |
| reward_steem_balance | 0.000STEEM | STEEM |
| STEEM POWER | ||
| Own SP | 0.125SP | SP |
| Delegated Out | 0.000SP | SP |
| Delegation In | 4.882SP | SP |
| Effective Power | 5.007SP | SP |
| Reward SP (pending) | 0.010SP | 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.040SBD | SBD |
{
"balance": "0.000 STEEM",
"savings_balance": "0.000 STEEM",
"reward_steem_balance": "0.000 STEEM",
"vesting_shares": "203.849575 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "7939.810231 VESTS",
"sbd_balance": "0.000 SBD",
"savings_sbd_balance": "0.000 SBD",
"reward_sbd_balance": "0.040 SBD",
"conversions": []
}Account Info
| name | turingsafe |
| id | 938484 |
| rank | 1,367,929 |
| reputation | 234740919 |
| created | 2018-04-12T06:56:12 |
| recovery_account | steem |
| proxy | None |
| post_count | 7 |
| comment_count | 0 |
| lifetime_vote_count | 0 |
| witnesses_voted_for | 0 |
| last_post | 2018-05-21T12:27:33 |
| last_root_post | 2018-05-21T12:27:33 |
| last_vote_time | 2018-05-21T12:27:42 |
| proxied_vsf_votes | 0, 0, 0, 0 |
| can_vote | 1 |
| voting_power | 0 |
| delayed_votes | 0 |
| balance | 0.000 STEEM |
| savings_balance | 0.000 STEEM |
| sbd_balance | 0.000 SBD |
| savings_sbd_balance | 0.000 SBD |
| vesting_shares | 203.849575 VESTS |
| delegated_vesting_shares | 0.000000 VESTS |
| received_vesting_shares | 7939.810231 VESTS |
| reward_vesting_balance | 20.363710 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-04-30T13:06:33 |
| 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": [
[
"STM7dXwndDe18F4jYA35JphQSFGySnh8r4tvJodauFWjwmYVvy2Yt",
1
]
],
"weight_threshold": 1
},
"balance": "0.000 STEEM",
"can_vote": true,
"comment_count": 0,
"created": "2018-04-12T06:56:12",
"curation_rewards": 0,
"delegated_vesting_shares": "0.000000 VESTS",
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779090192
},
"guest_bloggers": [],
"id": 938484,
"json_metadata": "{\"profile\":{\"name\":\"Turing Labs\",\"website\":\"https://www.turinglabs.io\"}}",
"last_account_recovery": "1970-01-01T00:00:00",
"last_account_update": "2018-04-30T13:06:33",
"last_owner_update": "1970-01-01T00:00:00",
"last_post": "2018-05-21T12:27:33",
"last_root_post": "2018-05-21T12:27:33",
"last_vote_time": "2018-05-21T12:27:42",
"lifetime_vote_count": 0,
"market_history": [],
"memo_key": "STM5JCVTuQpALTQ56RZZRFYSgT5SXv28m8t8j1nkTsBweRJxJq5Ku",
"mined": false,
"name": "turingsafe",
"next_vesting_withdrawal": "1969-12-31T23:59:59",
"other_history": [],
"owner": {
"account_auths": [],
"key_auths": [
[
"STM79naTYxEmqZboyDfo84uQKhxeYaexbPN5KrUrrUKXLbhk5e777",
1
]
],
"weight_threshold": 1
},
"pending_claimed_accounts": 0,
"post_bandwidth": 0,
"post_count": 7,
"post_history": [],
"posting": {
"account_auths": [],
"key_auths": [
[
"STM74HpaPCCzgpUBp7N226bJfXee3oQmFyWkkhZ7fwvY7CWzoR8SJ",
1
]
],
"weight_threshold": 1
},
"posting_json_metadata": "{\"profile\":{\"name\":\"Turing Labs\",\"website\":\"https://www.turinglabs.io\"}}",
"posting_rewards": 20,
"proxied_vsf_votes": [
0,
0,
0,
0
],
"proxy": "",
"received_vesting_shares": "7939.810231 VESTS",
"recovery_account": "steem",
"reputation": 234740919,
"reset_account": "null",
"reward_sbd_balance": "0.040 SBD",
"reward_steem_balance": "0.000 STEEM",
"reward_vesting_balance": "20.363710 VESTS",
"reward_vesting_steem": "0.010 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": "203.849575 VESTS",
"vesting_withdraw_rate": "0.000000 VESTS",
"vote_history": [],
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779090192
},
"voting_power": 0,
"withdraw_routes": 0,
"withdrawn": 0,
"witness_votes": [],
"witnesses_voted_for": 0,
"rank": 1367929
}Withdraw Routes
| Incoming | Outgoing |
|---|---|
Empty | Empty |
{
"incoming": [],
"outgoing": []
}From Date
To Date
steemdelegated 4.882 SP to @turingsafe2026/05/18 07:43:12
steemdelegated 4.882 SP to @turingsafe
2026/05/18 07:43:12
| delegatee | turingsafe |
| delegator | steem |
| vesting shares | 7939.810231 VESTS |
| Transaction Info | Block #106152371/Trx dbbc8a84b240a88873f6ea9d37d3dd8bbc440424 |
View Raw JSON Data
{
"block": 106152371,
"op": [
"delegate_vesting_shares",
{
"delegatee": "turingsafe",
"delegator": "steem",
"vesting_shares": "7939.810231 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2026-05-18T07:43:12",
"trx_id": "dbbc8a84b240a88873f6ea9d37d3dd8bbc440424",
"trx_in_block": 1,
"virtual_op": 0
}steemdelegated 3.214 SP to @turingsafe2026/05/13 10:06:21
steemdelegated 3.214 SP to @turingsafe
2026/05/13 10:06:21
| delegatee | turingsafe |
| delegator | steem |
| vesting shares | 5227.599826 VESTS |
| Transaction Info | Block #106011942/Trx 6b32d6d46af0d3957d0189eb3509a7c64f42d78a |
View Raw JSON Data
{
"block": 106011942,
"op": [
"delegate_vesting_shares",
{
"delegatee": "turingsafe",
"delegator": "steem",
"vesting_shares": "5227.599826 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2026-05-13T10:06:21",
"trx_id": "6b32d6d46af0d3957d0189eb3509a7c64f42d78a",
"trx_in_block": 0,
"virtual_op": 0
}steemdelegated 4.890 SP to @turingsafe2026/04/26 06:53:06
steemdelegated 4.890 SP to @turingsafe
2026/04/26 06:53:06
| delegatee | turingsafe |
| delegator | steem |
| vesting shares | 7952.325987 VESTS |
| Transaction Info | Block #105519819/Trx 946b6a3deff650573ff532fd8fd203b70b3934f6 |
View Raw JSON Data
{
"block": 105519819,
"op": [
"delegate_vesting_shares",
{
"delegatee": "turingsafe",
"delegator": "steem",
"vesting_shares": "7952.325987 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2026-04-26T06:53:06",
"trx_id": "946b6a3deff650573ff532fd8fd203b70b3934f6",
"trx_in_block": 1,
"virtual_op": 0
}steemdelegated 3.240 SP to @turingsafe2026/01/24 03:51:03
steemdelegated 3.240 SP to @turingsafe
2026/01/24 03:51:03
| delegatee | turingsafe |
| delegator | steem |
| vesting shares | 5269.146645 VESTS |
| Transaction Info | Block #102875820/Trx a39a4976cdf7113ce7ee9386dead482377a54960 |
View Raw JSON Data
{
"block": 102875820,
"op": [
"delegate_vesting_shares",
{
"delegatee": "turingsafe",
"delegator": "steem",
"vesting_shares": "5269.146645 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2026-01-24T03:51:03",
"trx_id": "a39a4976cdf7113ce7ee9386dead482377a54960",
"trx_in_block": 0,
"virtual_op": 0
}steemdelegated 3.341 SP to @turingsafe2024/12/17 22:59:42
steemdelegated 3.341 SP to @turingsafe
2024/12/17 22:59:42
| delegatee | turingsafe |
| delegator | steem |
| vesting shares | 5433.365842 VESTS |
| Transaction Info | Block #91322013/Trx b4a619805e5b5dee7e4b2f90e03a986e97c7948e |
View Raw JSON Data
{
"block": 91322013,
"op": [
"delegate_vesting_shares",
{
"delegatee": "turingsafe",
"delegator": "steem",
"vesting_shares": "5433.365842 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2024-12-17T22:59:42",
"trx_id": "b4a619805e5b5dee7e4b2f90e03a986e97c7948e",
"trx_in_block": 5,
"virtual_op": 0
}steemdelegated 3.445 SP to @turingsafe2023/11/14 14:37:57
steemdelegated 3.445 SP to @turingsafe
2023/11/14 14:37:57
| delegatee | turingsafe |
| delegator | steem |
| vesting shares | 5602.499374 VESTS |
| Transaction Info | Block #79876093/Trx c8882fc63f3439918030793c9b52c22c131839ff |
View Raw JSON Data
{
"block": 79876093,
"op": [
"delegate_vesting_shares",
{
"delegatee": "turingsafe",
"delegator": "steem",
"vesting_shares": "5602.499374 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2023-11-14T14:37:57",
"trx_id": "c8882fc63f3439918030793c9b52c22c131839ff",
"trx_in_block": 5,
"virtual_op": 0
}steemdelegated 5.251 SP to @turingsafe2023/09/22 12:03:57
steemdelegated 5.251 SP to @turingsafe
2023/09/22 12:03:57
| delegatee | turingsafe |
| delegator | steem |
| vesting shares | 8539.408160 VESTS |
| Transaction Info | Block #78364866/Trx 9b6c0fdc2873be53ffe3accddf63c9dcad60a403 |
View Raw JSON Data
{
"block": 78364866,
"op": [
"delegate_vesting_shares",
{
"delegatee": "turingsafe",
"delegator": "steem",
"vesting_shares": "8539.408160 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2023-09-22T12:03:57",
"trx_id": "9b6c0fdc2873be53ffe3accddf63c9dcad60a403",
"trx_in_block": 6,
"virtual_op": 0
}steemdelegated 5.387 SP to @turingsafe2022/11/03 19:20:36
steemdelegated 5.387 SP to @turingsafe
2022/11/03 19:20:36
| delegatee | turingsafe |
| delegator | steem |
| vesting shares | 8761.459598 VESTS |
| Transaction Info | Block #69122386/Trx 752ef719e0e8b913bc55428b9d55b8fad43573d5 |
View Raw JSON Data
{
"block": 69122386,
"op": [
"delegate_vesting_shares",
{
"delegatee": "turingsafe",
"delegator": "steem",
"vesting_shares": "8761.459598 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2022-11-03T19:20:36",
"trx_id": "752ef719e0e8b913bc55428b9d55b8fad43573d5",
"trx_in_block": 0,
"virtual_op": 0
}steemdelegated 5.522 SP to @turingsafe2022/01/18 00:24:09
steemdelegated 5.522 SP to @turingsafe
2022/01/18 00:24:09
| delegatee | turingsafe |
| delegator | steem |
| vesting shares | 8981.567199 VESTS |
| Transaction Info | Block #60825470/Trx 0711b8158c3623e269c7d0cd64d44f179efb1fb6 |
View Raw JSON Data
{
"block": 60825470,
"op": [
"delegate_vesting_shares",
{
"delegatee": "turingsafe",
"delegator": "steem",
"vesting_shares": "8981.567199 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2022-01-18T00:24:09",
"trx_id": "0711b8158c3623e269c7d0cd64d44f179efb1fb6",
"trx_in_block": 3,
"virtual_op": 0
}steemdelegated 5.636 SP to @turingsafe2021/06/14 07:31:33
steemdelegated 5.636 SP to @turingsafe
2021/06/14 07:31:33
| delegatee | turingsafe |
| delegator | steem |
| vesting shares | 9165.761487 VESTS |
| Transaction Info | Block #54615718/Trx aa21ffc451574e5df9ca4d10db800979a37db528 |
View Raw JSON Data
{
"block": 54615718,
"op": [
"delegate_vesting_shares",
{
"delegatee": "turingsafe",
"delegator": "steem",
"vesting_shares": "9165.761487 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2021-06-14T07:31:33",
"trx_id": "aa21ffc451574e5df9ca4d10db800979a37db528",
"trx_in_block": 1,
"virtual_op": 0
}steemdelegated 5.751 SP to @turingsafe2020/12/11 17:42:30
steemdelegated 5.751 SP to @turingsafe
2020/12/11 17:42:30
| delegatee | turingsafe |
| delegator | steem |
| vesting shares | 9353.183461 VESTS |
| Transaction Info | Block #49362936/Trx 00f70a56829a9748a7eb0c6662aeaeda8385c6db |
View Raw JSON Data
{
"block": 49362936,
"op": [
"delegate_vesting_shares",
{
"delegatee": "turingsafe",
"delegator": "steem",
"vesting_shares": "9353.183461 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-12-11T17:42:30",
"trx_id": "00f70a56829a9748a7eb0c6662aeaeda8385c6db",
"trx_in_block": 9,
"virtual_op": 0
}steemdelegated 1.176 SP to @turingsafe2020/12/06 11:17:51
steemdelegated 1.176 SP to @turingsafe
2020/12/06 11:17:51
| delegatee | turingsafe |
| delegator | steem |
| vesting shares | 1912.543513 VESTS |
| Transaction Info | Block #49214454/Trx d37392106d90848e85c9bad24f8612ad9f178f98 |
View Raw JSON Data
{
"block": 49214454,
"op": [
"delegate_vesting_shares",
{
"delegatee": "turingsafe",
"delegator": "steem",
"vesting_shares": "1912.543513 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-12-06T11:17:51",
"trx_id": "d37392106d90848e85c9bad24f8612ad9f178f98",
"trx_in_block": 0,
"virtual_op": 0
}steemdelegated 5.755 SP to @turingsafe2020/12/05 21:20:24
steemdelegated 5.755 SP to @turingsafe
2020/12/05 21:20:24
| delegatee | turingsafe |
| delegator | steem |
| vesting shares | 9359.391315 VESTS |
| Transaction Info | Block #49198021/Trx 108df10c4b015f3eb6914827e036468681e75a90 |
View Raw JSON Data
{
"block": 49198021,
"op": [
"delegate_vesting_shares",
{
"delegatee": "turingsafe",
"delegator": "steem",
"vesting_shares": "9359.391315 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-12-05T21:20:24",
"trx_id": "108df10c4b015f3eb6914827e036468681e75a90",
"trx_in_block": 2,
"virtual_op": 0
}steemdelegated 1.181 SP to @turingsafe2020/11/03 05:16:00
steemdelegated 1.181 SP to @turingsafe
2020/11/03 05:16:00
| delegatee | turingsafe |
| delegator | steem |
| vesting shares | 1920.017158 VESTS |
| Transaction Info | Block #48273846/Trx ff58c731bc9d5d7883c4efa8ff174b481ec4df24 |
View Raw JSON Data
{
"block": 48273846,
"op": [
"delegate_vesting_shares",
{
"delegatee": "turingsafe",
"delegator": "steem",
"vesting_shares": "1920.017158 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-11-03T05:16:00",
"trx_id": "ff58c731bc9d5d7883c4efa8ff174b481ec4df24",
"trx_in_block": 1,
"virtual_op": 0
}steemdelegated 5.879 SP to @turingsafe2020/05/09 12:22:09
steemdelegated 5.879 SP to @turingsafe
2020/05/09 12:22:09
| delegatee | turingsafe |
| delegator | steem |
| vesting shares | 9562.196674 VESTS |
| Transaction Info | Block #43224802/Trx 6bd0f23a4f0fd8a346e42eacbc06f8d6e74e0a26 |
View Raw JSON Data
{
"block": 43224802,
"op": [
"delegate_vesting_shares",
{
"delegatee": "turingsafe",
"delegator": "steem",
"vesting_shares": "9562.196674 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-05-09T12:22:09",
"trx_id": "6bd0f23a4f0fd8a346e42eacbc06f8d6e74e0a26",
"trx_in_block": 13,
"virtual_op": 0
}steemdelegated 1.201 SP to @turingsafe2020/05/08 16:57:42
steemdelegated 1.201 SP to @turingsafe
2020/05/08 16:57:42
| delegatee | turingsafe |
| delegator | steem |
| vesting shares | 1953.311140 VESTS |
| Transaction Info | Block #43202063/Trx 081c68bcc66cb92f73c747e6b360ab69fec19edb |
View Raw JSON Data
{
"block": 43202063,
"op": [
"delegate_vesting_shares",
{
"delegatee": "turingsafe",
"delegator": "steem",
"vesting_shares": "1953.311140 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-05-08T16:57:42",
"trx_id": "081c68bcc66cb92f73c747e6b360ab69fec19edb",
"trx_in_block": 10,
"virtual_op": 0
}steemdelegated 5.977 SP to @turingsafe2019/08/05 18:15:30
steemdelegated 5.977 SP to @turingsafe
2019/08/05 18:15:30
| delegatee | turingsafe |
| delegator | steem |
| vesting shares | 9720.744436 VESTS |
| Transaction Info | Block #35294051/Trx 92ebfa74a1efd9a3cd1539dd48aaec06b9153393 |
View Raw JSON Data
{
"block": 35294051,
"op": [
"delegate_vesting_shares",
{
"delegatee": "turingsafe",
"delegator": "steem",
"vesting_shares": "9720.744436 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2019-08-05T18:15:30",
"trx_id": "92ebfa74a1efd9a3cd1539dd48aaec06b9153393",
"trx_in_block": 27,
"virtual_op": 0
}2019/04/12 08:10:45
2019/04/12 08:10:45
| author | steemitboard |
| body | Congratulations @turingsafe! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@turingsafe/birthday1.png</td><td>Happy Birthday! - You are on the Steem blockchain for 1 year!</td></tr></table> <sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@turingsafe) and compare to others on the [Steem Ranking](http://steemitboard.com/ranking/index.php?name=turingsafe)_</sub> ###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| parent author | turingsafe |
| parent permlink | lessons-we-learnt-from-failed-icos |
| permlink | steemitboard-notify-turingsafe-20190412t081044000z |
| title | |
| Transaction Info | Block #31975112/Trx c4921d54c6a97dfd39707cfe4e229b3f1b48e010 |
View Raw JSON Data
{
"block": 31975112,
"op": [
"comment",
{
"author": "steemitboard",
"body": "Congratulations @turingsafe! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@turingsafe/birthday1.png</td><td>Happy Birthday! - You are on the Steem blockchain for 1 year!</td></tr></table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@turingsafe) and compare to others on the [Steem Ranking](http://steemitboard.com/ranking/index.php?name=turingsafe)_</sub>\n\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}",
"parent_author": "turingsafe",
"parent_permlink": "lessons-we-learnt-from-failed-icos",
"permlink": "steemitboard-notify-turingsafe-20190412t081044000z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2019-04-12T08:10:45",
"trx_id": "c4921d54c6a97dfd39707cfe4e229b3f1b48e010",
"trx_in_block": 11,
"virtual_op": 0
}zionkimupvoted (100.00%) @turingsafe / guidelines-for-writing-a-compelling-white-paper2018/12/12 11:46:21
zionkimupvoted (100.00%) @turingsafe / guidelines-for-writing-a-compelling-white-paper
2018/12/12 11:46:21
| author | turingsafe |
| permlink | guidelines-for-writing-a-compelling-white-paper |
| voter | zionkim |
| weight | 10000 (100.00%) |
| Transaction Info | Block #28497652/Trx eff8c8321c15e51bac8225e6a21facda4c1ef8e4 |
View Raw JSON Data
{
"block": 28497652,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "guidelines-for-writing-a-compelling-white-paper",
"voter": "zionkim",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-12-12T11:46:21",
"trx_id": "eff8c8321c15e51bac8225e6a21facda4c1ef8e4",
"trx_in_block": 0,
"virtual_op": 0
}steemdelegated 6.099 SP to @turingsafe2018/08/20 12:32:00
steemdelegated 6.099 SP to @turingsafe
2018/08/20 12:32:00
| delegatee | turingsafe |
| delegator | steem |
| vesting shares | 9919.250285 VESTS |
| Transaction Info | Block #25233098/Trx e0582c5473a51181026feeb1ddf1c8f5e867c27f |
View Raw JSON Data
{
"block": 25233098,
"op": [
"delegate_vesting_shares",
{
"delegatee": "turingsafe",
"delegator": "steem",
"vesting_shares": "9919.250285 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2018-08-20T12:32:00",
"trx_id": "e0582c5473a51181026feeb1ddf1c8f5e867c27f",
"trx_in_block": 37,
"virtual_op": 0
}steemdelegated 18.551 SP to @turingsafe2018/08/17 06:18:27
steemdelegated 18.551 SP to @turingsafe
2018/08/17 06:18:27
| delegatee | turingsafe |
| delegator | steem |
| vesting shares | 30170.803227 VESTS |
| Transaction Info | Block #25139264/Trx 48aff384d1a237c6eb634d135970c6d0f16374e4 |
View Raw JSON Data
{
"block": 25139264,
"op": [
"delegate_vesting_shares",
{
"delegatee": "turingsafe",
"delegator": "steem",
"vesting_shares": "30170.803227 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2018-08-17T06:18:27",
"trx_id": "48aff384d1a237c6eb634d135970c6d0f16374e4",
"trx_in_block": 22,
"virtual_op": 0
}sensationupvoted (100.00%) @turingsafe / lessons-we-learnt-from-failed-icos2018/05/21 14:57:12
sensationupvoted (100.00%) @turingsafe / lessons-we-learnt-from-failed-icos
2018/05/21 14:57:12
| author | turingsafe |
| permlink | lessons-we-learnt-from-failed-icos |
| voter | sensation |
| weight | 10000 (100.00%) |
| Transaction Info | Block #22627422/Trx 95c601c988c4cec886e64d56e4114a982df50609 |
View Raw JSON Data
{
"block": 22627422,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "lessons-we-learnt-from-failed-icos",
"voter": "sensation",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-05-21T14:57:12",
"trx_id": "95c601c988c4cec886e64d56e4114a982df50609",
"trx_in_block": 9,
"virtual_op": 0
}2018/05/21 12:30:15
2018/05/21 12:30:15
| author | freeesta |
| body | Excellent article Thanks for the information! I subscribed to you. I hope you subscribe to me. |
| json metadata | {"tags":["ico"],"app":"steemit/0.1"} |
| parent author | turingsafe |
| parent permlink | lessons-we-learnt-from-failed-icos |
| permlink | re-turingsafe-lessons-we-learnt-from-failed-icos-20180521t123015019z |
| title | |
| Transaction Info | Block #22624483/Trx 62ab053e563cbe9c5962f8e630b7acb123ba2c98 |
View Raw JSON Data
{
"block": 22624483,
"op": [
"comment",
{
"author": "freeesta",
"body": "Excellent article Thanks for the information! I subscribed to you. I hope you subscribe to me.",
"json_metadata": "{\"tags\":[\"ico\"],\"app\":\"steemit/0.1\"}",
"parent_author": "turingsafe",
"parent_permlink": "lessons-we-learnt-from-failed-icos",
"permlink": "re-turingsafe-lessons-we-learnt-from-failed-icos-20180521t123015019z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2018-05-21T12:30:15",
"trx_id": "62ab053e563cbe9c5962f8e630b7acb123ba2c98",
"trx_in_block": 49,
"virtual_op": 0
}freeestaupvoted (100.00%) @turingsafe / lessons-we-learnt-from-failed-icos2018/05/21 12:30:12
freeestaupvoted (100.00%) @turingsafe / lessons-we-learnt-from-failed-icos
2018/05/21 12:30:12
| author | turingsafe |
| permlink | lessons-we-learnt-from-failed-icos |
| voter | freeesta |
| weight | 10000 (100.00%) |
| Transaction Info | Block #22624482/Trx e0b6beeb4604b00a676b0f799394697492cc4d5d |
View Raw JSON Data
{
"block": 22624482,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "lessons-we-learnt-from-failed-icos",
"voter": "freeesta",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-05-21T12:30:12",
"trx_id": "e0b6beeb4604b00a676b0f799394697492cc4d5d",
"trx_in_block": 42,
"virtual_op": 0
}turingsafeupvoted (100.00%) @turingsafe / lessons-we-learnt-from-failed-icos2018/05/21 12:27:42
turingsafeupvoted (100.00%) @turingsafe / lessons-we-learnt-from-failed-icos
2018/05/21 12:27:42
| author | turingsafe |
| permlink | lessons-we-learnt-from-failed-icos |
| voter | turingsafe |
| weight | 10000 (100.00%) |
| Transaction Info | Block #22624432/Trx 903429c8bd7970c2be1495333e2eda1746a6645a |
View Raw JSON Data
{
"block": 22624432,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "lessons-we-learnt-from-failed-icos",
"voter": "turingsafe",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-05-21T12:27:42",
"trx_id": "903429c8bd7970c2be1495333e2eda1746a6645a",
"trx_in_block": 42,
"virtual_op": 0
}turingsafepublished a new post: lessons-we-learnt-from-failed-icos2018/05/21 12:27:33
turingsafepublished a new post: lessons-we-learnt-from-failed-icos
2018/05/21 12:27:33
| author | turingsafe |
| body |  The world of ICOs, in the absence of authoritative institutionalization and comprehensive regulatory mechanisms, is complicated and chaotic. It is not difficult to ruin a promising ICO project with a small mistake, and lose the faith of investors forever. If yours is a serious Blockchain-powered project which has the potential to make a considerable positive impact on any industry, you would want to make sure that your ICO goes right, and that you do not repeat the mistakes of those before you. Here are the things we learnt from the following failed ICOs in the past - -- <b>DAO</b> - The DAO hack is one of the most notorious examples of failures in the history of ICOs. Decentralised Autonomous Organisation or the DAO was meant to be a decentralized investment fund where all investors could vote on which companies to fund. The weight of the vote was equivalent to the contribution of the investor. The DAO had already raised 12M Ether, which was equivalent to over $150 MM at that time. Then, a hacker discovered a vulnerability in the Smart Contract code, and he exploited it to extract $50 MM worth of Ether from the DAO. The DAO attack reveals that security often tends to be neglected in ICOs. Smart Contracts are in the process of fundamentally changing the way the world conducts transactions, and it is imperative that any project, before deploying its Smart Contracts on the Blockchain, should get it audited from experienced developers in the Blockchain community to ensure that they are free of any bugs. -- <b>Tezos</b> - Tezos, an on chain governance protocol project, made headlines in the crypto-verse twice - first, when it raised a whopping $232 MM in its ICO, and the second time, when conflicts between founders Arthur and Kathleen Breitman and Johann Gevers became a serious issue and jeopardized the project. Further, the project has been condemned for selling unregistered securities, misrepresentation of how the funds would be spent, misrepresentations of when the network would be active, false advertising under state laws, unfair competition and deceptive trade practices. The complications continue, and there is little clarity on how the project will shape up post-ICO. While the Tezos ICO surely underscores the importance of ensuring legal compliance, and structuring, marketing and executing the token sale properly, the Tezos debacle teaches investors that is important to do one’s due diligence to ensure that the ICO team is absolutely serious about their project. A way of finding this out is if the team has a prototype in place. A minimum viable product (MVP) gives some assurance of the team’s technical capabilities, and their intention of making a full-fledged working product, as described in the White Paper. -- <b>Enigma</b> - Enigma, an investment platform, became the target of hackers because the team members failed to ensure password security of their accounts. Guy Zyskind, the CEO of Enigma, had apparently used a password, which had previously been used on a compromised platform, for his GitHub account. Hackers got hold of that password, gained control over the company’s website domain, slack channel and mailing lists, and end up taking away $500,000 from their investors. A minor negligence on the part of the CEO caused the collapse of the Enigma ICO, and it is a lesson for upcoming ICOs that poor security is any ICOs nemesis. It is a good practice to keep changing the passwords of ICO accounts, and ensuring their strength by making them complex. Small measures like these can make a significant difference to the success of your ICO, as the Enigma incident underlines. -- <b>PayCoin</b> - PayCoin rose to fame in the crypto-verse with the claim that they were going to create a new breed of cryptocurrency - at least, that’s what their White Paper suggested. However, when they launched their ICO, coin that came out was another generic altcoin. However, when the team failed to keep its promises, including the $20 pay floor, and the hype around the project soon fizzled out. In fact, GAW Miners and Paycoin Head Josh Garza pleaded guilty to operating a Ponzi scheme. What is evident from this case is that if your product is bad, no amount of marketing and PR can turn it around and make it worthy of raising millions of dollars. Therefore, it very important to give attention to conceptualizing your product meticulously, and developing it in a manner that it adds value to the industry it is catering to. For ICO participants, it foregrounds the importance of doing one’s research and reviewing the ICO for its technical and economic feasibility, because many ICOs, which make far-fetched projections about “revolutionizing” any industry, are actually Ponzi schemes. -- <b>CoinDash</b> - CoinDash is another ICO which suffered because it failed to take adequate measures in securing its ICO. The hacker replaced the Ethereum address the project was using to receive funds, with a fraudulent address, resulting in the loss of $7 MM to the ICO. Recently, the hacker reportedly returned 20,000 ETH to the company’s wallet. Hackers are always a step ahead of our security measures. Therefore, it is essential to ensure that you keep yourself updated on best practices for ensuring the security of your ICO, and leave no stone unturned in fortifying it against attacks. For ensuring website security, a good practice would ensure rigorous external penetration testing of the website done and buying all similar sounding domain names, so that hackers are not able to exploit your community with a fake website. -- <b>Munchee</b> - Munchee was an ICO which sprung out of existing business idea about rewarding restaurant reviewers with MUN tokens when they published an honest restaurant review with photos. The reviewers could redeem these tokens at a number of restaurants within the Munchee ecosystem. The ICO tumbled when its marketing efforts took the wrong turn, and make the utility token look like a security token, which would fetch investors profits. The SEC intervened and terminated the ICO on the grounds that MUN was an unregistered security. Munchee’s failure is an example of an ICO gone wrong because of improper messaging in its marketing campaign. The Howey Test’s rubric considers any token which shows the tendency to profit its investors, as a security. Munchee was a company operating in the US, and it bungled up because of non-compliance with SEC’s terms. Thus, there are two key takeaways from the Munchee case - first, ensure complete compliance with the regulations of the country you are operating in, and second, ensure that the messaging of your marketing campaigns should be focused on how the token will add value with its utility to the industry it is being implemented in. Refrain from talking about the profits it will bring to those buying the tokens as an investment. -- <b>JesusCoin</b> - No offense to Jesus, but this one had to be on the list. This is a coin “decentralizing Jesus on the Blockchain”. The coin offers “outsourced forgiveness” and “record transaction speed between you and God's son”. With the CEO of the company being Jesus Christ himself, no doubt it is a hoax. What’s even more surprising is out of nearly 1500 coins listed on CoinMarketCap, it ranks at 816 presently, and has managed a market cap of nearly $1.5 MM. There are a number of other ridiculous coins in the market such as the PrayerCoin - a coin for decentralizing religion, Sand Coin - a coin for ordering high-quality sand, Exotown - a reptile breeding program, etc. The point here is that not everything needs a blockchain. There are many projects out there in the market which have tried to include Blockchain in their poorly-made project blueprints, just because it has become a buzzword associated with raising money, and they want to use ICOs as a scheme for making easy money. Investors, beware. Do not support such projects at any cost because they bring a bad name to the cryptocurrency industry. For ICO developers behind such projects - regulatory authorities across the world are getting more stringent with their evaluation of ICOs. Your efforts to swindle people will be thwarted. -- <b>Spacebit</b> - Spacebit was an ambitious project which had the attention of crypto community back in 2014. Labeling itself as the “first decentralized space company” its aim was to launch “nano-satellites” into space and provide the world with a globally accessible blockchain, and thus allow bitcoin cold storage and help unbanked regions access financial services. The project, after creating a lot of buzz in the crypto-verse, died in 2015 when the community stopped hearing from the team altogether. Apparently, the team had started working on another project, BlockVerify, and had directed its attention entirely towards the new project. The reason why the team did not develop a prototype could perhaps be because of the project’s technological infeasibility at that time or the team’s lack of experience at fulfilling the idea. So, the project was scrapped after all the marketing efforts. From this instance, we can gather that it is absolutely important to evaluate a project’s technical feasibility before building an ICO around it. Get in touch with experienced developers in the crypto-community and consult with them if you can. If not, do your own research thoroughly and conceptualize a product which you and your team understand in and out. Last but not the least, as we have advised before, at least start developing a prototype before launching your idea in the market. We regularly update this space with articles on ICO best practices for different aspects and components of ICOs. Stay tuned! |
| json metadata | {"tags":["ico","blockchain","ethereum","organization","token"],"image":["https://steemitimages.com/DQmY27R4uCzodD5AP6d5jR1GBqdGombhYxHYwEGAkokYXjK/Fail_ico.jpg"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | ico |
| permlink | lessons-we-learnt-from-failed-icos |
| title | Lessons we learnt from failed ICOs |
| Transaction Info | Block #22624429/Trx e62e3ea5bc6bc708aaee79733f82864cd585c46b |
View Raw JSON Data
{
"block": 22624429,
"op": [
"comment",
{
"author": "turingsafe",
"body": "\n\nThe world of ICOs, in the absence of authoritative institutionalization and comprehensive regulatory mechanisms, is complicated and chaotic. It is not difficult to ruin a promising ICO project with a small mistake, and lose the faith of investors forever. If yours is a serious Blockchain-powered project which has the potential to make a considerable positive impact on any industry, you would want to make sure that your ICO goes right, and that you do not repeat the mistakes of those before you.\n\nHere are the things we learnt from the following failed ICOs in the past - \n\n-- <b>DAO</b> - The DAO hack is one of the most notorious examples of failures in the history of ICOs. Decentralised Autonomous Organisation or the DAO was meant to be a decentralized investment fund where all investors could vote on which companies to fund. The weight of the vote was equivalent to the contribution of the investor. The DAO had already raised 12M Ether, which was equivalent to over $150 MM at that time. Then, a hacker discovered a vulnerability in the Smart Contract code, and he exploited it to extract $50 MM worth of Ether from the DAO. \n\nThe DAO attack reveals that security often tends to be neglected in ICOs. Smart Contracts are in the process of fundamentally changing the way the world conducts transactions, and it is imperative that any project, before deploying its Smart Contracts on the Blockchain, should get it audited from experienced developers in the Blockchain community to ensure that they are free of any bugs. \n\n-- <b>Tezos</b> - Tezos, an on chain governance protocol project, made headlines in the crypto-verse twice - first, when it raised a whopping $232 MM in its ICO, and the second time, when conflicts between founders Arthur and Kathleen Breitman and Johann Gevers became a serious issue and jeopardized the project. Further, the project has been condemned for selling unregistered securities, misrepresentation of how the funds would be spent, misrepresentations of when the network would be active, false advertising under state laws, unfair competition and deceptive trade practices. The complications continue, and there is little clarity on how the project will shape up post-ICO. \n\nWhile the Tezos ICO surely underscores the importance of ensuring legal compliance, and structuring, marketing and executing the token sale properly, the Tezos debacle teaches investors that is important to do one’s due diligence to ensure that the ICO team is absolutely serious about their project. A way of finding this out is if the team has a prototype in place. A minimum viable product (MVP) gives some assurance of the team’s technical capabilities, and their intention of making a full-fledged working product, as described in the White Paper.\n\n\n\n-- <b>Enigma</b> - Enigma, an investment platform, became the target of hackers because the team members failed to ensure password security of their accounts. Guy Zyskind, the CEO of Enigma, had apparently used a password, which had previously been used on a compromised platform, for his GitHub account. Hackers got hold of that password, gained control over the company’s website domain, slack channel and mailing lists, and end up taking away $500,000 from their investors.\n\nA minor negligence on the part of the CEO caused the collapse of the Enigma ICO, and it is a lesson for upcoming ICOs that poor security is any ICOs nemesis. It is a good practice to keep changing the passwords of ICO accounts, and ensuring their strength by making them complex. Small measures like these can make a significant difference to the success of your ICO, as the Enigma incident underlines. \n\n-- <b>PayCoin</b> - PayCoin rose to fame in the crypto-verse with the claim that they were going to create a new breed of cryptocurrency - at least, that’s what their White Paper suggested. However, when they launched their ICO, coin that came out was another generic altcoin. However, when the team failed to keep its promises, including the $20 pay floor, and the hype around the project soon fizzled out. In fact, GAW Miners and Paycoin Head Josh Garza pleaded guilty to operating a Ponzi scheme. \n\n\nWhat is evident from this case is that if your product is bad, no amount of marketing and PR can turn it around and make it worthy of raising millions of dollars. Therefore, it very important to give attention to conceptualizing your product meticulously, and developing it in a manner that it adds value to the industry it is catering to. For ICO participants, it foregrounds the importance of doing one’s research and reviewing the ICO for its technical and economic feasibility, because many ICOs, which make far-fetched projections about “revolutionizing” any industry, are actually Ponzi schemes. \n\n-- <b>CoinDash</b> - CoinDash is another ICO which suffered because it failed to take adequate measures in securing its ICO. The hacker replaced the Ethereum address the project was using to receive funds, with a fraudulent address, resulting in the loss of $7 MM to the ICO. Recently, the hacker reportedly returned 20,000 ETH to the company’s wallet. \n\nHackers are always a step ahead of our security measures. Therefore, it is essential to ensure that you keep yourself updated on best practices for ensuring the security of your ICO, and leave no stone unturned in fortifying it against attacks. For ensuring website security, a good practice would ensure rigorous external penetration testing of the website done and buying all similar sounding domain names, so that hackers are not able to exploit your community with a fake website. \n\n-- <b>Munchee</b> - Munchee was an ICO which sprung out of existing business idea about rewarding restaurant reviewers with MUN tokens when they published an honest restaurant review with photos. The reviewers could redeem these tokens at a number of restaurants within the Munchee ecosystem. The ICO tumbled when its marketing efforts took the wrong turn, and make the utility token look like a security token, which would fetch investors profits. The SEC intervened and terminated the ICO on the grounds that MUN was an unregistered security.\n\nMunchee’s failure is an example of an ICO gone wrong because of improper messaging in its marketing campaign. The Howey Test’s rubric considers any token which shows the tendency to profit its investors, as a security. Munchee was a company operating in the US, and it bungled up because of non-compliance with SEC’s terms. Thus, there are two key takeaways from the Munchee case - first, ensure complete compliance with the regulations of the country you are operating in, and second, ensure that the messaging of your marketing campaigns should be focused on how the token will add value with its utility to the industry it is being implemented in. Refrain from talking about the profits it will bring to those buying the tokens as an investment. \n\n-- <b>JesusCoin</b> - No offense to Jesus, but this one had to be on the list. This is a coin “decentralizing Jesus on the Blockchain”. The coin offers “outsourced forgiveness” and “record transaction speed between you and God's son”. With the CEO of the company being Jesus Christ himself, no doubt it is a hoax. What’s even more surprising is out of nearly 1500 coins listed on CoinMarketCap, it ranks at 816 presently, and has managed a market cap of nearly $1.5 MM. There are a number of other ridiculous coins in the market such as the PrayerCoin - a coin for decentralizing religion, Sand Coin - a coin for ordering high-quality sand, Exotown - a reptile breeding program, etc.\n\nThe point here is that not everything needs a blockchain. There are many projects out there in the market which have tried to include Blockchain in their poorly-made project blueprints, just because it has become a buzzword associated with raising money, and they want to use ICOs as a scheme for making easy money. Investors, beware. Do not support such projects at any cost because they bring a bad name to the cryptocurrency industry. For ICO developers behind such projects - regulatory authorities across the world are getting more stringent with their evaluation of ICOs. Your efforts to swindle people will be thwarted. \n\n-- <b>Spacebit</b> - Spacebit was an ambitious project which had the attention of crypto community back in 2014. Labeling itself as the “first decentralized space company” its aim was to launch “nano-satellites” into space and provide the world with a globally accessible blockchain, and thus allow bitcoin cold storage and help unbanked regions access financial services. The project, after creating a lot of buzz in the crypto-verse, died in 2015 when the community stopped hearing from the team altogether. Apparently, the team had started working on another project, BlockVerify, and had directed its attention entirely towards the new project. \n\nThe reason why the team did not develop a prototype could perhaps be because of the project’s technological infeasibility at that time or the team’s lack of experience at fulfilling the idea. So, the project was scrapped after all the marketing efforts. From this instance, we can gather that it is absolutely important to evaluate a project’s technical feasibility before building an ICO around it. Get in touch with experienced developers in the crypto-community and consult with them if you can. If not, do your own research thoroughly and conceptualize a product which you and your team understand in and out. Last but not the least, as we have advised before, at least start developing a prototype before launching your idea in the market. \n\nWe regularly update this space with articles on ICO best practices for different aspects and components of ICOs. Stay tuned!",
"json_metadata": "{\"tags\":[\"ico\",\"blockchain\",\"ethereum\",\"organization\",\"token\"],\"image\":[\"https://steemitimages.com/DQmY27R4uCzodD5AP6d5jR1GBqdGombhYxHYwEGAkokYXjK/Fail_ico.jpg\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "ico",
"permlink": "lessons-we-learnt-from-failed-icos",
"title": "Lessons we learnt from failed ICOs"
}
],
"op_in_trx": 0,
"timestamp": "2018-05-21T12:27:33",
"trx_id": "e62e3ea5bc6bc708aaee79733f82864cd585c46b",
"trx_in_block": 56,
"virtual_op": 0
}turingsafepublished a new post: guidelines-for-writing-a-compelling-white-paper2018/05/18 13:27:30
turingsafepublished a new post: guidelines-for-writing-a-compelling-white-paper
2018/05/18 13:27:30
| author | turingsafe |
| body |  A White Paper is a crucial marketing document for any ICO; it plays a significant role in communicating your Blockchain-based business to the world, convincing them of its potential, and motivating them to contribute towards its development. Thus, the document must be carefully planned and drafted, keeping in the mind the target audience, which is usually the crypto-community looking for the next big Blockchain project to invest in, and the stakeholders of the industry that the Blockchain project is aiming to revolutionize. A White Paper must find a sweet spot between being a technical research paper, a business report, and a buzzword salad. Here are a few things you need to keep in mind while drafting a powerful White Paper - <b>Have a compelling abstract</b> - An abstract outlines the problem you are aiming and the solution being offered by you in a few lines. An abstract is necessary because it helps readers decide if they want to read the entire White Paper or not. If an abstract is interesting enough if it will pique the interest of the audience, and chances are that they will read the whole White Paper. So, spend some time drafting the abstract and make sure that it doesn’t extend over a page. <b>Establish the Problem & Solution clearly</b> - The magnitude of the problem is important to establish. If the problem that you are trying to solve is substantial and affects a large number of people, chances are that your project will be able to a gather great support because more people will be able to relate to it and appreciate your taking the pains to develop a Blockchain-based solution for it. Once the problem has been established, the solution must follow. The solution must be practically viable with the technology available at that time because investors would want to invest in an idea, which actually has the potential to become a full-fledged product, be put into use, and earn revenues in the foreseeable future. <b>Cite all numbers</b> - Citations help build the credibility of White Paper. When you say that your revolutionary product is going to impact the $XX Bn industry, you must be able to reference the $XX Bn figure. The more the citations the better it is, because it shows that - You know your industry well. You did your homework before writing the White Paper. Your data is not made up; your figures are not imaginary. Your calculations around the target market size, projected revenues, etc. are based on authentic data. Wikipedia is not a go-to place for data. Refer to research papers, journals, business reports, articles & books from experts in the field for obtaining reliable information. <b>Include good graphics</b> - While graphics add to the aesthetic appeal of the paper, their purpose is much more profound than that. They add to the White Paper’s readability. A reader might not have the time to go through 4 pages of your detailed solution, but he can study the diagram that’s accompanying it and gather the gist of your solution. Similarly, one can get the crux of the entire White Paper if there are well-made graphics accompanying each section. So, make sure to have ecosystem diagrams, pie charts, and graphs, illustrations, and icons, wherever possible. <b>Don’t forget to include Team profiles</b> - What you can’t do in the Lite Paper or on the website because of insufficiency of real estate, do it here - have detailed Team profiles. When the Team members are not internationally well-known people, it is difficult for the crypto-community spread across geographies to put their trust in them. Detailed profiles help in building credibility in the team working on the ICO project. So, talk about the work experience and educational qualifications of your team members, underline their achievements and the recognition they’ve won. Last but not the least, personalize them by talking about their passions, ambitions, and interests. <b>Draw a clear Roadmap</b> - This is another important credibility-building measure. A sufficiently detailed development roadmap helps the audience recognize why the ICO team needs to raise such large amounts of money. It helps them understand how and when the money raised will be utilized for different phases of product development. If the roadmap is ill-defined, then it means that the ICO team has not been rigorous enough in drafting the blueprint of its developmental plan. And if that is the case, then the money that the ICO team wants to raise will not get justified satisfactorily. <b>Justify the need for Blockchain</b> - Your White Paper must clearly be able to justify the organic need for Blockchain in your project. If it is unable to do that, then it probably means that you yourself don’t have a very clear understanding about the role of Blockchain in your product. Also, dedicating a paragraph to the generic features of Blockchain and signing off saying that it will “revolutionize” your concerned industry will not do. You must write about how and where exactly will Blockchain fit in into your ecosystem. <b>Check the message</b> - After you have finished the White Paper, compare it with your message planner. Have you covered all points of the message planner in your White Paper? Is your White Paper catering to all your audience segments? Have all the aspects of the problem been addressed by the solution you have provided? This exercise will help you to find the gaps in your White Paper and fill them before it goes live. <b>Don’t make it too long</b> - A White Paper, on an average, is made up of 30-40 pages, but sometimes, it can go up to a 100 pages or even more than that. If it really lengthy, chances are most readers will just skim through the White Paper or skip many parts of it. Some might not even read the White Paper. If you feel that your Tech sections are taking too many pages, then perhaps, you could have a separate Technical White Paper for your tech-savvy audience, while the Business White Paper can have only an outline of the technical solution. <b>Edit it</b> - Last but not the least, edit and proofread your White Paper before you publish it. A clean copy conveys your sense of meticulousness to your audience. If you have spent time to make sure that the White Paper is as high-quality as possible, you must have ensured the same about your product blueprint as well. Check for grammatical errors, spelling mistakes, stylistic inconsistencies, awkward phrasing, and typos. Go through the paper a few times to make sure that it is organized well, and the transitions between different sections are smooth. If possible, get a professional editor to look at it because software can point out grammatical and spelling errors, but it can’t comment on the quality of the paper. Once that’s done, you have a White Paper which is ready to be made live for the public. Turing Labs has helped numerous ICOs conceptualize, create, edit and publish top-quality Technical & Business White Papers. If you would like us to assist you developing your ICO White Paper, get in touch with us on [email protected] |
| json metadata | {"tags":["ico","blockchain","ethereum","organization","token"],"image":["https://steemitimages.com/DQmRukEgY6Ld24Ye6j6ss2B2eZeJRcwj4E8ZXdN6C3Pya1W/Whitepaper.jpg"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | ico |
| permlink | guidelines-for-writing-a-compelling-white-paper |
| title | Guidelines for writing a compelling White Paper |
| Transaction Info | Block #22539243/Trx b646353580f8b3884523cb67f16e6c43d8a967a3 |
View Raw JSON Data
{
"block": 22539243,
"op": [
"comment",
{
"author": "turingsafe",
"body": "\n\nA White Paper is a crucial marketing document for any ICO; it plays a significant role in communicating your Blockchain-based business to the world, convincing them of its potential, and motivating them to contribute towards its development. Thus, the document must be carefully planned and drafted, keeping in the mind the target audience, which is usually the crypto-community looking for the next big Blockchain project to invest in, and the stakeholders of the industry that the Blockchain project is aiming to revolutionize. \n\nA White Paper must find a sweet spot between being a technical research paper, a business report, and a buzzword salad. Here are a few things you need to keep in mind while drafting a powerful White Paper - \n\n<b>Have a compelling abstract</b> - An abstract outlines the problem you are aiming and the solution being offered by you in a few lines. An abstract is necessary because it helps readers decide if they want to read the entire White Paper or not. If an abstract is interesting enough if it will pique the interest of the audience, and chances are that they will read the whole White Paper. So, spend some time drafting the abstract and make sure that it doesn’t extend over a page. \n\n<b>Establish the Problem & Solution clearly</b> - The magnitude of the problem is important to establish. If the problem that you are trying to solve is substantial and affects a large number of people, chances are that your project will be able to a gather great support because more people will be able to relate to it and appreciate your taking the pains to develop a Blockchain-based solution for it. Once the problem has been established, the solution must follow. The solution must be practically viable with the technology available at that time because investors would want to invest in an idea, which actually has the potential to become a full-fledged product, be put into use, and earn revenues in the foreseeable future. \n\n<b>Cite all numbers</b> - Citations help build the credibility of White Paper. When you say that your revolutionary product is going to impact the $XX Bn industry, you must be able to reference the $XX Bn figure. The more the citations the better it is, because it shows that -\t\n\nYou know your industry well. You did your homework before writing the White Paper. \nYour data is not made up; your figures are not imaginary.\nYour calculations around the target market size, projected revenues, etc. are based on authentic data. \t\t\t\t\t\t\nWikipedia is not a go-to place for data. Refer to research papers, journals, business reports, articles & books from experts in the field for obtaining reliable information. \n\n<b>Include good graphics</b> - While graphics add to the aesthetic appeal of the paper, their purpose is much more profound than that. They add to the White Paper’s readability. A reader might not have the time to go through 4 pages of your detailed solution, but he can study the diagram that’s accompanying it and gather the gist of your solution. Similarly, one can get the crux of the entire White Paper if there are well-made graphics accompanying each section. So, make sure to have ecosystem diagrams, pie charts, and graphs, illustrations, and icons, wherever possible. \n\n<b>Don’t forget to include Team profiles</b> - What you can’t do in the Lite Paper or on the website because of insufficiency of real estate, do it here - have detailed Team profiles. When the Team members are not internationally well-known people, it is difficult for the crypto-community spread across geographies to put their trust in them. Detailed profiles help in building credibility in the team working on the ICO project. So, talk about the work experience and educational qualifications of your team members, underline their achievements and the recognition they’ve won. Last but not the least, personalize them by talking about their passions, ambitions, and interests. \n\n<b>Draw a clear Roadmap</b> - This is another important credibility-building measure. A sufficiently detailed development roadmap helps the audience recognize why the ICO team needs to raise such large amounts of money. It helps them understand how and when the money raised will be utilized for different phases of product development. If the roadmap is ill-defined, then it means that the ICO team has not been rigorous enough in drafting the blueprint of its developmental plan. And if that is the case, then the money that the ICO team wants to raise will not get justified satisfactorily. \n\n<b>Justify the need for Blockchain</b> - Your White Paper must clearly be able to justify the organic need for Blockchain in your project. If it is unable to do that, then it probably means that you yourself don’t have a very clear understanding about the role of Blockchain in your product. Also, dedicating a paragraph to the generic features of Blockchain and signing off saying that it will “revolutionize” your concerned industry will not do. You must write about how and where exactly will Blockchain fit in into your ecosystem. \n\n<b>Check the message</b> - After you have finished the White Paper, compare it with your message planner. Have you covered all points of the message planner in your White Paper? Is your White Paper catering to all your audience segments? Have all the aspects of the problem been addressed by the solution you have provided? This exercise will help you to find the gaps in your White Paper and fill them before it goes live. \n\n<b>Don’t make it too long</b> - A White Paper, on an average, is made up of 30-40 pages, but sometimes, it can go up to a 100 pages or even more than that. If it really lengthy, chances are most readers will just skim through the White Paper or skip many parts of it. Some might not even read the White Paper. If you feel that your Tech sections are taking too many pages, then perhaps, you could have a separate Technical White Paper for your tech-savvy audience, while the Business White Paper can have only an outline of the technical solution. \n\n<b>Edit it</b> - Last but not the least, edit and proofread your White Paper before you publish it. A clean copy conveys your sense of meticulousness to your audience. If you have spent time to make sure that the White Paper is as high-quality as possible, you must have ensured the same about your product blueprint as well. Check for grammatical errors, spelling mistakes, stylistic inconsistencies, awkward phrasing, and typos. Go through the paper a few times to make sure that it is organized well, and the transitions between different sections are smooth. If possible, get a professional editor to look at it because software can point out grammatical and spelling errors, but it can’t comment on the quality of the paper. Once that’s done, you have a White Paper which is ready to be made live for the public.\n\nTuring Labs has helped numerous ICOs conceptualize, create, edit and publish top-quality Technical & Business White Papers. If you would like us to assist you developing your ICO White Paper, get in touch with us on [email protected]",
"json_metadata": "{\"tags\":[\"ico\",\"blockchain\",\"ethereum\",\"organization\",\"token\"],\"image\":[\"https://steemitimages.com/DQmRukEgY6Ld24Ye6j6ss2B2eZeJRcwj4E8ZXdN6C3Pya1W/Whitepaper.jpg\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "ico",
"permlink": "guidelines-for-writing-a-compelling-white-paper",
"title": "Guidelines for writing a compelling White Paper"
}
],
"op_in_trx": 0,
"timestamp": "2018-05-18T13:27:30",
"trx_id": "b646353580f8b3884523cb67f16e6c43d8a967a3",
"trx_in_block": 2,
"virtual_op": 0
}turingsafereceived 0.011 SBD, 0.004 SP author reward for @turingsafe / what-is-community-building-and-how-you-can-get-it-right-for-your-ico2018/05/07 13:45:45
turingsafereceived 0.011 SBD, 0.004 SP author reward for @turingsafe / what-is-community-building-and-how-you-can-get-it-right-for-your-ico
2018/05/07 13:45:45
| author | turingsafe |
| permlink | what-is-community-building-and-how-you-can-get-it-right-for-your-ico |
| sbd payout | 0.011 SBD |
| steem payout | 0.000 STEEM |
| vesting payout | 6.107503 VESTS |
| Transaction Info | Block #22222847/Virtual Operation #4 |
View Raw JSON Data
{
"block": 22222847,
"op": [
"author_reward",
{
"author": "turingsafe",
"permlink": "what-is-community-building-and-how-you-can-get-it-right-for-your-ico",
"sbd_payout": "0.011 SBD",
"steem_payout": "0.000 STEEM",
"vesting_payout": "6.107503 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2018-05-07T13:45:45",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": 4
}2018/04/30 14:06:15
2018/04/30 14:06:15
| author | turingsafe |
| permlink | what-is-community-building-and-how-you-can-get-it-right-for-your-ico |
| voter | elowin |
| weight | 8000 (80.00%) |
| Transaction Info | Block #22021721/Trx 19af033d7975f1df3cfb1368c14c8c15f8c16721 |
View Raw JSON Data
{
"block": 22021721,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "what-is-community-building-and-how-you-can-get-it-right-for-your-ico",
"voter": "elowin",
"weight": 8000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-30T14:06:15",
"trx_id": "19af033d7975f1df3cfb1368c14c8c15f8c16721",
"trx_in_block": 32,
"virtual_op": 0
}2018/04/30 13:45:45
2018/04/30 13:45:45
| author | turingsafe |
| permlink | what-is-community-building-and-how-you-can-get-it-right-for-your-ico |
| voter | turingsafe |
| weight | 10000 (100.00%) |
| Transaction Info | Block #22021311/Trx faf31959426d33a3aacf46c801c18cbf2fa4aba9 |
View Raw JSON Data
{
"block": 22021311,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "what-is-community-building-and-how-you-can-get-it-right-for-your-ico",
"voter": "turingsafe",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-30T13:45:45",
"trx_id": "faf31959426d33a3aacf46c801c18cbf2fa4aba9",
"trx_in_block": 0,
"virtual_op": 0
}turingsafepublished a new post: what-is-community-building-and-how-you-can-get-it-right-for-your-ico2018/04/30 13:45:45
turingsafepublished a new post: what-is-community-building-and-how-you-can-get-it-right-for-your-ico
2018/04/30 13:45:45
| author | turingsafe |
| body |  We live in a world that is rapidly evolving because of the technological forces at play. One of the things that has changed because of technology is the way people connect and interact with one another. Blockchain-based products and services are reshaping the way the world conducts businesses by eliminating a lot of outdated, labour-intensive activities from business processes, and making the interactions between customers and businesses more transparent, efficient and productive. ICOs are a vehicle which help raise funds for the journey of Blockchain-based concepts from being ideas on paper to becoming actual products and services. However, an ICO needs the support of the crypto-community to become successful in its purpose. The ICO team has to identify its target community, reach out to it through different channels, communicate the product to it and convince it of its revolutionary potential, and then motivate the community members to contribute to the ICO. The process requires careful strategization and effort, and is absolutely imperative for any ICO. This is how you can build a great community for the success of your ICO - <b>Identify the right channels</b> - ICOs have a very small but powerful community at present. It is important to identify the right channels on which this community can be reached out to. Make sure that your ICO project has a strong presence on channels such as Facebook, Twitter, Medium, Reddit, Steemit, Telegram, Linkedin, BitcoinTalk etc. <b>Ensure strategic communications on all these channels</b> - Draft a message planner, which will act as a guiding light for all your communications. Strategize about how you want to communicate your project to the community. Communications should begin in the conceptualisation stage itself, and should intensify as the ICO progresses into further phases. Have a clear plan of what you want to communicate at each stage. <b>Have the website & all necessary documents in place</b> - All components of ICOs are interlinked, and thus, they affect each other. While creating a website & writing a white paper are distinct components of the ICO itself, they influence how the ICO community responds to your project. Before marketing your ICO, make sure that you have an informative, user-friendly and visually appealing website to direct your supporters to when they ask about your product. A white paper on the website explaining your product, business model, and technical architecture will contribute significantly in building credibility about your ICO. It also acted as a reference document when supporters ask questions about your product or the ICO. <b>Multi-lingual Support</b> - The ICO community is global, and to attract its support, the ICO team must have a provision for interacting with them in their languages. While Bounty Campaigns help in getting the white paper, website content and blogs translated, Telegram groups and Slack channels should also have a mix of admins fluent in different languages to respond to people promptly. <b>Bounty Campaigns</b> - Bounty Campaigns, when done right, contribute significantly to the viral growth of the community. In Bounty Campaigns, you reward your supporters with your tokens when they do certain tasks to help you reach out to a wider audience. Running a Bounty Campaign successfully requires time and attention, so assign a dedicated Bounty Manager for the same. The Bounty Manager will keep your BitcoinTalk Bounty Thread active, track the progress of Bounty participants, solve their problems, and invite more people to participate in the campaign. Plan stake allocation carefully, so as to avail maximum benefits from different Bounty pools. <b>Referral Marketing</b> - Initiating referral programs is another way of inducing viral growth of contributors. In marketing referral programs, existing contributors get incentives for bringing new contributors on board, which is generally a percentage of the new participant’s contribution, in tokens. Investing in conducting referral marketing is an smart choice because of higher conversion rates - existing participants are likely to promote the ICO to like-minded people. Secondly, the rewards are based on measurable results. To get more insights and support for community building, get in touch with us on [email protected] |
| json metadata | {"tags":["ico","blockchain","ethereum","organization","token"],"image":["https://steemitimages.com/DQmf3B88FNnr5EmYwdye5U9yAMV2Ecox61ATkyG1H1N7urG/Medium_post.jpg"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | ico |
| permlink | what-is-community-building-and-how-you-can-get-it-right-for-your-ico |
| title | What is Community Building and how you can get it right for your ICO |
| Transaction Info | Block #22021311/Trx faf31959426d33a3aacf46c801c18cbf2fa4aba9 |
View Raw JSON Data
{
"block": 22021311,
"op": [
"comment",
{
"author": "turingsafe",
"body": "\nWe live in a world that is rapidly evolving because of the technological forces at play. One of the things that has changed because of technology is the way people connect and interact with one another. Blockchain-based products and services are reshaping the way the world conducts businesses by eliminating a lot of outdated, labour-intensive activities from business processes, and making the interactions between customers and businesses more transparent, efficient and productive. \n\nICOs are a vehicle which help raise funds for the journey of Blockchain-based concepts from being ideas on paper to becoming actual products and services. However, an ICO needs the support of the crypto-community to become successful in its purpose. The ICO team has to identify its target community, reach out to it through different channels, communicate the product to it and convince it of its revolutionary potential, and then motivate the community members to contribute to the ICO. The process requires careful strategization and effort, and is absolutely imperative for any ICO. This is how you can build a great community for the success of your ICO -\n\n<b>Identify the right channels</b> - ICOs have a very small but powerful community at present. It is important to identify the right channels on which this community can be reached out to. Make sure that your ICO project has a strong presence on channels such as Facebook, Twitter, Medium, Reddit, Steemit, Telegram, Linkedin, BitcoinTalk etc. \n\n<b>Ensure strategic communications on all these channels</b> - Draft a message planner, which will act as a guiding light for all your communications. Strategize about how you want to communicate your project to the community. Communications should begin in the conceptualisation stage itself, and should intensify as the ICO progresses into further phases. Have a clear plan of what you want to communicate at each stage. \n\n<b>Have the website & all necessary documents in place</b> - All components of ICOs are interlinked, and thus, they affect each other. While creating a website & writing a white paper are distinct components of the ICO itself, they influence how the ICO community responds to your project. Before marketing your ICO, make sure that you have an informative, user-friendly and visually appealing website to direct your supporters to when they ask about your product. A white paper on the website explaining your product, business model, and technical architecture will contribute significantly in building credibility about your ICO. It also acted as a reference document when supporters ask questions about your product or the ICO. \n\n<b>Multi-lingual Support</b> - The ICO community is global, and to attract its support, the ICO team must have a provision for interacting with them in their languages. While Bounty Campaigns help in getting the white paper, website content and blogs translated, Telegram groups and Slack channels should also have a mix of admins fluent in different languages to respond to people promptly. \n\n<b>Bounty Campaigns</b> - Bounty Campaigns, when done right, contribute significantly to the viral growth of the community. In Bounty Campaigns, you reward your supporters with your tokens when they do certain tasks to help you reach out to a wider audience. Running a Bounty Campaign successfully requires time and attention, so assign a dedicated Bounty Manager for the same. The Bounty Manager will keep your BitcoinTalk Bounty Thread active, track the progress of Bounty participants, solve their problems, and invite more people to participate in the campaign. Plan stake allocation carefully, so as to avail maximum benefits from different Bounty pools. \n\n<b>Referral Marketing</b> - Initiating referral programs is another way of inducing viral growth of contributors. In marketing referral programs, existing contributors get incentives for bringing new contributors on board, which is generally a percentage of the new participant’s contribution, in tokens. Investing in conducting referral marketing is an smart choice because of higher conversion rates - existing participants are likely to promote the ICO to like-minded people. Secondly, the rewards are based on measurable results. \n\nTo get more insights and support for community building, get in touch with us on [email protected]",
"json_metadata": "{\"tags\":[\"ico\",\"blockchain\",\"ethereum\",\"organization\",\"token\"],\"image\":[\"https://steemitimages.com/DQmf3B88FNnr5EmYwdye5U9yAMV2Ecox61ATkyG1H1N7urG/Medium_post.jpg\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "ico",
"permlink": "what-is-community-building-and-how-you-can-get-it-right-for-your-ico",
"title": "What is Community Building and how you can get it right for your ICO"
}
],
"op_in_trx": 0,
"timestamp": "2018-04-30T13:45:45",
"trx_id": "faf31959426d33a3aacf46c801c18cbf2fa4aba9",
"trx_in_block": 0,
"virtual_op": 0
}turingsafeupdated their account properties2018/04/30 13:06:33
turingsafeupdated their account properties
2018/04/30 13:06:33
| account | turingsafe |
| json metadata | {"profile":{"name":"Turing Labs","website":"https://www.turinglabs.io"}} |
| memo key | STM5JCVTuQpALTQ56RZZRFYSgT5SXv28m8t8j1nkTsBweRJxJq5Ku |
| Transaction Info | Block #22020528/Trx 9f34a65fa2fc55142400ba7662f5601b880dc011 |
View Raw JSON Data
{
"block": 22020528,
"op": [
"account_update",
{
"account": "turingsafe",
"json_metadata": "{\"profile\":{\"name\":\"Turing Labs\",\"website\":\"https://www.turinglabs.io\"}}",
"memo_key": "STM5JCVTuQpALTQ56RZZRFYSgT5SXv28m8t8j1nkTsBweRJxJq5Ku"
}
],
"op_in_trx": 0,
"timestamp": "2018-04-30T13:06:33",
"trx_id": "9f34a65fa2fc55142400ba7662f5601b880dc011",
"trx_in_block": 18,
"virtual_op": 0
}turingsafereceived 0.029 SBD, 0.009 SP author reward for @turingsafe / best-practices-for-securing-your-ico2018/04/30 07:12:30
turingsafereceived 0.029 SBD, 0.009 SP author reward for @turingsafe / best-practices-for-securing-your-ico
2018/04/30 07:12:30
| author | turingsafe |
| permlink | best-practices-for-securing-your-ico |
| sbd payout | 0.029 SBD |
| steem payout | 0.000 STEEM |
| vesting payout | 14.256207 VESTS |
| Transaction Info | Block #22013448/Virtual Operation #8 |
View Raw JSON Data
{
"block": 22013448,
"op": [
"author_reward",
{
"author": "turingsafe",
"permlink": "best-practices-for-securing-your-ico",
"sbd_payout": "0.029 SBD",
"steem_payout": "0.000 STEEM",
"vesting_payout": "14.256207 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2018-04-30T07:12:30",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": 8
}2018/04/26 11:37:03
2018/04/26 11:37:03
| author | turingsafe |
| permlink | token-launcher-platform-build-a-fully-compliant-ico-tailored-for-your-success |
| voter | turingsafe |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21903570/Trx 343e7d7f4643a3370bd422665ce15e02cdccbcae |
View Raw JSON Data
{
"block": 21903570,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "token-launcher-platform-build-a-fully-compliant-ico-tailored-for-your-success",
"voter": "turingsafe",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-26T11:37:03",
"trx_id": "343e7d7f4643a3370bd422665ce15e02cdccbcae",
"trx_in_block": 20,
"virtual_op": 0
}turingsafepublished a new post: token-launcher-platform-build-a-fully-compliant-ico-tailored-for-your-success2018/04/26 11:37:03
turingsafepublished a new post: token-launcher-platform-build-a-fully-compliant-ico-tailored-for-your-success
2018/04/26 11:37:03
| author | turingsafe |
| body |  <b>Overview</b> ICOs have come a long way from their clumsy websites and white papers to a highly interactive and professional interface. Any website without 100% mobile-responsiveness gives the impression that the ICO is not serious about the product and just wants to raise money fast. A white paper with anything less than stellar tokenomics runs the risk of being labeled a scam. Therefore, the ICO platform should be a seamless integration of: 1. An interactive and engaging front-end; and 2. A robust and fortified backend optimized for performance. <b>Introduction</b> Turing Labs has built a comprehensive solution — The Token Launcher Platform to provide a launchpad for your ICO. The Token Launcher Platform is an end-to-end ICO launch platform that provides the following services: 1. Real-time Analysis of the ICO 2. KYC-compliance 3. User-friendly and interactive experience 4. Comprehensive Auditing of your ICO Platform 5. Customization of Services 6. Referral/Affiliate Marketing Integration These services work in tandem and leverage their strengths for the overall success of your ICO. Since each service has specific upsides and provides a specific outcome, the integration of all of these services and timing it perfectly is what separates a good ICO from a decent one. The utility of each of the above-mentioned services and their importance for the success of the ICO have been elucidated below. <b>Real-time Analysis of the ICO</b> An ICO is marketed globally. This creates a volume of data, if done right, and provides countless insights on the performance of the ICO in various regions and with various sections of contributors. Token Launcher Platform provides a dashboard for real-time tracking of the performance of your ICO by completely integrating with your CRM. It contains several graphs that help you devise further strategies and take corrective/expansive measures, as needed. It is of utmost importance to stay on top of the statistics that help you study emerging trends, as well as, anticipate and identify down-trends. <b>KYC Compliance</b> A good ICO always ensures that the funds accrued in its name are of clean origin and contain no traces of money laundering, terror financing, and other such nefarious activities. Therefore, KYC compliance has been introduced in the finance sector to prevent ill-gotten wealth from becoming a part of your ICO. Token Launcher Platform devises a non-intrusive mechanism for your contributors to create KYC verified profiles before contributing. <b>User-friendly and Interactive Experience</b> Visitors and contributors alike must be provided with an engaging interface to ensure that that keep coming back and refer their friends. This requires a well-designed funnel which pushes the visitor/prospective contributor to the next segment of the funnel without requiring much effort. The Token Launcher Platform creates an extremely user-friendly ICO platform that integrates completely with the Analysis Dashboard. This allows you to find out missing links in your funnel and plug them, as well as, expand the efforts on those aspects which are giving good results. <b>Comprehensive Auditing of your ICO Platform</b> An ICO platform consists of three chief components that are exposed to outside interference. These are, the ICO Website, the ICO Smart Contracts, and the ICO recipient wallet addresses. The Token Launcher Platform provides complete auditing of all these three components and offers assistance to plug the vulnerabilities uncovered in the audit process. <b>Customization of Services</b> At Token Launcher Platform, we believe that templates are never the path to success. We create unique solutions customized as per their needs and wants. While we advise the clients on the best practices in token launching services, we also take into account the individuality and the brand identity that you want to build for your ICO. Referral/Affiliate Marketing Integration Creating customized referral links which can be distributed by your ICO evangelists to their followers and peers. A customized referral link can help track the performance of your evangelists even better. Through this tool, you can analyze the conversion ratios of your evangelists and ICO Advisors.  <b>Conclusion</b> In sum, the Token Launcher Platform is a one-stop shop for your ICO. If you've got the idea, we've got the tools to create a platform that will increase the reach of your ICO many times over. For queries, please contact us at [email protected] |
| json metadata | {"tags":["ico","blockchain","ethereum","organization","dapps"],"image":["https://steemitimages.com/DQmfUBXKEDkoD5PGE8u4cxzTf9vSFu3w9c5fnpLAH8CK2KG/Image-1.jpg","https://steemitimages.com/DQmeGF7DknpWquMXXXyNVbHFYGZGduiyA3iaiEDGHAxUmyS/Image-2.jpg"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | ico |
| permlink | token-launcher-platform-build-a-fully-compliant-ico-tailored-for-your-success |
| title | Token Launcher Platform — Build a fully compliant ICO, tailored for your Success |
| Transaction Info | Block #21903570/Trx 343e7d7f4643a3370bd422665ce15e02cdccbcae |
View Raw JSON Data
{
"block": 21903570,
"op": [
"comment",
{
"author": "turingsafe",
"body": "\n<b>Overview</b>\nICOs have come a long way from their clumsy websites and white papers to a highly interactive and professional interface. Any website without 100% mobile-responsiveness gives the impression that the ICO is not serious about the product and just wants to raise money fast. A white paper with anything less than stellar tokenomics runs the risk of being labeled a scam. Therefore, the ICO platform should be a seamless integration of:\n\n1. An interactive and engaging front-end; and\n2. A robust and fortified backend optimized for performance.\n\n<b>Introduction</b>\nTuring Labs has built a comprehensive solution — The Token Launcher Platform to provide a launchpad for your ICO. The Token Launcher Platform is an end-to-end ICO launch platform that provides the following services:\n\n1. Real-time Analysis of the ICO\n2. KYC-compliance\n3. User-friendly and interactive experience\n4. Comprehensive Auditing of your ICO Platform\n5. Customization of Services\n6. Referral/Affiliate Marketing Integration\n\nThese services work in tandem and leverage their strengths for the overall success of your ICO. Since each service has specific upsides and provides a specific outcome, the integration of all of these services and timing it perfectly is what separates a good ICO from a decent one. The utility of each of the above-mentioned services and their importance for the success of the ICO have been elucidated below.\n\n<b>Real-time Analysis of the ICO</b>\nAn ICO is marketed globally. This creates a volume of data, if done right, and provides countless insights on the performance of the ICO in various regions and with various sections of contributors. Token Launcher Platform provides a dashboard for real-time tracking of the performance of your ICO by completely integrating with your CRM. It contains several graphs that help you devise further strategies and take corrective/expansive measures, as needed. It is of utmost importance to stay on top of the statistics that help you study emerging trends, as well as, anticipate and identify down-trends.\n\n<b>KYC Compliance</b>\nA good ICO always ensures that the funds accrued in its name are of clean origin and contain no traces of money laundering, terror financing, and other such nefarious activities. Therefore, KYC compliance has been introduced in the finance sector to prevent ill-gotten wealth from becoming a part of your ICO. Token Launcher Platform devises a non-intrusive mechanism for your contributors to create KYC verified profiles before contributing.\n\n<b>User-friendly and Interactive Experience</b>\nVisitors and contributors alike must be provided with an engaging interface to ensure that that keep coming back and refer their friends. This requires a well-designed funnel which pushes the visitor/prospective contributor to the next segment of the funnel without requiring much effort. The Token Launcher Platform creates an extremely user-friendly ICO platform that integrates completely with the Analysis Dashboard. This allows you to find out missing links in your funnel and plug them, as well as, expand the efforts on those aspects which are giving good results. \n\n<b>Comprehensive Auditing of your ICO Platform</b>\nAn ICO platform consists of three chief components that are exposed to outside interference. These are, the ICO Website, the ICO Smart Contracts, and the ICO recipient wallet addresses. The Token Launcher Platform provides complete auditing of all these three components and offers assistance to plug the vulnerabilities uncovered in the audit process.\n\n<b>Customization of Services</b>\nAt Token Launcher Platform, we believe that templates are never the path to success. We create unique solutions customized as per their needs and wants. While we advise the clients on the best practices in token launching services, we also take into account the individuality and the brand identity that you want to build for your ICO.\nReferral/Affiliate Marketing Integration\nCreating customized referral links which can be distributed by your ICO evangelists to their followers and peers. A customized referral link can help track the performance of your evangelists even better. Through this tool, you can analyze the conversion ratios of your evangelists and ICO Advisors.\n\n\n<b>Conclusion</b> \nIn sum, the Token Launcher Platform is a one-stop shop for your ICO. If you've got the idea, we've got the tools to create a platform that will increase the reach of your ICO many times over. \n\nFor queries, please contact us at [email protected]",
"json_metadata": "{\"tags\":[\"ico\",\"blockchain\",\"ethereum\",\"organization\",\"dapps\"],\"image\":[\"https://steemitimages.com/DQmfUBXKEDkoD5PGE8u4cxzTf9vSFu3w9c5fnpLAH8CK2KG/Image-1.jpg\",\"https://steemitimages.com/DQmeGF7DknpWquMXXXyNVbHFYGZGduiyA3iaiEDGHAxUmyS/Image-2.jpg\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "ico",
"permlink": "token-launcher-platform-build-a-fully-compliant-ico-tailored-for-your-success",
"title": "Token Launcher Platform — Build a fully compliant ICO, tailored for your Success"
}
],
"op_in_trx": 0,
"timestamp": "2018-04-26T11:37:03",
"trx_id": "343e7d7f4643a3370bd422665ce15e02cdccbcae",
"trx_in_block": 20,
"virtual_op": 0
}olegkuslijupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico2018/04/23 16:16:30
olegkuslijupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico
2018/04/23 16:16:30
| author | turingsafe |
| permlink | best-practices-for-securing-your-ico |
| voter | olegkuslij |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21823412/Trx 951c3813aba27295494fd09dcd4685536db25dd9 |
View Raw JSON Data
{
"block": 21823412,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "best-practices-for-securing-your-ico",
"voter": "olegkuslij",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-23T16:16:30",
"trx_id": "951c3813aba27295494fd09dcd4685536db25dd9",
"trx_in_block": 16,
"virtual_op": 0
}polyaevupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico2018/04/23 16:16:00
polyaevupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico
2018/04/23 16:16:00
| author | turingsafe |
| permlink | best-practices-for-securing-your-ico |
| voter | polyaev |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21823402/Trx 2cea5c74897e173e0ebe7604de4173d20a407fb9 |
View Raw JSON Data
{
"block": 21823402,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "best-practices-for-securing-your-ico",
"voter": "polyaev",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-23T16:16:00",
"trx_id": "2cea5c74897e173e0ebe7604de4173d20a407fb9",
"trx_in_block": 17,
"virtual_op": 0
}genassharupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico2018/04/23 16:15:48
genassharupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico
2018/04/23 16:15:48
| author | turingsafe |
| permlink | best-practices-for-securing-your-ico |
| voter | genasshar |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21823398/Trx 4518f96eb7f4c9ac97a2db0a48e9b69af802261a |
View Raw JSON Data
{
"block": 21823398,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "best-practices-for-securing-your-ico",
"voter": "genasshar",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-23T16:15:48",
"trx_id": "4518f96eb7f4c9ac97a2db0a48e9b69af802261a",
"trx_in_block": 38,
"virtual_op": 0
}denidenisupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico2018/04/23 16:15:18
denidenisupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico
2018/04/23 16:15:18
| author | turingsafe |
| permlink | best-practices-for-securing-your-ico |
| voter | denidenis |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21823388/Trx fc78d52b59c95c5377e2af2c2a1df6f8508b8888 |
View Raw JSON Data
{
"block": 21823388,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "best-practices-for-securing-your-ico",
"voter": "denidenis",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-23T16:15:18",
"trx_id": "fc78d52b59c95c5377e2af2c2a1df6f8508b8888",
"trx_in_block": 41,
"virtual_op": 0
}ktoryaupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico2018/04/23 16:15:06
ktoryaupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico
2018/04/23 16:15:06
| author | turingsafe |
| permlink | best-practices-for-securing-your-ico |
| voter | ktorya |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21823384/Trx b4558797f179c1cc79ca5427d96225bbee7d7764 |
View Raw JSON Data
{
"block": 21823384,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "best-practices-for-securing-your-ico",
"voter": "ktorya",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-23T16:15:06",
"trx_id": "b4558797f179c1cc79ca5427d96225bbee7d7764",
"trx_in_block": 40,
"virtual_op": 0
}metelupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico2018/04/23 16:14:51
metelupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico
2018/04/23 16:14:51
| author | turingsafe |
| permlink | best-practices-for-securing-your-ico |
| voter | metel |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21823379/Trx 790791b8b1956b7a091fb770e13d4763166632e2 |
View Raw JSON Data
{
"block": 21823379,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "best-practices-for-securing-your-ico",
"voter": "metel",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-23T16:14:51",
"trx_id": "790791b8b1956b7a091fb770e13d4763166632e2",
"trx_in_block": 30,
"virtual_op": 0
}shammupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico2018/04/23 16:13:51
shammupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico
2018/04/23 16:13:51
| author | turingsafe |
| permlink | best-practices-for-securing-your-ico |
| voter | shamm |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21823359/Trx a2499a717b1797b4d9000bf05cca759a0a83ca31 |
View Raw JSON Data
{
"block": 21823359,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "best-practices-for-securing-your-ico",
"voter": "shamm",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-23T16:13:51",
"trx_id": "a2499a717b1797b4d9000bf05cca759a0a83ca31",
"trx_in_block": 13,
"virtual_op": 0
}margaritapahomoupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico2018/04/23 16:13:45
margaritapahomoupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico
2018/04/23 16:13:45
| author | turingsafe |
| permlink | best-practices-for-securing-your-ico |
| voter | margaritapahomo |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21823357/Trx 19bcfba9e2bcc2922dc8252160a1a2bfc28e0301 |
View Raw JSON Data
{
"block": 21823357,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "best-practices-for-securing-your-ico",
"voter": "margaritapahomo",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-23T16:13:45",
"trx_id": "19bcfba9e2bcc2922dc8252160a1a2bfc28e0301",
"trx_in_block": 40,
"virtual_op": 0
}ramannarkomanupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico2018/04/23 15:08:06
ramannarkomanupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico
2018/04/23 15:08:06
| author | turingsafe |
| permlink | best-practices-for-securing-your-ico |
| voter | ramannarkoman |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21822044/Trx e52b6ba0295d44258f47711f421e0451ae6a3397 |
View Raw JSON Data
{
"block": 21822044,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "best-practices-for-securing-your-ico",
"voter": "ramannarkoman",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-23T15:08:06",
"trx_id": "e52b6ba0295d44258f47711f421e0451ae6a3397",
"trx_in_block": 0,
"virtual_op": 0
}izotovupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico2018/04/23 15:07:57
izotovupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico
2018/04/23 15:07:57
| author | turingsafe |
| permlink | best-practices-for-securing-your-ico |
| voter | izotov |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21822041/Trx 50babffa9b714c2e7ab8dddaaf58a89cd8101935 |
View Raw JSON Data
{
"block": 21822041,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "best-practices-for-securing-your-ico",
"voter": "izotov",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-23T15:07:57",
"trx_id": "50babffa9b714c2e7ab8dddaaf58a89cd8101935",
"trx_in_block": 2,
"virtual_op": 0
}borisa35upvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico2018/04/23 15:07:51
borisa35upvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico
2018/04/23 15:07:51
| author | turingsafe |
| permlink | best-practices-for-securing-your-ico |
| voter | borisa35 |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21822039/Trx c098ebb4d4d77c8d0a24af6a4d9c8a7c604113bb |
View Raw JSON Data
{
"block": 21822039,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "best-practices-for-securing-your-ico",
"voter": "borisa35",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-23T15:07:51",
"trx_id": "c098ebb4d4d77c8d0a24af6a4d9c8a7c604113bb",
"trx_in_block": 0,
"virtual_op": 0
}astriostovupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico2018/04/23 15:07:30
astriostovupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico
2018/04/23 15:07:30
| author | turingsafe |
| permlink | best-practices-for-securing-your-ico |
| voter | astriostov |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21822032/Trx fc8bff4179a62906240150e9a64397a548e92558 |
View Raw JSON Data
{
"block": 21822032,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "best-practices-for-securing-your-ico",
"voter": "astriostov",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-23T15:07:30",
"trx_id": "fc8bff4179a62906240150e9a64397a548e92558",
"trx_in_block": 27,
"virtual_op": 0
}chuvanovaupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico2018/04/23 15:07:09
chuvanovaupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico
2018/04/23 15:07:09
| author | turingsafe |
| permlink | best-practices-for-securing-your-ico |
| voter | chuvanova |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21822025/Trx 36aa9dfbebcf1220bb7480ba4466ddb94d8d2498 |
View Raw JSON Data
{
"block": 21822025,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "best-practices-for-securing-your-ico",
"voter": "chuvanova",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-23T15:07:09",
"trx_id": "36aa9dfbebcf1220bb7480ba4466ddb94d8d2498",
"trx_in_block": 36,
"virtual_op": 0
}lenasazonupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico2018/04/23 15:07:09
lenasazonupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico
2018/04/23 15:07:09
| author | turingsafe |
| permlink | best-practices-for-securing-your-ico |
| voter | lenasazon |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21822025/Trx 46697b9b99196a3f735a968daff47790b6530813 |
View Raw JSON Data
{
"block": 21822025,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "best-practices-for-securing-your-ico",
"voter": "lenasazon",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-23T15:07:09",
"trx_id": "46697b9b99196a3f735a968daff47790b6530813",
"trx_in_block": 27,
"virtual_op": 0
}brataupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico2018/04/23 15:06:06
brataupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico
2018/04/23 15:06:06
| author | turingsafe |
| permlink | best-practices-for-securing-your-ico |
| voter | brata |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21822004/Trx e5fe34cbc85f5c9efad05221f92233d4a9e8e158 |
View Raw JSON Data
{
"block": 21822004,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "best-practices-for-securing-your-ico",
"voter": "brata",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-23T15:06:06",
"trx_id": "e5fe34cbc85f5c9efad05221f92233d4a9e8e158",
"trx_in_block": 19,
"virtual_op": 0
}vazakevvaupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico2018/04/23 15:06:06
vazakevvaupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico
2018/04/23 15:06:06
| author | turingsafe |
| permlink | best-practices-for-securing-your-ico |
| voter | vazakevva |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21822004/Trx 9081d22cf349753da6a18d402e416177a14654d6 |
View Raw JSON Data
{
"block": 21822004,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "best-practices-for-securing-your-ico",
"voter": "vazakevva",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-23T15:06:06",
"trx_id": "9081d22cf349753da6a18d402e416177a14654d6",
"trx_in_block": 0,
"virtual_op": 0
}ramazanupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico2018/04/23 15:06:00
ramazanupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico
2018/04/23 15:06:00
| author | turingsafe |
| permlink | best-practices-for-securing-your-ico |
| voter | ramazan |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21822002/Trx 7fe3d2873577eba1c122e04a341ab7e439f9c1c1 |
View Raw JSON Data
{
"block": 21822002,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "best-practices-for-securing-your-ico",
"voter": "ramazan",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-23T15:06:00",
"trx_id": "7fe3d2873577eba1c122e04a341ab7e439f9c1c1",
"trx_in_block": 49,
"virtual_op": 0
}nimaevupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico2018/04/23 15:05:54
nimaevupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico
2018/04/23 15:05:54
| author | turingsafe |
| permlink | best-practices-for-securing-your-ico |
| voter | nimaev |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21822000/Trx a10860513ec1704f205a7b892f0a68211e1364c6 |
View Raw JSON Data
{
"block": 21822000,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "best-practices-for-securing-your-ico",
"voter": "nimaev",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-23T15:05:54",
"trx_id": "a10860513ec1704f205a7b892f0a68211e1364c6",
"trx_in_block": 20,
"virtual_op": 0
}mirandaqupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico2018/04/23 15:05:24
mirandaqupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico
2018/04/23 15:05:24
| author | turingsafe |
| permlink | best-practices-for-securing-your-ico |
| voter | mirandaq |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21821990/Trx 28bcd63335c061dfdbe7bae8c9439aa0069b3ca1 |
View Raw JSON Data
{
"block": 21821990,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "best-practices-for-securing-your-ico",
"voter": "mirandaq",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-23T15:05:24",
"trx_id": "28bcd63335c061dfdbe7bae8c9439aa0069b3ca1",
"trx_in_block": 32,
"virtual_op": 0
}rupovetsupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico2018/04/23 08:46:54
rupovetsupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico
2018/04/23 08:46:54
| author | turingsafe |
| permlink | best-practices-for-securing-your-ico |
| voter | rupovets |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21814420/Trx 6f4e8d4d567090f6913ec14d001e687d6f3e67a4 |
View Raw JSON Data
{
"block": 21814420,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "best-practices-for-securing-your-ico",
"voter": "rupovets",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-23T08:46:54",
"trx_id": "6f4e8d4d567090f6913ec14d001e687d6f3e67a4",
"trx_in_block": 27,
"virtual_op": 0
}nikolas169upvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico2018/04/23 08:46:33
nikolas169upvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico
2018/04/23 08:46:33
| author | turingsafe |
| permlink | best-practices-for-securing-your-ico |
| voter | nikolas169 |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21814413/Trx 1928393f9a766e39154cb937ddffa50bca4ea718 |
View Raw JSON Data
{
"block": 21814413,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "best-practices-for-securing-your-ico",
"voter": "nikolas169",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-23T08:46:33",
"trx_id": "1928393f9a766e39154cb937ddffa50bca4ea718",
"trx_in_block": 2,
"virtual_op": 0
}finikupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico2018/04/23 08:46:24
finikupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico
2018/04/23 08:46:24
| author | turingsafe |
| permlink | best-practices-for-securing-your-ico |
| voter | finik |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21814410/Trx cf4b533f599a3bf0bff9933ddabbe212529d5f6f |
View Raw JSON Data
{
"block": 21814410,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "best-practices-for-securing-your-ico",
"voter": "finik",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-23T08:46:24",
"trx_id": "cf4b533f599a3bf0bff9933ddabbe212529d5f6f",
"trx_in_block": 41,
"virtual_op": 0
}fvvv6upvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico2018/04/23 08:46:12
fvvv6upvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico
2018/04/23 08:46:12
| author | turingsafe |
| permlink | best-practices-for-securing-your-ico |
| voter | fvvv6 |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21814406/Trx 7988f36c359f951d3526d978f03da1e389288927 |
View Raw JSON Data
{
"block": 21814406,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "best-practices-for-securing-your-ico",
"voter": "fvvv6",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-23T08:46:12",
"trx_id": "7988f36c359f951d3526d978f03da1e389288927",
"trx_in_block": 34,
"virtual_op": 0
}artemkayaupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico2018/04/23 08:45:54
artemkayaupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico
2018/04/23 08:45:54
| author | turingsafe |
| permlink | best-practices-for-securing-your-ico |
| voter | artemkaya |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21814400/Trx 5af8a8f81d991a44c500be9219abde7df64bd809 |
View Raw JSON Data
{
"block": 21814400,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "best-practices-for-securing-your-ico",
"voter": "artemkaya",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-23T08:45:54",
"trx_id": "5af8a8f81d991a44c500be9219abde7df64bd809",
"trx_in_block": 39,
"virtual_op": 0
}mosovupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico2018/04/23 08:45:48
mosovupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico
2018/04/23 08:45:48
| author | turingsafe |
| permlink | best-practices-for-securing-your-ico |
| voter | mosov |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21814398/Trx 2210290009a19ddf9f5b57aab94f7e7495fac482 |
View Raw JSON Data
{
"block": 21814398,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "best-practices-for-securing-your-ico",
"voter": "mosov",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-23T08:45:48",
"trx_id": "2210290009a19ddf9f5b57aab94f7e7495fac482",
"trx_in_block": 23,
"virtual_op": 0
}corabelupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico2018/04/23 08:45:30
corabelupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico
2018/04/23 08:45:30
| author | turingsafe |
| permlink | best-practices-for-securing-your-ico |
| voter | corabel |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21814392/Trx 0abf64d01ec643bb3a50c95eee3d4fcd7683a648 |
View Raw JSON Data
{
"block": 21814392,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "best-practices-for-securing-your-ico",
"voter": "corabel",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-23T08:45:30",
"trx_id": "0abf64d01ec643bb3a50c95eee3d4fcd7683a648",
"trx_in_block": 48,
"virtual_op": 0
}fakaska86upvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico2018/04/23 08:45:30
fakaska86upvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico
2018/04/23 08:45:30
| author | turingsafe |
| permlink | best-practices-for-securing-your-ico |
| voter | fakaska86 |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21814392/Trx 4df72ad22097db155521454b461b518fa3000a9c |
View Raw JSON Data
{
"block": 21814392,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "best-practices-for-securing-your-ico",
"voter": "fakaska86",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-23T08:45:30",
"trx_id": "4df72ad22097db155521454b461b518fa3000a9c",
"trx_in_block": 36,
"virtual_op": 0
}olgaskalupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico2018/04/23 08:45:24
olgaskalupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico
2018/04/23 08:45:24
| author | turingsafe |
| permlink | best-practices-for-securing-your-ico |
| voter | olgaskal |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21814390/Trx 53acf200359c2f9f78a50a191e05baa31e047e1b |
View Raw JSON Data
{
"block": 21814390,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "best-practices-for-securing-your-ico",
"voter": "olgaskal",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-23T08:45:24",
"trx_id": "53acf200359c2f9f78a50a191e05baa31e047e1b",
"trx_in_block": 14,
"virtual_op": 0
}vonyuupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico2018/04/23 08:45:24
vonyuupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico
2018/04/23 08:45:24
| author | turingsafe |
| permlink | best-practices-for-securing-your-ico |
| voter | vonyu |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21814390/Trx f4a246511bfe0ca9200c68320507d04e9f065f1b |
View Raw JSON Data
{
"block": 21814390,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "best-practices-for-securing-your-ico",
"voter": "vonyu",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-23T08:45:24",
"trx_id": "f4a246511bfe0ca9200c68320507d04e9f065f1b",
"trx_in_block": 4,
"virtual_op": 0
}buchenkovaupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico2018/04/23 08:45:21
buchenkovaupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico
2018/04/23 08:45:21
| author | turingsafe |
| permlink | best-practices-for-securing-your-ico |
| voter | buchenkova |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21814389/Trx b78d955e059c1f1e637697681dca91c482778226 |
View Raw JSON Data
{
"block": 21814389,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "best-practices-for-securing-your-ico",
"voter": "buchenkova",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-23T08:45:21",
"trx_id": "b78d955e059c1f1e637697681dca91c482778226",
"trx_in_block": 13,
"virtual_op": 0
}skolyshenaupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico2018/04/23 08:45:18
skolyshenaupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico
2018/04/23 08:45:18
| author | turingsafe |
| permlink | best-practices-for-securing-your-ico |
| voter | skolyshena |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21814388/Trx 050949ab5bd3afd1a3bd4c63f6f8e4fa17c1e048 |
View Raw JSON Data
{
"block": 21814388,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "best-practices-for-securing-your-ico",
"voter": "skolyshena",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-23T08:45:18",
"trx_id": "050949ab5bd3afd1a3bd4c63f6f8e4fa17c1e048",
"trx_in_block": 0,
"virtual_op": 0
}letoisnichupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico2018/04/23 08:44:42
letoisnichupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico
2018/04/23 08:44:42
| author | turingsafe |
| permlink | best-practices-for-securing-your-ico |
| voter | letoisnich |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21814376/Trx 93d7eead58cbc7655765fce53090f7772178ebc3 |
View Raw JSON Data
{
"block": 21814376,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "best-practices-for-securing-your-ico",
"voter": "letoisnich",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-23T08:44:42",
"trx_id": "93d7eead58cbc7655765fce53090f7772178ebc3",
"trx_in_block": 14,
"virtual_op": 0
}maxvoroshupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico2018/04/23 08:44:36
maxvoroshupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico
2018/04/23 08:44:36
| author | turingsafe |
| permlink | best-practices-for-securing-your-ico |
| voter | maxvorosh |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21814374/Trx 23c314295b42713ac04f6be24108b1b4422a5104 |
View Raw JSON Data
{
"block": 21814374,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "best-practices-for-securing-your-ico",
"voter": "maxvorosh",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-23T08:44:36",
"trx_id": "23c314295b42713ac04f6be24108b1b4422a5104",
"trx_in_block": 9,
"virtual_op": 0
}ivnitisenupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico2018/04/23 08:44:30
ivnitisenupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico
2018/04/23 08:44:30
| author | turingsafe |
| permlink | best-practices-for-securing-your-ico |
| voter | ivnitisen |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21814372/Trx baf3d47f342ef7817af1fd162e7780318c8be3dd |
View Raw JSON Data
{
"block": 21814372,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "best-practices-for-securing-your-ico",
"voter": "ivnitisen",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-23T08:44:30",
"trx_id": "baf3d47f342ef7817af1fd162e7780318c8be3dd",
"trx_in_block": 1,
"virtual_op": 0
}olichidjaupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico2018/04/23 08:44:27
olichidjaupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico
2018/04/23 08:44:27
| author | turingsafe |
| permlink | best-practices-for-securing-your-ico |
| voter | olichidja |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21814371/Trx 524f21d125484cac74ab74fe8922548b1814f0d8 |
View Raw JSON Data
{
"block": 21814371,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "best-practices-for-securing-your-ico",
"voter": "olichidja",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-23T08:44:27",
"trx_id": "524f21d125484cac74ab74fe8922548b1814f0d8",
"trx_in_block": 10,
"virtual_op": 0
}leksandupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico2018/04/23 08:44:24
leksandupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico
2018/04/23 08:44:24
| author | turingsafe |
| permlink | best-practices-for-securing-your-ico |
| voter | leksand |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21814370/Trx e8d59a617aea0ffb62cb3fd40210281c5e7f6c05 |
View Raw JSON Data
{
"block": 21814370,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "best-practices-for-securing-your-ico",
"voter": "leksand",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-23T08:44:24",
"trx_id": "e8d59a617aea0ffb62cb3fd40210281c5e7f6c05",
"trx_in_block": 40,
"virtual_op": 0
}ustartsevupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico2018/04/23 08:44:21
ustartsevupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico
2018/04/23 08:44:21
| author | turingsafe |
| permlink | best-practices-for-securing-your-ico |
| voter | ustartsev |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21814369/Trx df3d8fe6afabcdbccde27910e12343e26ea28427 |
View Raw JSON Data
{
"block": 21814369,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "best-practices-for-securing-your-ico",
"voter": "ustartsev",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-23T08:44:21",
"trx_id": "df3d8fe6afabcdbccde27910e12343e26ea28427",
"trx_in_block": 2,
"virtual_op": 0
}berlokupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico2018/04/23 08:40:15
berlokupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico
2018/04/23 08:40:15
| author | turingsafe |
| permlink | best-practices-for-securing-your-ico |
| voter | berlok |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21814287/Trx ddd4729de1a9d4b06da3c11dba7fb430ed23c6b6 |
View Raw JSON Data
{
"block": 21814287,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "best-practices-for-securing-your-ico",
"voter": "berlok",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-23T08:40:15",
"trx_id": "ddd4729de1a9d4b06da3c11dba7fb430ed23c6b6",
"trx_in_block": 12,
"virtual_op": 0
}khryaevaoupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico2018/04/23 08:40:06
khryaevaoupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico
2018/04/23 08:40:06
| author | turingsafe |
| permlink | best-practices-for-securing-your-ico |
| voter | khryaevao |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21814284/Trx 7fe2a54055eaf1186720027a7690e4814c2a6a3e |
View Raw JSON Data
{
"block": 21814284,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "best-practices-for-securing-your-ico",
"voter": "khryaevao",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-23T08:40:06",
"trx_id": "7fe2a54055eaf1186720027a7690e4814c2a6a3e",
"trx_in_block": 6,
"virtual_op": 0
}mbiketovupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico2018/04/23 08:39:45
mbiketovupvoted (100.00%) @turingsafe / best-practices-for-securing-your-ico
2018/04/23 08:39:45
| author | turingsafe |
| permlink | best-practices-for-securing-your-ico |
| voter | mbiketov |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21814277/Trx 6d896d1a8fee01496c63ffc251cebff3967f5481 |
View Raw JSON Data
{
"block": 21814277,
"op": [
"vote",
{
"author": "turingsafe",
"permlink": "best-practices-for-securing-your-ico",
"voter": "mbiketov",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-23T08:39:45",
"trx_id": "6d896d1a8fee01496c63ffc251cebff3967f5481",
"trx_in_block": 0,
"virtual_op": 0
}Manabar
Voting Power100.00%
Downvote Power100.00%
Resource Credits100.00%
Reputation Progress0.00%
{
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779090192
},
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779090192
},
"rc_account": {
"account": "turingsafe",
"max_rc": "10164408779",
"max_rc_creation_adjustment": {
"amount": "2020748973",
"nai": "@@000000037",
"precision": 6
},
"rc_manabar": {
"current_mana": "10164408779",
"last_update_time": 1779090192
}
}
}Account Metadata
| POSTING JSON METADATA | |
| profile | {"name":"Turing Labs","website":"https://www.turinglabs.io"} |
| JSON METADATA | |
| profile | {"name":"Turing Labs","website":"https://www.turinglabs.io"} |
{
"posting_json_metadata": {
"profile": {
"name": "Turing Labs",
"website": "https://www.turinglabs.io"
}
},
"json_metadata": {
"profile": {
"name": "Turing Labs",
"website": "https://www.turinglabs.io"
}
}
}Auth Keys
Owner
Single Signature
Public Keys
STM79naTYxEmqZboyDfo84uQKhxeYaexbPN5KrUrrUKXLbhk5e7771/1
Active
Single Signature
Public Keys
STM7dXwndDe18F4jYA35JphQSFGySnh8r4tvJodauFWjwmYVvy2Yt1/1
Posting
Single Signature
Public Keys
STM74HpaPCCzgpUBp7N226bJfXee3oQmFyWkkhZ7fwvY7CWzoR8SJ1/1
Memo
STM5JCVTuQpALTQ56RZZRFYSgT5SXv28m8t8j1nkTsBweRJxJq5Ku
{
"owner": {
"account_auths": [],
"key_auths": [
[
"STM79naTYxEmqZboyDfo84uQKhxeYaexbPN5KrUrrUKXLbhk5e777",
1
]
],
"weight_threshold": 1
},
"active": {
"account_auths": [],
"key_auths": [
[
"STM7dXwndDe18F4jYA35JphQSFGySnh8r4tvJodauFWjwmYVvy2Yt",
1
]
],
"weight_threshold": 1
},
"posting": {
"account_auths": [],
"key_auths": [
[
"STM74HpaPCCzgpUBp7N226bJfXee3oQmFyWkkhZ7fwvY7CWzoR8SJ",
1
]
],
"weight_threshold": 1
},
"memo": "STM5JCVTuQpALTQ56RZZRFYSgT5SXv28m8t8j1nkTsBweRJxJq5Ku"
}Witness Votes
0 / 30
No active witness votes.
[]