Ecoer Logo
VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS0.00%
Net Worth
0.037USD
STEEM
0.000STEEM
SBD
0.000SBD
Effective Power
5.007SP
├── Own SP
0.632SP
└── Incoming Deleg
+4.375SP

Detailed Balance

STEEM
balance
0.000STEEM
market_balance
0.000STEEM
savings_balance
0.000STEEM
reward_steem_balance
0.000STEEM
STEEM POWER
Own SP
0.632SP
Delegated Out
0.000SP
Delegation In
4.375SP
Effective Power
5.007SP
Reward SP (pending)
0.000SP
SBD
sbd_balance
0.000SBD
sbd_conversions
0.000SBD
sbd_market_balance
0.000SBD
savings_sbd_balance
0.000SBD
reward_sbd_balance
0.000SBD
{
  "balance": "0.000 STEEM",
  "savings_balance": "0.000 STEEM",
  "reward_steem_balance": "0.000 STEEM",
  "vesting_shares": "1027.256295 VESTS",
  "delegated_vesting_shares": "0.000000 VESTS",
  "received_vesting_shares": "7116.403511 VESTS",
  "sbd_balance": "0.000 SBD",
  "savings_sbd_balance": "0.000 SBD",
  "reward_sbd_balance": "0.000 SBD",
  "conversions": []
}

Account Info

namenethamdotsh
id436540
rank1,443,647
reputation18133517
created2017-11-10T13:23:45
recovery_accountsteem
proxyNone
post_count2
comment_count0
lifetime_vote_count0
witnesses_voted_for0
last_post2017-11-14T04:04:45
last_root_post2017-11-13T19:03:48
last_vote_time2017-11-14T04:03:33
proxied_vsf_votes0, 0, 0, 0
can_vote1
voting_power0
delayed_votes0
balance0.000 STEEM
savings_balance0.000 STEEM
sbd_balance0.000 SBD
savings_sbd_balance0.000 SBD
vesting_shares1027.256295 VESTS
delegated_vesting_shares0.000000 VESTS
received_vesting_shares7116.403511 VESTS
reward_vesting_balance0.000000 VESTS
vesting_balance0.000 STEEM
vesting_withdraw_rate0.000000 VESTS
next_vesting_withdrawal1969-12-31T23:59:59
withdrawn0
to_withdraw0
withdraw_routes0
savings_withdraw_requests0
last_account_recovery1970-01-01T00:00:00
reset_accountnull
last_owner_update1970-01-01T00:00:00
last_account_update1970-01-01T00:00:00
minedNo
sbd_seconds0
sbd_last_interest_payment1970-01-01T00:00:00
savings_sbd_last_interest_payment1970-01-01T00:00:00
{
  "id": 436540,
  "name": "nethamdotsh",
  "owner": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM8LCVi8VtjUsKutr5UceGkzALEq2NmJfHxSFkPJqKXhv6dh5FmJ",
        1
      ]
    ]
  },
  "active": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM64w8A8S3K7uormof1pZz63KqRQFs7F3tyDFNwC5rDeERudMV2b",
        1
      ]
    ]
  },
  "posting": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM7aUTF3mbtyiqCecm2XU8ofwPURxvZKb65Y8mFN5xgJZqU6WzHS",
        1
      ]
    ]
  },
  "memo_key": "STM5iALwPbHyyjALmEqPh8MtL2ArrXZMGBUraJdHL1Li3cK8XAKHg",
  "json_metadata": "",
  "posting_json_metadata": "",
  "proxy": "",
  "last_owner_update": "1970-01-01T00:00:00",
  "last_account_update": "1970-01-01T00:00:00",
  "created": "2017-11-10T13:23:45",
  "mined": false,
  "recovery_account": "steem",
  "last_account_recovery": "1970-01-01T00:00:00",
  "reset_account": "null",
  "comment_count": 0,
  "lifetime_vote_count": 0,
  "post_count": 2,
  "can_vote": true,
  "voting_manabar": {
    "current_mana": "8143659806",
    "last_update_time": 1779078276
  },
  "downvote_manabar": {
    "current_mana": 2035914951,
    "last_update_time": 1779078276
  },
  "voting_power": 0,
  "balance": "0.000 STEEM",
  "savings_balance": "0.000 STEEM",
  "sbd_balance": "0.000 SBD",
  "sbd_seconds": "0",
  "sbd_seconds_last_update": "1970-01-01T00:00:00",
  "sbd_last_interest_payment": "1970-01-01T00:00:00",
  "savings_sbd_balance": "0.000 SBD",
  "savings_sbd_seconds": "0",
  "savings_sbd_seconds_last_update": "1970-01-01T00:00:00",
  "savings_sbd_last_interest_payment": "1970-01-01T00:00:00",
  "savings_withdraw_requests": 0,
  "reward_sbd_balance": "0.000 SBD",
  "reward_steem_balance": "0.000 STEEM",
  "reward_vesting_balance": "0.000000 VESTS",
  "reward_vesting_steem": "0.000 STEEM",
  "vesting_shares": "1027.256295 VESTS",
  "delegated_vesting_shares": "0.000000 VESTS",
  "received_vesting_shares": "7116.403511 VESTS",
  "vesting_withdraw_rate": "0.000000 VESTS",
  "next_vesting_withdrawal": "1969-12-31T23:59:59",
  "withdrawn": 0,
  "to_withdraw": 0,
  "withdraw_routes": 0,
  "curation_rewards": 0,
  "posting_rewards": 0,
  "proxied_vsf_votes": [
    0,
    0,
    0,
    0
  ],
  "witnesses_voted_for": 0,
  "last_post": "2017-11-14T04:04:45",
  "last_root_post": "2017-11-13T19:03:48",
  "last_vote_time": "2017-11-14T04:03:33",
  "post_bandwidth": 0,
  "pending_claimed_accounts": 0,
  "vesting_balance": "0.000 STEEM",
  "reputation": 18133517,
  "transfer_history": [],
  "market_history": [],
  "post_history": [],
  "vote_history": [],
  "other_history": [],
  "witness_votes": [],
  "tags_usage": [],
  "guest_bloggers": [],
  "rank": 1443647
}

Withdraw Routes

IncomingOutgoing
Empty
Empty
{
  "incoming": [],
  "outgoing": []
}
From Date
To Date
steemdelegated 4.375 SP to @nethamdotsh
2026/05/18 04:24:36
delegatorsteem
delegateenethamdotsh
vesting shares7116.403511 VESTS
Transaction InfoBlock #106148412/Trx 14523e219c5949d9e9a8ca9247b7141c962b6604
View Raw JSON Data
{
  "trx_id": "14523e219c5949d9e9a8ca9247b7141c962b6604",
  "block": 106148412,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2026-05-18T04:24:36",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "nethamdotsh",
      "vesting_shares": "7116.403511 VESTS"
    }
  ]
}
steemdelegated 2.708 SP to @nethamdotsh
2026/05/12 20:41:39
delegatorsteem
delegateenethamdotsh
vesting shares4404.193106 VESTS
Transaction InfoBlock #105995891/Trx 6bd8cb169804b136d3612533f44cacae174b26aa
View Raw JSON Data
{
  "trx_id": "6bd8cb169804b136d3612533f44cacae174b26aa",
  "block": 105995891,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2026-05-12T20:41:39",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "nethamdotsh",
      "vesting_shares": "4404.193106 VESTS"
    }
  ]
}
steemdelegated 4.383 SP to @nethamdotsh
2026/04/26 03:38:57
delegatorsteem
delegateenethamdotsh
vesting shares7128.919267 VESTS
Transaction InfoBlock #105515946/Trx ca3d902a6b5290f405cb9c83ab4edf089e42a0cc
View Raw JSON Data
{
  "trx_id": "ca3d902a6b5290f405cb9c83ab4edf089e42a0cc",
  "block": 105515946,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2026-04-26T03:38:57",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "nethamdotsh",
      "vesting_shares": "7128.919267 VESTS"
    }
  ]
}
steemdelegated 2.733 SP to @nethamdotsh
2026/01/23 18:57:48
delegatorsteem
delegateenethamdotsh
vesting shares4445.739925 VESTS
Transaction InfoBlock #102865184/Trx 3c3bacb61e5d697e75428aa233024db0b208659e
View Raw JSON Data
{
  "trx_id": "3c3bacb61e5d697e75428aa233024db0b208659e",
  "block": 102865184,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2026-01-23T18:57:48",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "nethamdotsh",
      "vesting_shares": "4445.739925 VESTS"
    }
  ]
}
steemdelegated 2.834 SP to @nethamdotsh
2024/12/17 14:09:30
delegatorsteem
delegateenethamdotsh
vesting shares4609.959122 VESTS
Transaction InfoBlock #91311431/Trx e9b35469267dadaae164d56ffb0348b9336fc30e
View Raw JSON Data
{
  "trx_id": "e9b35469267dadaae164d56ffb0348b9336fc30e",
  "block": 91311431,
  "trx_in_block": 3,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2024-12-17T14:09:30",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "nethamdotsh",
      "vesting_shares": "4609.959122 VESTS"
    }
  ]
}
steemdelegated 2.938 SP to @nethamdotsh
2023/11/14 05:51:12
delegatorsteem
delegateenethamdotsh
vesting shares4779.092654 VESTS
Transaction InfoBlock #79865601/Trx 13e59278fd92a42415ef8559996bdd74f4984fc0
View Raw JSON Data
{
  "trx_id": "13e59278fd92a42415ef8559996bdd74f4984fc0",
  "block": 79865601,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2023-11-14T05:51:12",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "nethamdotsh",
      "vesting_shares": "4779.092654 VESTS"
    }
  ]
}
steemdelegated 4.744 SP to @nethamdotsh
2023/09/22 08:09:39
delegatorsteem
delegateenethamdotsh
vesting shares7716.001440 VESTS
Transaction InfoBlock #78360198/Trx 0fb46775fd96e4967677d500a6d5a3b1de65d0b8
View Raw JSON Data
{
  "trx_id": "0fb46775fd96e4967677d500a6d5a3b1de65d0b8",
  "block": 78360198,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2023-09-22T08:09:39",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "nethamdotsh",
      "vesting_shares": "7716.001440 VESTS"
    }
  ]
}
steemdelegated 4.880 SP to @nethamdotsh
2022/11/03 15:55:06
delegatorsteem
delegateenethamdotsh
vesting shares7938.052878 VESTS
Transaction InfoBlock #69118295/Trx f3121a99ca96635d8ea46d51a08738b45c7f0e10
View Raw JSON Data
{
  "trx_id": "f3121a99ca96635d8ea46d51a08738b45c7f0e10",
  "block": 69118295,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-11-03T15:55:06",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "nethamdotsh",
      "vesting_shares": "7938.052878 VESTS"
    }
  ]
}
steemdelegated 5.016 SP to @nethamdotsh
2022/01/17 21:17:51
delegatorsteem
delegateenethamdotsh
vesting shares8158.160479 VESTS
Transaction InfoBlock #60821759/Trx 3aa536be59fe6c22a046a3bd4667e8f6a4d74d2e
View Raw JSON Data
{
  "trx_id": "3aa536be59fe6c22a046a3bd4667e8f6a4d74d2e",
  "block": 60821759,
  "trx_in_block": 34,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-01-17T21:17:51",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "nethamdotsh",
      "vesting_shares": "8158.160479 VESTS"
    }
  ]
}
steemdelegated 5.129 SP to @nethamdotsh
2021/06/14 04:33:39
delegatorsteem
delegateenethamdotsh
vesting shares8342.354767 VESTS
Transaction InfoBlock #54612190/Trx 1049dfa586693290336af6122fbf860ca25805cd
View Raw JSON Data
{
  "trx_id": "1049dfa586693290336af6122fbf860ca25805cd",
  "block": 54612190,
  "trx_in_block": 3,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-06-14T04:33:39",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "nethamdotsh",
      "vesting_shares": "8342.354767 VESTS"
    }
  ]
}
steemdelegated 5.244 SP to @nethamdotsh
2020/12/11 14:47:42
delegatorsteem
delegateenethamdotsh
vesting shares8529.776741 VESTS
Transaction InfoBlock #49359504/Trx bb06d642b757255426f895c1ef11dc2f2b2b5d00
View Raw JSON Data
{
  "trx_id": "bb06d642b757255426f895c1ef11dc2f2b2b5d00",
  "block": 49359504,
  "trx_in_block": 5,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-12-11T14:47:42",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "nethamdotsh",
      "vesting_shares": "8529.776741 VESTS"
    }
  ]
}
steemdelegated 1.176 SP to @nethamdotsh
2020/12/06 08:24:00
delegatorsteem
delegateenethamdotsh
vesting shares1912.543513 VESTS
Transaction InfoBlock #49211045/Trx 9f96ca94f1b155c20d0f83708ba140f984bb58b9
View Raw JSON Data
{
  "trx_id": "9f96ca94f1b155c20d0f83708ba140f984bb58b9",
  "block": 49211045,
  "trx_in_block": 14,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-12-06T08:24:00",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "nethamdotsh",
      "vesting_shares": "1912.543513 VESTS"
    }
  ]
}
steemdelegated 5.248 SP to @nethamdotsh
2020/12/05 18:25:21
delegatorsteem
delegateenethamdotsh
vesting shares8535.984595 VESTS
Transaction InfoBlock #49194589/Trx bc28a2a8d178b5200aa044cb72d2511beeaba5ff
View Raw JSON Data
{
  "trx_id": "bc28a2a8d178b5200aa044cb72d2511beeaba5ff",
  "block": 49194589,
  "trx_in_block": 8,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-12-05T18:25:21",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "nethamdotsh",
      "vesting_shares": "8535.984595 VESTS"
    }
  ]
}
steemdelegated 1.180 SP to @nethamdotsh
2020/11/02 23:13:54
delegatorsteem
delegateenethamdotsh
vesting shares1920.017158 VESTS
Transaction InfoBlock #48266747/Trx 41e7772bbf3389312f7680aa3bc613d5532d490b
View Raw JSON Data
{
  "trx_id": "41e7772bbf3389312f7680aa3bc613d5532d490b",
  "block": 48266747,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-11-02T23:13:54",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "nethamdotsh",
      "vesting_shares": "1920.017158 VESTS"
    }
  ]
}
steemdelegated 5.373 SP to @nethamdotsh
2020/05/09 09:25:00
delegatorsteem
delegateenethamdotsh
vesting shares8738.789954 VESTS
Transaction InfoBlock #43221344/Trx 557d3f80f81918a3cd4060e7aea158c1531caaf0
View Raw JSON Data
{
  "trx_id": "557d3f80f81918a3cd4060e7aea158c1531caaf0",
  "block": 43221344,
  "trx_in_block": 9,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-05-09T09:25:00",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "nethamdotsh",
      "vesting_shares": "8738.789954 VESTS"
    }
  ]
}
steemdelegated 1.201 SP to @nethamdotsh
2020/05/08 13:34:27
delegatorsteem
delegateenethamdotsh
vesting shares1953.311140 VESTS
Transaction InfoBlock #43198092/Trx f4d72bd57ab62f357200685bfd0cd24b7330d2c4
View Raw JSON Data
{
  "trx_id": "f4d72bd57ab62f357200685bfd0cd24b7330d2c4",
  "block": 43198092,
  "trx_in_block": 14,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-05-08T13:34:27",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "nethamdotsh",
      "vesting_shares": "1953.311140 VESTS"
    }
  ]
}
steemdelegated 5.380 SP to @nethamdotsh
2020/04/16 02:14:00
delegatorsteem
delegateenethamdotsh
vesting shares8751.677402 VESTS
Transaction InfoBlock #42567920/Trx e7f8203cbab93de53463b43d42b0bc9973c68658
View Raw JSON Data
{
  "trx_id": "e7f8203cbab93de53463b43d42b0bc9973c68658",
  "block": 42567920,
  "trx_in_block": 5,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-04-16T02:14:00",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "nethamdotsh",
      "vesting_shares": "8751.677402 VESTS"
    }
  ]
}
2019/11/10 14:28:27
parent authornethamdotsh
parent permlinkbuilding-a-crypto-trading-bot-a-beginner-s-attempt-part-1
authorsteemitboard
permlinksteemitboard-notify-nethamdotsh-20191110t142827000z
title
bodyCongratulations @nethamdotsh! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@nethamdotsh/birthday2.png</td><td>Happy Birthday! - You are on the Steem blockchain for 2 years!</td></tr></table> <sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@nethamdotsh) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=nethamdotsh)_</sub> **Do not miss the last post from @steemitboard:** <table><tr><td><a href="https://steemit.com/steemfest/@steemitboard/steemfest-meet-the-stemians-contest-the-mysterious-rule-revealed"><img src="https://steemitimages.com/64x128/https://cdn.steemitimages.com/DQmasWw4jQHwxng82DKxY6Q6tVg9mWcto4xcDURs8knFgCa/image.png"></a></td><td><a href="https://steemit.com/steemfest/@steemitboard/steemfest-meet-the-stemians-contest-the-mysterious-rule-revealed">SteemFest Meet The Stemians Contest - The mysterious rule revealed</a></td></tr></table> ###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!
json metadata{"image":["https://steemitboard.com/img/notify.png"]}
Transaction InfoBlock #38054849/Trx 63004b980e385e3f6caf9baac165f8a78118f5ec
View Raw JSON Data
{
  "trx_id": "63004b980e385e3f6caf9baac165f8a78118f5ec",
  "block": 38054849,
  "trx_in_block": 5,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-11-10T14:28:27",
  "op": [
    "comment",
    {
      "parent_author": "nethamdotsh",
      "parent_permlink": "building-a-crypto-trading-bot-a-beginner-s-attempt-part-1",
      "author": "steemitboard",
      "permlink": "steemitboard-notify-nethamdotsh-20191110t142827000z",
      "title": "",
      "body": "Congratulations @nethamdotsh! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@nethamdotsh/birthday2.png</td><td>Happy Birthday! - You are on the Steem blockchain for 2 years!</td></tr></table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@nethamdotsh) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=nethamdotsh)_</sub>\n\n\n**Do not miss the last post from @steemitboard:**\n<table><tr><td><a href=\"https://steemit.com/steemfest/@steemitboard/steemfest-meet-the-stemians-contest-the-mysterious-rule-revealed\"><img src=\"https://steemitimages.com/64x128/https://cdn.steemitimages.com/DQmasWw4jQHwxng82DKxY6Q6tVg9mWcto4xcDURs8knFgCa/image.png\"></a></td><td><a href=\"https://steemit.com/steemfest/@steemitboard/steemfest-meet-the-stemians-contest-the-mysterious-rule-revealed\">SteemFest Meet The Stemians Contest - The mysterious rule revealed</a></td></tr></table>\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
      "json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}"
    }
  ]
}
steemdelegated 5.501 SP to @nethamdotsh
2019/05/12 19:20:33
delegatorsteem
delegateenethamdotsh
vesting shares8947.294215 VESTS
Transaction InfoBlock #32850812/Trx 4d46aebb3de067da0070f3eed43ae34703643cb0
View Raw JSON Data
{
  "trx_id": "4d46aebb3de067da0070f3eed43ae34703643cb0",
  "block": 32850812,
  "trx_in_block": 42,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-05-12T19:20:33",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "nethamdotsh",
      "vesting_shares": "8947.294215 VESTS"
    }
  ]
}
2018/11/10 14:53:15
parent authornethamdotsh
parent permlinkbuilding-a-crypto-trading-bot-a-beginner-s-attempt-part-1
authorsteemitboard
permlinksteemitboard-notify-nethamdotsh-20181110t145314000z
title
bodyCongratulations @nethamdotsh! You have received a personal award! [![](https://steemitimages.com/70x70/http://steemitboard.com/@nethamdotsh/birthday1.png)](http://steemitboard.com/@nethamdotsh) 1 Year on Steemit <sub>_Click on the badge to view your Board of Honor._</sub> **Do not miss the last post from @steemitboard:** <table><tr><td><a href="https://steemit.com/steemfest/@steemitboard/steemfest3-and-steemitboard-meet-the-steemians-contest"><img src="https://steemitimages.com/64x128/https://cdn.steemitimages.com/DQmeLukvNFRsa7RURqsFpiLGEZZD49MiU52JtWmjS5S2wtW/image.png"></a></td><td><a href="https://steemit.com/steemfest/@steemitboard/steemfest3-and-steemitboard-meet-the-steemians-contest">SteemFest3 and SteemitBoard - Meet the Steemians Contest</a></td></tr></table> > Support [SteemitBoard's project](https://steemit.com/@steemitboard)! **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**!
json metadata{"image":["https://steemitboard.com/img/notify.png"]}
Transaction InfoBlock #27580283/Trx f0a2e1181239835bdb1be96f63571114efafde6a
View Raw JSON Data
{
  "trx_id": "f0a2e1181239835bdb1be96f63571114efafde6a",
  "block": 27580283,
  "trx_in_block": 5,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-11-10T14:53:15",
  "op": [
    "comment",
    {
      "parent_author": "nethamdotsh",
      "parent_permlink": "building-a-crypto-trading-bot-a-beginner-s-attempt-part-1",
      "author": "steemitboard",
      "permlink": "steemitboard-notify-nethamdotsh-20181110t145314000z",
      "title": "",
      "body": "Congratulations @nethamdotsh! You have received a personal award!\n\n[![](https://steemitimages.com/70x70/http://steemitboard.com/@nethamdotsh/birthday1.png)](http://steemitboard.com/@nethamdotsh)  1 Year on Steemit\n<sub>_Click on the badge to view your Board of Honor._</sub>\n\n\n**Do not miss the last post from @steemitboard:**\n<table><tr><td><a href=\"https://steemit.com/steemfest/@steemitboard/steemfest3-and-steemitboard-meet-the-steemians-contest\"><img src=\"https://steemitimages.com/64x128/https://cdn.steemitimages.com/DQmeLukvNFRsa7RURqsFpiLGEZZD49MiU52JtWmjS5S2wtW/image.png\"></a></td><td><a href=\"https://steemit.com/steemfest/@steemitboard/steemfest3-and-steemitboard-meet-the-steemians-contest\">SteemFest3 and SteemitBoard - Meet the Steemians Contest</a></td></tr></table>\n\n> Support [SteemitBoard's project](https://steemit.com/@steemitboard)! **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**!",
      "json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}"
    }
  ]
}
2018/06/29 01:37:39
voterbushman
authornethamdotsh
permlinkbuilding-a-crypto-trading-bot-a-beginner-s-attempt-part-1
weight10000 (100.00%)
Transaction InfoBlock #23733381/Trx 0374f4c2da735b9ebce2deada604dd8bbb688731
View Raw JSON Data
{
  "trx_id": "0374f4c2da735b9ebce2deada604dd8bbb688731",
  "block": 23733381,
  "trx_in_block": 37,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-29T01:37:39",
  "op": [
    "vote",
    {
      "voter": "bushman",
      "author": "nethamdotsh",
      "permlink": "building-a-crypto-trading-bot-a-beginner-s-attempt-part-1",
      "weight": 10000
    }
  ]
}
steemdelegated 5.623 SP to @nethamdotsh
2018/05/16 23:19:03
delegatorsteem
delegateenethamdotsh
vesting shares9146.905083 VESTS
Transaction InfoBlock #22493482/Trx fb01e04004e2069c075b63a7a7cab680ea309210
View Raw JSON Data
{
  "trx_id": "fb01e04004e2069c075b63a7a7cab680ea309210",
  "block": 22493482,
  "trx_in_block": 34,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-05-16T23:19:03",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "nethamdotsh",
      "vesting_shares": "9146.905083 VESTS"
    }
  ]
}
2018/04/21 23:18:51
parent authornethamdotsh
parent permlinkbuilding-a-crypto-trading-bot-a-beginner-s-attempt-part-1
authorproseries
permlinkre-nethamdotsh-building-a-crypto-trading-bot-a-beginner-s-attempt-part-1-20180421t231852799z
title
bodyCan you build me a bot to trade crypto? Please contact me at [email protected]
json metadata{"tags":["cryptocurrency"],"app":"steemit/0.1"}
Transaction InfoBlock #21774264/Trx f4de662fb4bd5bb326cf782684effa9abaaa0c1d
View Raw JSON Data
{
  "trx_id": "f4de662fb4bd5bb326cf782684effa9abaaa0c1d",
  "block": 21774264,
  "trx_in_block": 34,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-04-21T23:18:51",
  "op": [
    "comment",
    {
      "parent_author": "nethamdotsh",
      "parent_permlink": "building-a-crypto-trading-bot-a-beginner-s-attempt-part-1",
      "author": "proseries",
      "permlink": "re-nethamdotsh-building-a-crypto-trading-bot-a-beginner-s-attempt-part-1-20180421t231852799z",
      "title": "",
      "body": "Can you build me a bot to trade crypto? Please contact me at [email protected]",
      "json_metadata": "{\"tags\":[\"cryptocurrency\"],\"app\":\"steemit/0.1\"}"
    }
  ]
}
steemdelegated 18.158 SP to @nethamdotsh
2018/04/21 20:49:21
delegatorsteem
delegateenethamdotsh
vesting shares29534.911653 VESTS
Transaction InfoBlock #21771275/Trx 8c95a17c26f6b00ad5e22d230263ac57e0fae6f4
View Raw JSON Data
{
  "trx_id": "8c95a17c26f6b00ad5e22d230263ac57e0fae6f4",
  "block": 21771275,
  "trx_in_block": 29,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-04-21T20:49:21",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "nethamdotsh",
      "vesting_shares": "29534.911653 VESTS"
    }
  ]
}
2018/04/10 14:33:00
votermgpeng
authornethamdotsh
permlinkbuilding-a-crypto-trading-bot-a-beginner-s-attempt-part-1
weight9900 (99.00%)
Transaction InfoBlock #21447003/Trx 234c4b69aa2ee6c632c7dc9329de00ea76cabc1a
View Raw JSON Data
{
  "trx_id": "234c4b69aa2ee6c632c7dc9329de00ea76cabc1a",
  "block": 21447003,
  "trx_in_block": 41,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-04-10T14:33:00",
  "op": [
    "vote",
    {
      "voter": "mgpeng",
      "author": "nethamdotsh",
      "permlink": "building-a-crypto-trading-bot-a-beginner-s-attempt-part-1",
      "weight": 9900
    }
  ]
}
2018/03/24 19:13:24
voterrondellrandall
authornethamdotsh
permlinkbuilding-a-crypto-trading-bot-a-beginner-s-attempt-part-1
weight10000 (100.00%)
Transaction InfoBlock #20963116/Trx 9c6ae473bd7f294dca1d80cf0bc747e14d5e784f
View Raw JSON Data
{
  "trx_id": "9c6ae473bd7f294dca1d80cf0bc747e14d5e784f",
  "block": 20963116,
  "trx_in_block": 23,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-03-24T19:13:24",
  "op": [
    "vote",
    {
      "voter": "rondellrandall",
      "author": "nethamdotsh",
      "permlink": "building-a-crypto-trading-bot-a-beginner-s-attempt-part-1",
      "weight": 10000
    }
  ]
}
2018/02/08 15:08:42
voterarnaudmalfoy
authornethamdotsh
permlinkbuilding-a-crypto-trading-bot-a-beginner-s-attempt-part-1
weight10000 (100.00%)
Transaction InfoBlock #19692873/Trx 99807414e515ce5f743a7220165ea798644c50fa
View Raw JSON Data
{
  "trx_id": "99807414e515ce5f743a7220165ea798644c50fa",
  "block": 19692873,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-02-08T15:08:42",
  "op": [
    "vote",
    {
      "voter": "arnaudmalfoy",
      "author": "nethamdotsh",
      "permlink": "building-a-crypto-trading-bot-a-beginner-s-attempt-part-1",
      "weight": 10000
    }
  ]
}
2018/01/11 16:40:15
voterterecoin
authornethamdotsh
permlinkbuilding-a-crypto-trading-bot-a-beginner-s-attempt-part-1
weight10000 (100.00%)
Transaction InfoBlock #18889177/Trx 61ecbfb2b59421107347dcc74a30c2513a2bfe1d
View Raw JSON Data
{
  "trx_id": "61ecbfb2b59421107347dcc74a30c2513a2bfe1d",
  "block": 18889177,
  "trx_in_block": 3,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-01-11T16:40:15",
  "op": [
    "vote",
    {
      "voter": "terecoin",
      "author": "nethamdotsh",
      "permlink": "building-a-crypto-trading-bot-a-beginner-s-attempt-part-1",
      "weight": 10000
    }
  ]
}
steemdelegated 18.283 SP to @nethamdotsh
2017/12/12 22:22:09
delegatorsteem
delegateenethamdotsh
vesting shares29738.743705 VESTS
Transaction InfoBlock #18032626/Trx 92d585c22fbd42a6d1feaac1483a8880d4fa5d27
View Raw JSON Data
{
  "trx_id": "92d585c22fbd42a6d1feaac1483a8880d4fa5d27",
  "block": 18032626,
  "trx_in_block": 23,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-12-12T22:22:09",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "nethamdotsh",
      "vesting_shares": "29738.743705 VESTS"
    }
  ]
}
2017/11/14 04:04:45
parent authorbismark1
parent permlinkre-nethamdotsh-building-a-crypto-trading-bot-a-beginner-s-attempt-part-1-20171113t190543484z
authornethamdotsh
permlinkre-bismark1-re-nethamdotsh-building-a-crypto-trading-bot-a-beginner-s-attempt-part-1-20171114t040445344z
title
bodyThe power of human innovation, networks and free markets.
json metadata{"tags":["cryptocurrency"],"app":"steemit/0.1"}
Transaction InfoBlock #17204637/Trx 4bf1a5212cbf3822ad70592f97c4986788592bbc
View Raw JSON Data
{
  "trx_id": "4bf1a5212cbf3822ad70592f97c4986788592bbc",
  "block": 17204637,
  "trx_in_block": 13,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-11-14T04:04:45",
  "op": [
    "comment",
    {
      "parent_author": "bismark1",
      "parent_permlink": "re-nethamdotsh-building-a-crypto-trading-bot-a-beginner-s-attempt-part-1-20171113t190543484z",
      "author": "nethamdotsh",
      "permlink": "re-bismark1-re-nethamdotsh-building-a-crypto-trading-bot-a-beginner-s-attempt-part-1-20171114t040445344z",
      "title": "",
      "body": "The power of human innovation, networks and free markets.",
      "json_metadata": "{\"tags\":[\"cryptocurrency\"],\"app\":\"steemit/0.1\"}"
    }
  ]
}
2017/11/14 04:03:33
voternethamdotsh
authornethamdotsh
permlinkbuilding-a-crypto-trading-bot-a-beginner-s-attempt-part-1
weight10000 (100.00%)
Transaction InfoBlock #17204613/Trx 0fcaad8813a5f4bf8f22c5782d819e2fdcefb901
View Raw JSON Data
{
  "trx_id": "0fcaad8813a5f4bf8f22c5782d819e2fdcefb901",
  "block": 17204613,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-11-14T04:03:33",
  "op": [
    "vote",
    {
      "voter": "nethamdotsh",
      "author": "nethamdotsh",
      "permlink": "building-a-crypto-trading-bot-a-beginner-s-attempt-part-1",
      "weight": 10000
    }
  ]
}
2017/11/13 19:06:39
parent authornethamdotsh
parent permlinkbuilding-a-crypto-trading-bot-a-beginner-s-attempt-part-1
authorbismark1
permlinkre-nethamdotsh-building-a-crypto-trading-bot-a-beginner-s-attempt-part-1-20171113t190543484z
title
body@@ -175,8 +175,25 @@ billion. + %0A%0AIsn't amazing?
json metadata{"tags":["cryptocurrency"],"app":"steemit/0.1"}
Transaction InfoBlock #17193876/Trx fa3b72d5fca0d648d4a9464e69b3ce4c31a8f22f
View Raw JSON Data
{
  "trx_id": "fa3b72d5fca0d648d4a9464e69b3ce4c31a8f22f",
  "block": 17193876,
  "trx_in_block": 31,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-11-13T19:06:39",
  "op": [
    "comment",
    {
      "parent_author": "nethamdotsh",
      "parent_permlink": "building-a-crypto-trading-bot-a-beginner-s-attempt-part-1",
      "author": "bismark1",
      "permlink": "re-nethamdotsh-building-a-crypto-trading-bot-a-beginner-s-attempt-part-1-20171113t190543484z",
      "title": "",
      "body": "@@ -175,8 +175,25 @@\n billion.\n+ %0A%0AIsn't amazing?\n",
      "json_metadata": "{\"tags\":[\"cryptocurrency\"],\"app\":\"steemit/0.1\"}"
    }
  ]
}
2017/11/13 19:05:45
parent authornethamdotsh
parent permlinkbuilding-a-crypto-trading-bot-a-beginner-s-attempt-part-1
authorbismark1
permlinkre-nethamdotsh-building-a-crypto-trading-bot-a-beginner-s-attempt-part-1-20171113t190543484z
title
bodyBitcoin is booming, digital currency hedge funds are sprouting at the rate of two a week and the value of all cryptocurrencies has surged tenfold this year to more than $170 billion.
json metadata{"tags":["cryptocurrency"],"app":"steemit/0.1"}
Transaction InfoBlock #17193858/Trx 98584a5831b82fd59b6a47c7b0b8d2c39cd952d6
View Raw JSON Data
{
  "trx_id": "98584a5831b82fd59b6a47c7b0b8d2c39cd952d6",
  "block": 17193858,
  "trx_in_block": 19,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-11-13T19:05:45",
  "op": [
    "comment",
    {
      "parent_author": "nethamdotsh",
      "parent_permlink": "building-a-crypto-trading-bot-a-beginner-s-attempt-part-1",
      "author": "bismark1",
      "permlink": "re-nethamdotsh-building-a-crypto-trading-bot-a-beginner-s-attempt-part-1-20171113t190543484z",
      "title": "",
      "body": "Bitcoin is booming, digital currency hedge funds are sprouting at the rate of two a week and the value of all cryptocurrencies has surged tenfold this year to more than $170 billion.",
      "json_metadata": "{\"tags\":[\"cryptocurrency\"],\"app\":\"steemit/0.1\"}"
    }
  ]
}
2017/11/13 19:05:12
parent author
parent permlinkcryptocurrency
authornethamdotsh
permlinkbuilding-a-crypto-trading-bot-a-beginner-s-attempt-part-1
titleBuilding a Crypto Trading Bot : A beginner's attempt - Part 1
body@@ -3712,30 +3712,8 @@ %0A%0A -!%5BOrder Book example%5D (htt
json metadata{"tags":["cryptocurrency","trading","bot","bittrex","bitcoin"],"image":["https://i.imgur.com/upheC7h.png"],"links":["https://m.do.co/c/22764aaa6bbf","https://bittrex.com/Market/Index?MarketName=BTC-BCC","https://bittrex.com/Home/Api","https://bittrex.com/api/v1.1/public/getticker?market=BTC-BCC ","https://bittrex.com/api/v1.1/public/getorderbook?market=BTC-LTC&type=both ","https://bittrex.com/api/v1.1/public/getorderbook?market=BTC-LTTT&type=both ","https://bittrex.com/api/v1.1/public/getorderbook?market=BTC-LTC&type=random ","https://support.bittrex.com/hc/en-us/articles/202605394-Updates-to-Minimum-Trade-Sizes","https://github.com/ndri/python-bittrex/blob/master/bittrex.py","https://github.com/n0mad01/node.bittrex.api/blob/master/node.bittrex.api.js"],"app":"steemit/0.1","format":"markdown"}
Transaction InfoBlock #17193847/Trx 8bdc620e4ea827071b5fb65acbb7cd1ee6a7cc63
View Raw JSON Data
{
  "trx_id": "8bdc620e4ea827071b5fb65acbb7cd1ee6a7cc63",
  "block": 17193847,
  "trx_in_block": 11,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-11-13T19:05:12",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "cryptocurrency",
      "author": "nethamdotsh",
      "permlink": "building-a-crypto-trading-bot-a-beginner-s-attempt-part-1",
      "title": "Building a Crypto Trading Bot : A beginner's attempt - Part 1",
      "body": "@@ -3712,30 +3712,8 @@\n   %0A%0A\n-!%5BOrder Book example%5D \n (htt\n",
      "json_metadata": "{\"tags\":[\"cryptocurrency\",\"trading\",\"bot\",\"bittrex\",\"bitcoin\"],\"image\":[\"https://i.imgur.com/upheC7h.png\"],\"links\":[\"https://m.do.co/c/22764aaa6bbf\",\"https://bittrex.com/Market/Index?MarketName=BTC-BCC\",\"https://bittrex.com/Home/Api\",\"https://bittrex.com/api/v1.1/public/getticker?market=BTC-BCC \",\"https://bittrex.com/api/v1.1/public/getorderbook?market=BTC-LTC&type=both \",\"https://bittrex.com/api/v1.1/public/getorderbook?market=BTC-LTTT&type=both \",\"https://bittrex.com/api/v1.1/public/getorderbook?market=BTC-LTC&type=random \",\"https://support.bittrex.com/hc/en-us/articles/202605394-Updates-to-Minimum-Trade-Sizes\",\"https://github.com/ndri/python-bittrex/blob/master/bittrex.py\",\"https://github.com/n0mad01/node.bittrex.api/blob/master/node.bittrex.api.js\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}
2017/11/13 19:03:48
parent author
parent permlinkcryptocurrency
authornethamdotsh
permlinkbuilding-a-crypto-trading-bot-a-beginner-s-attempt-part-1
titleBuilding a Crypto Trading Bot : A beginner's attempt - Part 1
body## Introduction I don't have much knowledge about trading, I design and build things for a living. A friend asked me to spin up a bot for him. This will help beginners trying to build a trading bot. The design of the bot is strategy independent so you can plugin any strategy or a mix of strategies. I used Bittrex API but you can use any exchange API with this architecture. ##### What we will talk talk about * Few basics of trading (can be skipped) * Bittrex API * Architecture of the bot * Mechanics of bot * Adding strategies to the bot * What not to do * Things to keep in mind * Testing ##### What is not here * Strategies * HFT (you can use the architecture) * Scalability * How to get rich --- For people who are new to coding/development (rest can skip) ``` What I used to build the bot : PHP and MySQL Server: Ubuntu on DigitalOcean What tools you can use: Any language you are comfortable with or you are learning. This article is not language specific. You don't need to learn any complex frameworks. Don't go looking for frameworks if you are a beginner. Things you will need to know in any language you want to use: 1. How to make http requests and parse JSON 2. How to store and read data from a database 3. Running cronjobs and background tasks You can also contact me to build a bot for you. ``` You can get 10$ credit for digitalocean using my referral link <https://m.do.co/c/22764aaa6bbf> --- ## Basics of Trading I am discussing few basics, the minimum required to understand the rest of the post. If you have done trading before and understand the type of orders and partial orders, this can be skipped. #### ELI5 Trading simply means exchanging A for B (called BUY B) or B for A (called SELL B) in market A-B. e.g. In BTC-BCC market, if you place an order for exchange of BTC for BCC, you are placing a BUY BCC order, if you place an order for exchange of BCC for BTC, you are placing a SELL BCC order. To trade, you place a BUY or SELL order of type T (will come to types later) in the market for a quantity Q and Rate R (per unit price). If the quantity and rate of your order matches the requirements or conditions of another order of the opposite kind, a transaction takes place. The requirements and the conditions are determined by the type of order. Few terms: "Ask" - The lowest rate at which someone in the market A-B is ready to SELL B for "Bid" - The highest rate at which someone in the market A-B is ready to BUY B for "Last" - The rate at which the last transaction took place in the market #### Types of Order There are different types of orders which can be placed. We are discussing only two types here, because most APIs allow only these two * Market Order - When you want to buy or sell immediately but you don't care for the rate, you place a Market order. In this case you don't control how much you bought something for or for how much you sold it for. * Limit Order - When you want to set a maximum rate for your BUY order or a minimum rate for your SELL order, you place a Limit order where the maximum/minimum price is referred to as Limit e.g. You placed a Limit order to SELL 1 BCC FOR 0.005 BTC (Your Ask), but if the bid in the market is for 0.007 BTC, then your order will fetch you 0.007 BTC. If there is no bid in the market over 0.005, it won't sell. In Market Order, there is guarantee of fullfillment. In Limit Order type, there is a guarantee of price. More types of orders like Stop orders, All or None orders, Good till Cancelled etc. can be placed at the Exchange using their dashboard. I suggest read about them too. #### Order Book Below is a screenshot for the Order Book of BTC-BCC market. ![Order Book example] (https://i.imgur.com/upheC7h.png) It is a list of current Bids in descending order and Asks and in ascending order. So on the left you will see highest bid on the top and on the right you will see lowest ask on the top. When you will place a SELL or a BUY order it will show in the order book. As soon as an order gets complete, it disappears from the order book and goes into Market history. The blanks you see were the rows which were getting updated while I took the screenshot. This is sufficient for you to understand the API. But first go here <a href="https://bittrex.com/Market/Index?MarketName=BTC-BCC" target="_blank"> BTC-BCC Market</a> and spend few minutes looking at live action, look around the page and see if you understand most of it. ## Bittrex API Take a look at the Bittrex API - <a href="https://bittrex.com/Home/Api" target="_blank"> Bittrex API Documentation</a> If you are using any other exchange, the difference will be probably between endpoint names and flags. Few points to note for Bittrex : All requests are GET requests and gives data in JSON. There is always a "success" flag in each and every request, which is boolean so you should check it everytime you make a request. Bittrex has no way to tell you when something happened, like an order got completed in thar market (some APIs do that), you have to constantly make requests to find status of your order. Let's dive into playing around with the API and understanding more about it. The documentation starts with authentication but we will talk about that later. ### Public API Public API doesn't requires any sort of authentication. You can view these endpoints in your browser. #### Ticker **/public/getticker?market=** Ticker returns the most current Bid, Ask and Last rate for a market. The values will change every moment if lot of people are trading in the market. Let's find out the current Bid, Ask and Last of BTC-BCC market. <a href="https://bittrex.com/api/v1.1/public/getticker?market=BTC-BCC " target="_blank"> https://bittrex.com/api/v1.1/**public/getticker?market=**BTC-BCC </a>. Visit it again, and you might see different rates. #### Order Book **/public/getorderbook?market= ___ &type= ____** This endpoint gets the orderbook for the requested market. Type can have values as 'sell' : returns only sell order data, 'buy': returns only buy order data or 'both'. Check the order book of BTC-LTC market <a href="https://bittrex.com/api/v1.1/public/getorderbook?market=BTC-LTC&type=both " target="_blank"> https://bittrex.com/api/v1.1/**public/getorderbook?market=BTC-LTC&type=both**</a> Lets look at few different error messages: * When market is invalid, mostly happens in typos. <a href="https://bittrex.com/api/v1.1/public/getorderbook?market=BTC-LTTT&type=both " target="_blank"> https://bittrex.com/api/v1.1/public/getorderbook?market=BTC-**LTTT**&type=both</a> ` {"success":false,"message":"INVALID_MARKET","result":null} ` * When type is invalid. <a href="https://bittrex.com/api/v1.1/public/getorderbook?market=BTC-LTC&type=random " target="_blank"> https://bittrex.com/api/v1.1/public/getorderbook?market=BTC-LTC&type=**random**</a> ` {"success":false,"message":"TYPE_INVALID","result":null} ` Note the success flag is false in both the above requests. Similarly in the documentation there are other public endpoints like getmarketsummary, getcurrencies etc. Copy the links from the examples in the <a href="https://bittrex.com/Home/Api" target="_blank"> Bittrex API Documentation</a> and visit them in new tab to understand the structure of the data. ``` Task (for beginners) : Ping the BTC-BCC ticker endpoint every minute for 10 minutes and find % change in Bid and Ask per minute and total % change in 10 minutes. If you have never made GET requests before or parsed JSON, stop reading, and do this task. Comment below with your results and time and date. ``` ### Market API Market API endpoints are interaction points with the market. Using them you can place an order, cancel an order and look at your open orders. Open orders refer to orders which you have placed in the market but have not been fullfilled yet. These endpoints require authentication which we will talk in the end of this section. So you won't be able to test the endpoints right now, we will first understand the responses. Bittrex allows only limit type of orders to be placed for now (refer to the Basics of Trading section). It had market orders in the past but they are not available anymore. Note: the API endpoints below will be missing apikey parameter. They are required for Market API. We will add it when we learn about authentication. #### Limit Buy Order **/market/buylimit?market= ___ &quantity= __ &rate= ___** Suppose we want to buy 0.0032673 BCC at the rate of 0.001423 BTC, we will form our url like /market/buylimit?market=BTC-BCC&quantity=0.0032673&rate=0.001423 . The response looks like this: ``` { "success" : true, "message" : "", "result" : { "uuid" : "d402d53c-0d70-11e3-94b5-425231b86ab6" } } ``` The flag "success" is true, so our order got placed in the market. It returned a uuid (universally unique identifier) which represents our order ID in the market. To find out anything about the order we placed we will use this uuid. #### Limit Sell Order **/market/selllimit?market= ___ &quantity= __ &rate= ___** This returns response similar to limitbuy, a uuid. Note: Bittrex doesn't allows orders which have size less than 50,000 Satoshis. It gives you error message of "DUST\_TRADE\_DISALLOWED\_MIN\_VALUE\_50K\_SAT". [More info](https://support.bittrex.com/hc/en-us/articles/202605394-Updates-to-Minimum-Trade-Sizes) #### Points to keep in mind for fullfillment of orders * Remember the orders using the above endpoints are limit orders. A Limit Sell will get complete/fullfilled whenever the price in the market is higher than or equal to the rate you requested. A Limit Buy order will get complete whenever the price in the market is lower or equal to the rate you requested. * Placement of an order and fullfillment of an order are two different steps. The success message in the previous two discussed endpoints is a confirmation of successful placement of an order. * Sometimes your oder will get fullfilled partially only. e.g. You placed a LIMIT BUY order for 100 BCC at the rate 0.005. Someone else placed a SELL order at the same or lower rate, but had only say 20 BCC to sell. As soon as your order got fullfilled with 20 BCC, say the market went up. It will remain partially filled unless the market comes down or you cancel the order which will cancel the remaining order. #### Open Orders **/market/getopenorders** **/market/getopenorders?market= ___** Open orders returns the orders which have not been fullfilled, partially or completely. You can request for a specific market also. Below is the response we get. Look at the // comments below to understand more (they are not part of the response). ``` { "success" : true, "message" : "", "result" : [{ "Uuid" : null, "OrderUuid" : "09aa5bb6-8232-41aa-9b78-a5a1093e0211", "Exchange" : "BTC-LTC", "OrderType" : "LIMIT_SELL", "Quantity" : 5.00000000, "QuantityRemaining" : 5.00000000, "Limit" : 2.00000000, "CommissionPaid" : 0.00000000, "Price" : 0.00000000, "PricePerUnit" : null, "Opened" : "2014-07-09T03:55:48.77", "Closed" : null, "CancelInitiated" : false, "ImmediateOrCancel" : false, "IsConditional" : false, "Condition" : null, "ConditionTarget" : null }, { "Uuid" : null, "OrderUuid" : This is uuid which we got when placed the LIMIT SELL order. You can use this to search for your order. "Exchange" : Market "OrderType" : Type of order "Quantity" : The quantity you requested for "QuantityRemaining" : This tells how much is yet to be bought/sold. We will use this to find the status of our order. "Limit" : Your Limit Rate "CommissionPaid" : Comission of Bittrex which is 0.25% "Price" : The total price at which the order got fullfilled for. "PricePerUnit" : Price per unit at which the order got fullfilled for "Opened" : timestamp when bittrex placed your order "Closed" : timestamp when bittrex completed your order "CancelInitiated" : true if you cancelled the order but it has not been cancelled yet. The process is taking place. "ImmediateOrCancel" : Bittrex uses these flags and following ones when you place using Bittrex dashboard. "IsConditional" : false, "Condition" : null, "ConditionTarget" : null } ] } ``` So we can use this endpoint with QuantityRemaining key to check the status of the order and to find how much of the order got fullfilled. We will learn more on that later when we design the bot. ### Authentication This is specific to Bittrex. With an account on Bittrex you can create multiple API keys which can set to have different permissions. You will need API Key and API secret to make authenticated requests. To make an authenticated request, like for market APIs in Bittrex, apikey and nonce are appended to the url. Nonce is the current Unix timestamp. It is in seconds. e.g. Get Open orders request will become **/market/getopenorders?apikey=xxxxxxxx&nonce=yyyyyyyyy** When making this request, you also calculate HMAC hash of request url (containing nonce and key) and API secret and include it in the request under apisign header. A nice way is to make a function to which you can pass the a url append nonce and apikey inside the function and make a request with the hash. ``` function BittrexAuthRequest($url){ $apikey='xxx'; $apisecret='xxx'; $nonce=time(); $uri=$url.'&apikey='.$apikey.'&nonce='.$nonce; //appending apikey and nonce $sign=hash_hmac('sha512',$uri,$apisecret); //calculating hmac hash $ch = curl_init($uri); curl_setopt($ch, CURLOPT_HTTPHEADER, array('apisign:'.$sign)); //adding hash to the apisign $execResult = curl_exec($ch); $obj = json_decode($execResult); return $obj; } ``` Some of you might be new to headers so I am including examples in other languages [Python](https://github.com/ndri/python-bittrex/blob/master/bittrex.py) : Look at line 33 [Javascript](https://github.com/n0mad01/node.bittrex.api/blob/master/node.bittrex.api.js) : Check at line 81. Also note inclusion of external file at line 15 for calculating hmac. ``` Task (for beginners): Signup on Bittrex and create an API key. Code in the BittrexAuthRequest function in your own language and place a BUY order for 0.00000001 BCC at current Ask. Use Ticker to find the Ask. If you code it right, then the order will fail (because it is less than 50k Satoshis) and response message will be either 'Insufficient Funds' or DUST\_TRADE\_DISALLOWED\_MIN\_VALUE\_50K\_SAT ``` --------------- --------------- Part 2 coming soon. Follow to stay updated. If you liked this upvote. If you have questions or any suggestions, you can comment below. For consultation/development of trading bot or something similar you can contact me netham91+steemit [at] gmail with subject line containing '[Project]'
json metadata{"tags":["cryptocurrency","trading","bot","bittrex","bitcoin"],"image":["https://i.imgur.com/upheC7h.png"],"links":["https://m.do.co/c/22764aaa6bbf","https://bittrex.com/Market/Index?MarketName=BTC-BCC","https://bittrex.com/Home/Api","https://bittrex.com/api/v1.1/public/getticker?market=BTC-BCC ","https://bittrex.com/api/v1.1/public/getorderbook?market=BTC-LTC&type=both ","https://bittrex.com/api/v1.1/public/getorderbook?market=BTC-LTTT&type=both ","https://bittrex.com/api/v1.1/public/getorderbook?market=BTC-LTC&type=random ","https://support.bittrex.com/hc/en-us/articles/202605394-Updates-to-Minimum-Trade-Sizes","https://github.com/ndri/python-bittrex/blob/master/bittrex.py","https://github.com/n0mad01/node.bittrex.api/blob/master/node.bittrex.api.js"],"app":"steemit/0.1","format":"markdown"}
Transaction InfoBlock #17193819/Trx 691b30a47d2bbae63c21101b853c107d1e0f3aa6
View Raw JSON Data
{
  "trx_id": "691b30a47d2bbae63c21101b853c107d1e0f3aa6",
  "block": 17193819,
  "trx_in_block": 26,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-11-13T19:03:48",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "cryptocurrency",
      "author": "nethamdotsh",
      "permlink": "building-a-crypto-trading-bot-a-beginner-s-attempt-part-1",
      "title": "Building a Crypto Trading Bot : A beginner's attempt - Part 1",
      "body": "## Introduction\n\nI don't have much knowledge about trading,  I design and build things for a living. A friend asked me to spin up a bot for him. This will help beginners trying to build a trading bot. The design of the bot is strategy independent so you can plugin any strategy or a mix of strategies. I used Bittrex API but you can use any exchange API with this architecture.\n\n##### What we will talk talk about\n* Few basics of trading (can be skipped)\n* Bittrex API\n* Architecture of the bot\n* Mechanics of bot\n* Adding strategies to the bot\n* What not to do\n* Things to keep in mind\n* Testing\n\n##### What is not here\n* Strategies\n* HFT (you can use the architecture)\n* Scalability\n* How to get rich\n\n---\nFor people who are new to coding/development (rest can skip)\n\n```\n\t\n\tWhat I used to build the bot : PHP and MySQL\n\tServer: Ubuntu on DigitalOcean \n\t\n\tWhat tools you can use: Any language you are comfortable  with or \n\tyou are learning. This article is not language specific.\n\tYou don't need to learn any complex frameworks. Don't go looking\n\tfor frameworks if you are a beginner.\n\t\n\tThings you will need to know in any language you want to use:\n\t1. How to make http requests and parse JSON\n\t2. How to store and read data from a database\n\t3. Running cronjobs and background tasks\n\n\tYou can also contact me to build a bot for you.\n\t\n```\nYou can get 10$ credit for digitalocean using my referral link <https://m.do.co/c/22764aaa6bbf> \n\n---\t\n\n## Basics of Trading\n\nI am discussing few basics, the minimum required to understand the rest of the post. If you have done trading before and understand the type of orders and partial orders, this can be skipped.\n\n#### ELI5\n\nTrading simply means exchanging A for B (called BUY B) or B for A (called SELL B) in market A-B. e.g. In BTC-BCC market, if you place an order for exchange of BTC for BCC, you are placing a BUY BCC order, if you place an order for exchange of BCC for BTC, you are placing a SELL BCC order.\n\nTo trade, you place a BUY or SELL order of type T (will come to types later) in the market for a quantity Q and Rate R (per unit price). If the quantity and rate of your order matches the requirements or conditions of another order of the opposite kind, a transaction takes place. The requirements and the conditions are determined by the type of order.\n\nFew terms:  \n\"Ask\" - The lowest rate at which someone in the market A-B is ready to SELL B for  \n\"Bid\" - The highest rate at which someone in the market A-B is ready to BUY B for  \n\"Last\" - The rate at which the last transaction took place in the market\n\n\n#### Types of Order\n\nThere are different types of orders which can be placed. We are discussing only two types here, because most APIs allow only these two\n\n* Market Order - When you want to buy or sell immediately but you don't care for the rate, you place a Market order. In this case you don't control how much you bought something for or for how much you sold it for.\n\n* Limit Order - When you want to set a maximum rate for your BUY order or a minimum rate for your SELL order, you place a Limit order where the maximum/minimum price is referred to as Limit e.g. You placed a Limit order to SELL 1 BCC FOR 0.005 BTC (Your Ask), but if the bid in the market is for 0.007 BTC, then your order will fetch you 0.007 BTC. If there is no bid in the market over 0.005, it won't sell. \n\nIn Market Order, there is guarantee of fullfillment. In Limit Order type, there is a guarantee of price. More types of orders like Stop orders, All or None orders, Good till Cancelled etc. can be placed at the Exchange using their dashboard. I suggest read about them too. \n\n#### Order Book\n\nBelow is a screenshot for the Order Book of BTC-BCC market.   \n\n![Order Book example] (https://i.imgur.com/upheC7h.png)\n\nIt is a list of current Bids in descending order and Asks and in ascending order. So on the left you will see highest bid on the top and on the right you will see lowest ask on the top. When you will place a SELL or a BUY order it will show in the order book. As soon as an order gets complete, it disappears from the order book and goes into Market history. The blanks you see were the rows which were getting updated while I took the screenshot.\n\nThis is sufficient for you to understand the API. But first go here <a href=\"https://bittrex.com/Market/Index?MarketName=BTC-BCC\" target=\"_blank\"> BTC-BCC Market</a> and spend few minutes looking at live action, look around the page and see if you understand most of it.\n\n\n## Bittrex API\n\nTake a look at the Bittrex API -  <a href=\"https://bittrex.com/Home/Api\" target=\"_blank\"> Bittrex API Documentation</a> If you are using any other exchange, the difference will be probably between endpoint names and flags.\n\nFew points to note for Bittrex : All requests are GET requests and gives data in JSON. There is always a \"success\" flag in each and every request, which is boolean so you should check it everytime you make a request. Bittrex has no way to tell you when something happened, like an order got completed in thar market (some APIs do that), you have to constantly make requests to find status of your order.\n\nLet's dive into playing around with the API and understanding more about it. The documentation starts with authentication but we will talk about that later. \n\n### Public API \n\nPublic API doesn't requires any sort of authentication. You can view these endpoints in your browser.\n\n#### Ticker\n\n**/public/getticker?market=**\n\nTicker returns the most current Bid, Ask and Last rate for a market. The values will change every moment if lot of people are trading in the market. Let's find out the current Bid, Ask and Last of BTC-BCC market. <a href=\"https://bittrex.com/api/v1.1/public/getticker?market=BTC-BCC \" target=\"_blank\">\nhttps://bittrex.com/api/v1.1/**public/getticker?market=**BTC-BCC </a>. \nVisit it again, and you might see different rates. \n\n#### Order Book\n**/public/getorderbook?market= ___ &type= ____**\n\nThis endpoint gets the orderbook for the requested market. Type can have values as 'sell' : returns only sell order data, 'buy': returns only buy order data or 'both'. Check the order book of BTC-LTC market <a href=\"https://bittrex.com/api/v1.1/public/getorderbook?market=BTC-LTC&type=both \" target=\"_blank\">\nhttps://bittrex.com/api/v1.1/**public/getorderbook?market=BTC-LTC&type=both**</a>\n\nLets look at few different error messages:  \n\n* When market is invalid, mostly happens in typos. <a href=\"https://bittrex.com/api/v1.1/public/getorderbook?market=BTC-LTTT&type=both \" target=\"_blank\">\nhttps://bittrex.com/api/v1.1/public/getorderbook?market=BTC-**LTTT**&type=both</a>  \n\n`  {\"success\":false,\"message\":\"INVALID_MARKET\",\"result\":null}  `  \n\n* When type is invalid. <a href=\"https://bittrex.com/api/v1.1/public/getorderbook?market=BTC-LTC&type=random \" target=\"_blank\">\nhttps://bittrex.com/api/v1.1/public/getorderbook?market=BTC-LTC&type=**random**</a>\n  \n`  \n   {\"success\":false,\"message\":\"TYPE_INVALID\",\"result\":null} \n`\n\nNote the success flag is false in both the above requests.  \n\nSimilarly in the documentation there are other public endpoints like getmarketsummary, getcurrencies etc. Copy the links from the examples in the  <a href=\"https://bittrex.com/Home/Api\" target=\"_blank\"> Bittrex API Documentation</a> and visit them in new tab to understand the structure of the data.\n\n\n```\n Task (for beginners) : Ping the BTC-BCC ticker endpoint every minute for 10\n minutes and find % change in Bid and Ask per minute and total % change in 10\n minutes. If you have never made GET requests before or parsed JSON, stop \n reading, and do this task. Comment below with your results and time and date.\n\n```\n\n\n### Market API\n\nMarket API endpoints are interaction points with the market. Using them you can place an order, cancel an order and look at your open orders. Open orders refer to orders which you have placed in the market but have not been fullfilled yet.\nThese endpoints require authentication which we will talk in the end of this section. So you won't be able to test the endpoints right now, we will first understand the responses. Bittrex allows only limit type of orders to be placed for now (refer to the Basics of Trading section). It had market orders in the past but they are not available anymore.\n\nNote: the API endpoints below will be missing apikey parameter. They are required for Market API. We will add it when we learn about authentication. \n\n#### Limit Buy Order  \n\n**/market/buylimit?market= ___ &quantity= __ &rate= ___** \n\nSuppose we want to buy 0.0032673 BCC at the rate of 0.001423 BTC, we will form our url like\n/market/buylimit?market=BTC-BCC&quantity=0.0032673&rate=0.001423 \n. The response looks like this: \n\n```\n{\n\t\"success\" : true,\n\t\"message\" : \"\",\n\t\"result\" : {\n\t\t\t\"uuid\" : \"d402d53c-0d70-11e3-94b5-425231b86ab6\"\n\t\t}\n}\n``` \n\nThe flag \"success\" is true, so our order got placed in the market. It returned a uuid (universally unique identifier) which represents our order ID in the market. To find out anything about the order we placed we will use this uuid.\n\n\n#### Limit Sell Order\n\n**/market/selllimit?market= ___ &quantity= __ &rate= ___** \n\nThis returns response similar to limitbuy, a uuid.  \n\nNote:  Bittrex doesn't allows orders which have size less than 50,000 Satoshis. It gives you error message of \"DUST\\_TRADE\\_DISALLOWED\\_MIN\\_VALUE\\_50K\\_SAT\". [More info](https://support.bittrex.com/hc/en-us/articles/202605394-Updates-to-Minimum-Trade-Sizes) \n\n#### Points to keep in mind for fullfillment of orders\n*  \tRemember the orders using the above endpoints are limit orders. A Limit Sell will get complete/fullfilled whenever the price in the market is higher than or equal to the rate you requested. A Limit Buy order will get complete whenever the price in the market is lower or equal to the rate you requested. \n*  Placement of an order and fullfillment of an order are two different steps. The success message in the previous two discussed endpoints is a confirmation of successful placement of an order.\n*  Sometimes your oder will get fullfilled partially only. e.g. You placed a LIMIT BUY order for 100 BCC at the rate 0.005. Someone else placed a SELL order at the same or lower rate, but had only say 20 BCC to sell. As soon as your order got fullfilled with 20 BCC, say the market went up. It will remain partially filled unless the market comes down or you cancel the order which will cancel the remaining order.\n\n\n#### Open Orders\n**/market/getopenorders**   \n**/market/getopenorders?market= ___** \n\nOpen orders returns the orders which have not been fullfilled, partially or completely. You can request for a specific market also. Below is the response we get. Look at the // comments below to understand more (they are not part of the response).\n\n```\n\n    {\n\t\"success\" : true,\n\t\"message\" : \"\",\n\t\"result\" : [{\n\t\t\t\"Uuid\" : null,\n\t\t\t\"OrderUuid\" : \"09aa5bb6-8232-41aa-9b78-a5a1093e0211\",\n\t\t\t\"Exchange\" : \"BTC-LTC\",\n\t\t\t\"OrderType\" : \"LIMIT_SELL\", \n\t\t\t\"Quantity\" : 5.00000000,\n\t\t\t\"QuantityRemaining\" : 5.00000000,\n\t\t\t\"Limit\" : 2.00000000,\n\t\t\t\"CommissionPaid\" : 0.00000000,\n\t\t\t\"Price\" : 0.00000000,\n\t\t\t\"PricePerUnit\" : null,\n\t\t\t\"Opened\" : \"2014-07-09T03:55:48.77\",\n\t\t\t\"Closed\" : null,\n\t\t\t\"CancelInitiated\" : false,\n\t\t\t\"ImmediateOrCancel\" : false,\n\t\t\t\"IsConditional\" : false,\n\t\t\t\"Condition\" : null,\n\t\t\t\"ConditionTarget\" : null\n\t\t}, {\n\t\t\t\"Uuid\" : null,\n\t\t\t\"OrderUuid\" : This is uuid which we got when placed the LIMIT SELL \n\t\t\torder. You can use this to search for your order.\n\t\t\t\"Exchange\" :  Market\n\t\t\t\"OrderType\" : Type of order\n\t\t\t\"Quantity\" : The quantity you requested for\n\t\t\t\"QuantityRemaining\" : This tells how much is yet to be bought/sold.\n\t\t\tWe will use this to find the status of our order.\n\t\t\t\"Limit\" : Your Limit Rate\n\t\t\t\"CommissionPaid\" : Comission of Bittrex which is 0.25%\n\t\t\t\"Price\" : The total price at which the order got fullfilled for. \n\t\t\t\"PricePerUnit\" : Price per unit at which the order got fullfilled for\n\t\t\t\"Opened\" : timestamp when bittrex placed your order\n\t\t\t\"Closed\" : timestamp when bittrex completed your order\n\t\t\t\"CancelInitiated\" : true if you cancelled the order but it has \n\t\t\tnot been cancelled yet. The process is taking place.\n\t\t\t\"ImmediateOrCancel\" : Bittrex uses these flags and following ones\n\t\t\t when you place using Bittrex dashboard.  \n\t\t\t\"IsConditional\" : false,\n\t\t\t\"Condition\" : null,\n\t\t\t\"ConditionTarget\" : null\n\t\t}\n\t]\n}\n```\n\n\nSo we can use this endpoint with QuantityRemaining key to check the status of the order and to find how much of the order got fullfilled. We will learn more on that later when we design the bot.\n\n\n### Authentication\n\nThis is specific to Bittrex. With an account on Bittrex you can create multiple API keys which can set to have different permissions. You will need API Key and API secret to make authenticated requests.\n\nTo make an authenticated request, like for market APIs in Bittrex, apikey and nonce are appended to the url. Nonce is the current Unix timestamp. It is in seconds. e.g. Get Open orders request will become   \n**/market/getopenorders?apikey=xxxxxxxx&nonce=yyyyyyyyy** \n\nWhen making this request, you also calculate HMAC hash of request url (containing nonce and key) and API secret and include it in the request under apisign header.\n\nA nice way is to make a function to which you can pass the a url append nonce and apikey inside the function and make a request with the hash.\n\n```\nfunction BittrexAuthRequest($url){\n\t$apikey='xxx';\n\t$apisecret='xxx';\n\t$nonce=time();\n\t$uri=$url.'&apikey='.$apikey.'&nonce='.$nonce; //appending apikey and nonce\n\t$sign=hash_hmac('sha512',$uri,$apisecret); //calculating hmac hash\n\t$ch = curl_init($uri);\n\tcurl_setopt($ch, CURLOPT_HTTPHEADER, array('apisign:'.$sign)); //adding hash to the apisign\n\t$execResult = curl_exec($ch);\n\t$obj = json_decode($execResult);\n\treturn $obj;\n}\n```\nSome of you might be new to headers so I am including examples in other languages  \n[Python](https://github.com/ndri/python-bittrex/blob/master/bittrex.py) : Look at line 33  \n[Javascript](https://github.com/n0mad01/node.bittrex.api/blob/master/node.bittrex.api.js) : Check at line 81. Also note inclusion of external file at line 15 for calculating hmac.\n\n```\nTask (for beginners): Signup on Bittrex and create an API key. \nCode in the BittrexAuthRequest function in your own \nlanguage and place a BUY order for 0.00000001 BCC at current Ask. \nUse Ticker to find the Ask. If you code it right, then the order will\nfail (because it is less than 50k Satoshis) and  response message\nwill be either 'Insufficient Funds' or DUST\\_TRADE\\_DISALLOWED\\_MIN\\_VALUE\\_50K\\_SAT\n```\n\n---------------\n\n---------------\n\nPart 2 coming soon. Follow to stay updated.  \n\nIf you liked this upvote. If you have questions or any suggestions, you can comment below.\n\nFor consultation/development of trading bot or something similar you can contact me netham91+steemit [at] gmail with subject line containing '[Project]'",
      "json_metadata": "{\"tags\":[\"cryptocurrency\",\"trading\",\"bot\",\"bittrex\",\"bitcoin\"],\"image\":[\"https://i.imgur.com/upheC7h.png\"],\"links\":[\"https://m.do.co/c/22764aaa6bbf\",\"https://bittrex.com/Market/Index?MarketName=BTC-BCC\",\"https://bittrex.com/Home/Api\",\"https://bittrex.com/api/v1.1/public/getticker?market=BTC-BCC \",\"https://bittrex.com/api/v1.1/public/getorderbook?market=BTC-LTC&type=both \",\"https://bittrex.com/api/v1.1/public/getorderbook?market=BTC-LTTT&type=both \",\"https://bittrex.com/api/v1.1/public/getorderbook?market=BTC-LTC&type=random \",\"https://support.bittrex.com/hc/en-us/articles/202605394-Updates-to-Minimum-Trade-Sizes\",\"https://github.com/ndri/python-bittrex/blob/master/bittrex.py\",\"https://github.com/n0mad01/node.bittrex.api/blob/master/node.bittrex.api.js\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}
steemcreated a new account: @nethamdotsh
2017/11/10 13:23:45
fee0.500 STEEM
delegation57000.000000 VESTS
creatorsteem
new account namenethamdotsh
owner{"weight_threshold":1,"account_auths":[],"key_auths":[["STM8LCVi8VtjUsKutr5UceGkzALEq2NmJfHxSFkPJqKXhv6dh5FmJ",1]]}
active{"weight_threshold":1,"account_auths":[],"key_auths":[["STM64w8A8S3K7uormof1pZz63KqRQFs7F3tyDFNwC5rDeERudMV2b",1]]}
posting{"weight_threshold":1,"account_auths":[],"key_auths":[["STM7aUTF3mbtyiqCecm2XU8ofwPURxvZKb65Y8mFN5xgJZqU6WzHS",1]]}
memo keySTM5iALwPbHyyjALmEqPh8MtL2ArrXZMGBUraJdHL1Li3cK8XAKHg
json metadata
extensions[]
Transaction InfoBlock #17100623/Trx 22828f372d1876391da566a0fe4618bde553fde4
View Raw JSON Data
{
  "trx_id": "22828f372d1876391da566a0fe4618bde553fde4",
  "block": 17100623,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-11-10T13:23:45",
  "op": [
    "account_create_with_delegation",
    {
      "fee": "0.500 STEEM",
      "delegation": "57000.000000 VESTS",
      "creator": "steem",
      "new_account_name": "nethamdotsh",
      "owner": {
        "weight_threshold": 1,
        "account_auths": [],
        "key_auths": [
          [
            "STM8LCVi8VtjUsKutr5UceGkzALEq2NmJfHxSFkPJqKXhv6dh5FmJ",
            1
          ]
        ]
      },
      "active": {
        "weight_threshold": 1,
        "account_auths": [],
        "key_auths": [
          [
            "STM64w8A8S3K7uormof1pZz63KqRQFs7F3tyDFNwC5rDeERudMV2b",
            1
          ]
        ]
      },
      "posting": {
        "weight_threshold": 1,
        "account_auths": [],
        "key_auths": [
          [
            "STM7aUTF3mbtyiqCecm2XU8ofwPURxvZKb65Y8mFN5xgJZqU6WzHS",
            1
          ]
        ]
      },
      "memo_key": "STM5iALwPbHyyjALmEqPh8MtL2ArrXZMGBUraJdHL1Li3cK8XAKHg",
      "json_metadata": "",
      "extensions": []
    }
  ]
}

Account Metadata

POSTING JSON METADATA
None
JSON METADATA
None
{
  "posting_json_metadata": {},
  "json_metadata": {}
}

Auth Keys

Owner
Single Signature
Public Keys
STM8LCVi8VtjUsKutr5UceGkzALEq2NmJfHxSFkPJqKXhv6dh5FmJ1/1
Active
Single Signature
Public Keys
STM64w8A8S3K7uormof1pZz63KqRQFs7F3tyDFNwC5rDeERudMV2b1/1
Posting
Single Signature
Public Keys
STM7aUTF3mbtyiqCecm2XU8ofwPURxvZKb65Y8mFN5xgJZqU6WzHS1/1
Memo
STM5iALwPbHyyjALmEqPh8MtL2ArrXZMGBUraJdHL1Li3cK8XAKHg
{
  "owner": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM8LCVi8VtjUsKutr5UceGkzALEq2NmJfHxSFkPJqKXhv6dh5FmJ",
        1
      ]
    ]
  },
  "active": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM64w8A8S3K7uormof1pZz63KqRQFs7F3tyDFNwC5rDeERudMV2b",
        1
      ]
    ]
  },
  "posting": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM7aUTF3mbtyiqCecm2XU8ofwPURxvZKb65Y8mFN5xgJZqU6WzHS",
        1
      ]
    ]
  },
  "memo": "STM5iALwPbHyyjALmEqPh8MtL2ArrXZMGBUraJdHL1Li3cK8XAKHg"
}

Witness Votes

0 / 30
No active witness votes.
[]