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

Detailed Balance

STEEM
balance
0.000STEEM
market_balance
0.000STEEM
savings_balance
0.000STEEM
reward_steem_balance
0.000STEEM
STEEM POWER
Own SP
0.000SP
Delegated Out
0.000SP
Delegation In
10.062SP
Effective Power
10.062SP
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": "0.000000 VESTS",
  "delegated_vesting_shares": "0.000000 VESTS",
  "received_vesting_shares": "16384.600372 VESTS",
  "sbd_balance": "0.000 SBD",
  "savings_sbd_balance": "0.000 SBD",
  "reward_sbd_balance": "0.000 SBD",
  "conversions": []
}

Account Info

nameryan1walker
id1954472
rank129,559
reputation0
created2026-02-21T14:43:39
recovery_accountsteemcurator01
proxyNone
post_count5
comment_count0
lifetime_vote_count0
witnesses_voted_for0
last_post2026-04-02T10:54:06
last_root_post1970-01-01T00:00:00
last_vote_time1970-01-01T00:00:00
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_shares0.000000 VESTS
delegated_vesting_shares0.000000 VESTS
received_vesting_shares16384.600372 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": 1954472,
  "name": "ryan1walker",
  "owner": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM7Ec8YwPcxhY1EjkFopuvZWvbyvELrbdNs3uJ8f4taxR96sFmSE",
        1
      ]
    ]
  },
  "active": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM5ovBQr9XXxaH8D3RsK7BdqHeoQwYDkKWsXengL6CEsRNkHEzyU",
        1
      ]
    ]
  },
  "posting": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM7jShqZys7aNJ7a2ryk8JGn3FfdB7aZFQHJfTuBEncpikuzr4BA",
        1
      ]
    ]
  },
  "memo_key": "STM5pYkxDNcJrpjrePR7TZm4rfttfKuoJYeUUJ3u6gPggfwsWfNxZ",
  "json_metadata": "{}",
  "posting_json_metadata": "",
  "proxy": "",
  "last_owner_update": "1970-01-01T00:00:00",
  "last_account_update": "1970-01-01T00:00:00",
  "created": "2026-02-21T14:43:39",
  "mined": false,
  "recovery_account": "steemcurator01",
  "last_account_recovery": "1970-01-01T00:00:00",
  "reset_account": "null",
  "comment_count": 0,
  "lifetime_vote_count": 0,
  "post_count": 5,
  "can_vote": true,
  "voting_manabar": {
    "current_mana": "16384600372",
    "last_update_time": 1771692159
  },
  "downvote_manabar": {
    "current_mana": 4096150093,
    "last_update_time": 1771692159
  },
  "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": "0.000000 VESTS",
  "delegated_vesting_shares": "0.000000 VESTS",
  "received_vesting_shares": "16384.600372 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": "2026-04-02T10:54:06",
  "last_root_post": "1970-01-01T00:00:00",
  "last_vote_time": "1970-01-01T00:00:00",
  "post_bandwidth": 0,
  "pending_claimed_accounts": 0,
  "vesting_balance": "0.000 STEEM",
  "reputation": 0,
  "transfer_history": [],
  "market_history": [],
  "post_history": [],
  "vote_history": [],
  "other_history": [],
  "witness_votes": [],
  "tags_usage": [],
  "guest_bloggers": [],
  "rank": 129559
}

Withdraw Routes

IncomingOutgoing
Empty
Empty
{
  "incoming": [],
  "outgoing": []
}
From Date
To Date
2026/04/02 10:54:06
parent authorrayparker
parent permlink7-best-web-design-tools-for-designers-to-try
authorryan1walker
permlinktcv4y5
title
bodyGreat list! Tools like Axure and Atomic are genuinely useful for day-to-day prototyping. One thing I'd add though - no matter how good your tools are, the final result still depends heavily on the overall design strategy, especially for larger projects. I've seen teams use all the right software and still end up with a website that doesn't convert, simply because the structure and UX weren't thought through from a business perspective. If you're working on something at scale, it might be worth looking at how specialized teams approach it - for example, https://arounda.agency/services/enterprise-website-design-agency covers a lot of the strategic side that individual tools alone can't handle. Anyway, solid post - Frontify is criminally underrated for keeping teams aligned on brand guidelines.
json metadata{"links":["https://arounda.agency/services/enterprise-website-design-agency"],"app":"steemit/0.2"}
Transaction InfoBlock #104835040/Trx f9149e95c98639d3e0f3c1c8f2daf081da1111f1
View Raw JSON Data
{
  "trx_id": "f9149e95c98639d3e0f3c1c8f2daf081da1111f1",
  "block": 104835040,
  "trx_in_block": 16,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2026-04-02T10:54:06",
  "op": [
    "comment",
    {
      "parent_author": "rayparker",
      "parent_permlink": "7-best-web-design-tools-for-designers-to-try",
      "author": "ryan1walker",
      "permlink": "tcv4y5",
      "title": "",
      "body": "Great list! Tools like Axure and Atomic are genuinely useful for day-to-day prototyping. One thing I'd add though - no matter how good your tools are, the final result still depends heavily on the overall design strategy, especially for larger projects. I've seen teams use all the right software and still end up with a website that doesn't convert, simply because the structure and UX weren't thought through from a business perspective. If you're working on something at scale, it might be worth looking at how specialized teams approach it - for example, https://arounda.agency/services/enterprise-website-design-agency covers a lot of the strategic side that individual tools alone can't handle. Anyway, solid post - Frontify is criminally underrated for keeping teams aligned on brand guidelines.",
      "json_metadata": "{\"links\":[\"https://arounda.agency/services/enterprise-website-design-agency\"],\"app\":\"steemit/0.2\"}"
    }
  ]
}
2026/02/27 13:39:03
parent authorummjackson
parent permlinkbringing-cryptocurrency-to-a-wider-audience-via-the-browser-webrtc
authorryan1walker
permlinktb4dx3
title
bodyLove this idea. WebRTC is a really nice way to lower the “install a wallet + sync a huge chain” barrier, but in practice there are a couple of gotchas worth calling out for anyone thinking of building it: * **You still need signaling + discovery.** WebRTC gives you the P2P transport (DTLS/SRTP + data channels), but peers still need a way to find each other and exchange SDP/ICE info. That part becomes your “hidden backend” unless you have enough bridge nodes. * **NAT traversal is the silent cost.** In the real world, a chunk of users will require TURN relays, and that’s bandwidth + reliability planning (plus good fallback logic when a direct route fails). * **Security model matters more than UX.** A browser wallet is only as safe as the page context: XSS protections, CSP, dependency hygiene, storage encryption, and a clean key management story (ideally hardware keys / external signing where possible). If someone is actually implementing browser-based P2P connectivity for wallets or real-time features, it helps to look at how experienced RTC teams structure signaling/TURN/monitoring and edge cases — I bookmarked this overview of **[webrtc development services](https://yojji.io/solutions/webrtc-development-company)** as a decent reference for what to plan for end-to-end. Curious: do you see the bridge nodes as a temporary bootstrap (until browsers/clients adopt a common standard), or a permanent part of the network?
json metadata{"links":["https://yojji.io/solutions/webrtc-development-company"],"app":"steemit/0.2"}
Transaction InfoBlock #103864422/Trx c00799921fb88b959f7a49398c18c9d5fc6fa730
View Raw JSON Data
{
  "trx_id": "c00799921fb88b959f7a49398c18c9d5fc6fa730",
  "block": 103864422,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2026-02-27T13:39:03",
  "op": [
    "comment",
    {
      "parent_author": "ummjackson",
      "parent_permlink": "bringing-cryptocurrency-to-a-wider-audience-via-the-browser-webrtc",
      "author": "ryan1walker",
      "permlink": "tb4dx3",
      "title": "",
      "body": "Love this idea. WebRTC is a really nice way to lower the “install a wallet + sync a huge chain” barrier, but in practice there are a couple of gotchas worth calling out for anyone thinking of building it:\n\n* **You still need signaling + discovery.** WebRTC gives you the P2P transport (DTLS/SRTP + data channels), but peers still need a way to find each other and exchange SDP/ICE info. That part becomes your “hidden backend” unless you have enough bridge nodes.\n* **NAT traversal is the silent cost.** In the real world, a chunk of users will require TURN relays, and that’s bandwidth + reliability planning (plus good fallback logic when a direct route fails).\n* **Security model matters more than UX.** A browser wallet is only as safe as the page context: XSS protections, CSP, dependency hygiene, storage encryption, and a clean key management story (ideally hardware keys / external signing where possible).\n\nIf someone is actually implementing browser-based P2P connectivity for wallets or real-time features, it helps to look at how experienced RTC teams structure signaling/TURN/monitoring and edge cases — I bookmarked this overview of **[webrtc development services](https://yojji.io/solutions/webrtc-development-company)** as a decent reference for what to plan for end-to-end.\n\nCurious: do you see the bridge nodes as a temporary bootstrap (until browsers/clients adopt a common standard), or a permanent part of the network?",
      "json_metadata": "{\"links\":[\"https://yojji.io/solutions/webrtc-development-company\"],\"app\":\"steemit/0.2\"}"
    }
  ]
}
2026/02/25 11:55:12
parent authorpaulag
parent permlinksolving-nolock-sql-power-bi-issues-with-sample-code-for-steemsql
authorryan1walker
permlinktb0jrz
title
bodyGreat thread still very useful, especially the point about testing the SQL first and then moving it into Power BI. That workflow saves a lot of time when you’re debugging filters, date conversions, or reserved column names. I also like the focus on keeping queries clean when working with live data sources. Even small changes in query structure can make a big difference in performance and reliability once the report starts growing. For teams that need more advanced reporting setup (data modeling, dashboard architecture, refresh optimization, etc.), it can also help to [hire power bi developer](https://cobit-solutions.com/en/services/power-bi-developers-for-data-driven-solutions/) instead of trying to solve every issue ad hoc.
json metadata{"links":["https://cobit-solutions.com/en/services/power-bi-developers-for-data-driven-solutions/"],"app":"steemit/0.2"}
Transaction InfoBlock #103804959/Trx fff7a349dfd9d790b9a16276978eee6d7de4039c
View Raw JSON Data
{
  "trx_id": "fff7a349dfd9d790b9a16276978eee6d7de4039c",
  "block": 103804959,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2026-02-25T11:55:12",
  "op": [
    "comment",
    {
      "parent_author": "paulag",
      "parent_permlink": "solving-nolock-sql-power-bi-issues-with-sample-code-for-steemsql",
      "author": "ryan1walker",
      "permlink": "tb0jrz",
      "title": "",
      "body": "Great thread still very useful, especially the point about testing the SQL first and then moving it into Power BI. That workflow saves a lot of time when you’re debugging filters, date conversions, or reserved column names.\n\nI also like the focus on keeping queries clean when working with live data sources. Even small changes in query structure can make a big difference in performance and reliability once the report starts growing.\n\nFor teams that need more advanced reporting setup (data modeling, dashboard architecture, refresh optimization, etc.), it can also help to [hire power bi developer](https://cobit-solutions.com/en/services/power-bi-developers-for-data-driven-solutions/) instead of trying to solve every issue ad hoc.",
      "json_metadata": "{\"links\":[\"https://cobit-solutions.com/en/services/power-bi-developers-for-data-driven-solutions/\"],\"app\":\"steemit/0.2\"}"
    }
  ]
}
2026/02/24 12:13:45
parent authorbegtodiffer
parent permlinkthe-importance-of-the-software-development-life-cycle
authorryan1walker
permlinktaypyw
title
bodyGreat article it clearly shows that SDLC is not just a formal framework but a structure that directly impacts product quality. I especially liked the emphasis on the continuous nature of the lifecycle through maintenance. Many clients still assume that once development is finished, the project is “done,” while in reality the most important phase often begins after release, when the product starts evolving based on real usage. From experience, this becomes even more critical in niche solutions such as the flooring industry, where systems often include complex logic pricing calculations, ERP integrations, order and inventory management. Without a structured lifecycle, projects can quickly become difficult to maintain and scale. That’s why specialized [flooring software development services](https://bitsorchestra.com/industries/flooring-software) are typically built around a clear yet flexible SDLC approach. Thanks for sharing a solid reminder that quality software is always an ongoing process, not a one-time delivery.
json metadata{"links":["https://bitsorchestra.com/industries/flooring-software"],"app":"steemit/0.2"}
Transaction InfoBlock #103776638/Trx 68a55ad8e020d8f58909ac257bc1a7150eb2ff00
View Raw JSON Data
{
  "trx_id": "68a55ad8e020d8f58909ac257bc1a7150eb2ff00",
  "block": 103776638,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2026-02-24T12:13:45",
  "op": [
    "comment",
    {
      "parent_author": "begtodiffer",
      "parent_permlink": "the-importance-of-the-software-development-life-cycle",
      "author": "ryan1walker",
      "permlink": "taypyw",
      "title": "",
      "body": "Great article  it clearly shows that SDLC is not just a formal framework but a structure that directly impacts product quality. I especially liked the emphasis on the continuous nature of the lifecycle through maintenance. Many clients still assume that once development is finished, the project is “done,” while in reality the most important phase often begins after release, when the product starts evolving based on real usage.\n\nFrom experience, this becomes even more critical in niche solutions such as the flooring industry, where systems often include complex logic  pricing calculations, ERP integrations, order and inventory management. Without a structured lifecycle, projects can quickly become difficult to maintain and scale. That’s why specialized [flooring software development services](https://bitsorchestra.com/industries/flooring-software) are typically built around a clear yet flexible SDLC approach.\n\nThanks for sharing a solid reminder that quality software is always an ongoing process, not a one-time delivery.",
      "json_metadata": "{\"links\":[\"https://bitsorchestra.com/industries/flooring-software\"],\"app\":\"steemit/0.2\"}"
    }
  ]
}
steemdelegated 10.062 SP to @ryan1walker
2026/02/21 16:42:39
delegatorsteem
delegateeryan1walker
vesting shares16384.600372 VESTS
Transaction InfoBlock #103695820/Trx 74d8bc0764452c6f9196b4b7e25c91b07414e99a
View Raw JSON Data
{
  "trx_id": "74d8bc0764452c6f9196b4b7e25c91b07414e99a",
  "block": 103695820,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2026-02-21T16:42:39",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "ryan1walker",
      "vesting_shares": "16384.600372 VESTS"
    }
  ]
}
2026/02/21 14:49:15
parent authorthesocialpreneur
parent permlinkin-web-development-there-is-no-end-to-learning
authorryan1walker
permlinktatd63
title
bodyGreat post, and the main point is still true even in 2026, in software development, learning never really stops. What changed is the speed. Today, developers are not only learning frameworks and languages, but also adapting to AI-assisted workflows, cloud infrastructure, and faster product cycles. Tools like AI copilots and Cursor can speed up coding, but they don’t replace real engineering thinking - you still need to understand architecture, debugging, performance, and how systems work together. This is especially true in niche products like travel platforms, where development often includes API integrations (booking, maps, payments), scalable backend logic, and a smooth user experience across devices. That’s why teams usually look for solid **[travel website development services](https://www.overcode.tech/industries/travel-website-development)** not just “a website,” but a product built with the right technical foundation. So yes, your point is timeless: the constant learning is not a downside of this field it’s exactly what makes it interesting.
json metadata{"links":["https://www.overcode.tech/industries/travel-website-development"],"app":"steemit/0.2"}
Transaction InfoBlock #103693557/Trx 9635f1eb739b7f28c88a592acbd4460d48b1a3ac
View Raw JSON Data
{
  "trx_id": "9635f1eb739b7f28c88a592acbd4460d48b1a3ac",
  "block": 103693557,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2026-02-21T14:49:15",
  "op": [
    "comment",
    {
      "parent_author": "thesocialpreneur",
      "parent_permlink": "in-web-development-there-is-no-end-to-learning",
      "author": "ryan1walker",
      "permlink": "tatd63",
      "title": "",
      "body": "Great post, and the main point is still true even in 2026, in software development, learning never really stops.\n\nWhat changed is the speed. Today, developers are not only learning frameworks and languages, but also adapting to AI-assisted workflows, cloud infrastructure, and faster product cycles. Tools like AI copilots and Cursor can speed up coding, but they don’t replace real engineering thinking - you still need to understand architecture, debugging, performance, and how systems work together.\n\nThis is especially true in niche products like travel platforms, where development often includes API integrations (booking, maps, payments), scalable backend logic, and a smooth user experience across devices. That’s why teams usually look for solid **[travel website development services](https://www.overcode.tech/industries/travel-website-development)**   not just “a website,” but a product built with the right technical foundation.\n\nSo yes, your point is timeless: the constant learning is not a downside of this field it’s exactly what makes it interesting.",
      "json_metadata": "{\"links\":[\"https://www.overcode.tech/industries/travel-website-development\"],\"app\":\"steemit/0.2\"}"
    }
  ]
}
steemdelegated 10.697 SP to @ryan1walker
2026/02/21 14:43:42
delegatorsteem
delegateeryan1walker
vesting shares17419.000000 VESTS
Transaction InfoBlock #103693446/Trx 203c0b8b8afec8da0333839c2514953724b5ff56
View Raw JSON Data
{
  "trx_id": "203c0b8b8afec8da0333839c2514953724b5ff56",
  "block": 103693446,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2026-02-21T14:43:42",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "ryan1walker",
      "vesting_shares": "17419.000000 VESTS"
    }
  ]
}
steemcurator01created a new account: @ryan1walker
2026/02/21 14:43:39
creatorsteemcurator01
new account nameryan1walker
owner{"weight_threshold":1,"account_auths":[],"key_auths":[["STM7Ec8YwPcxhY1EjkFopuvZWvbyvELrbdNs3uJ8f4taxR96sFmSE",1]]}
active{"weight_threshold":1,"account_auths":[],"key_auths":[["STM5ovBQr9XXxaH8D3RsK7BdqHeoQwYDkKWsXengL6CEsRNkHEzyU",1]]}
posting{"weight_threshold":1,"account_auths":[],"key_auths":[["STM7jShqZys7aNJ7a2ryk8JGn3FfdB7aZFQHJfTuBEncpikuzr4BA",1]]}
memo keySTM5pYkxDNcJrpjrePR7TZm4rfttfKuoJYeUUJ3u6gPggfwsWfNxZ
json metadata{}
extensions[]
Transaction InfoBlock #103693445/Trx 3ceadc097d3fdcef0c02ae9d1484d140c85cf0b3
View Raw JSON Data
{
  "trx_id": "3ceadc097d3fdcef0c02ae9d1484d140c85cf0b3",
  "block": 103693445,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2026-02-21T14:43:39",
  "op": [
    "create_claimed_account",
    {
      "creator": "steemcurator01",
      "new_account_name": "ryan1walker",
      "owner": {
        "weight_threshold": 1,
        "account_auths": [],
        "key_auths": [
          [
            "STM7Ec8YwPcxhY1EjkFopuvZWvbyvELrbdNs3uJ8f4taxR96sFmSE",
            1
          ]
        ]
      },
      "active": {
        "weight_threshold": 1,
        "account_auths": [],
        "key_auths": [
          [
            "STM5ovBQr9XXxaH8D3RsK7BdqHeoQwYDkKWsXengL6CEsRNkHEzyU",
            1
          ]
        ]
      },
      "posting": {
        "weight_threshold": 1,
        "account_auths": [],
        "key_auths": [
          [
            "STM7jShqZys7aNJ7a2ryk8JGn3FfdB7aZFQHJfTuBEncpikuzr4BA",
            1
          ]
        ]
      },
      "memo_key": "STM5pYkxDNcJrpjrePR7TZm4rfttfKuoJYeUUJ3u6gPggfwsWfNxZ",
      "json_metadata": "{}",
      "extensions": []
    }
  ]
}

Account Metadata

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

Auth Keys

Owner
Single Signature
Public Keys
STM7Ec8YwPcxhY1EjkFopuvZWvbyvELrbdNs3uJ8f4taxR96sFmSE1/1
Active
Single Signature
Public Keys
STM5ovBQr9XXxaH8D3RsK7BdqHeoQwYDkKWsXengL6CEsRNkHEzyU1/1
Posting
Single Signature
Public Keys
STM7jShqZys7aNJ7a2ryk8JGn3FfdB7aZFQHJfTuBEncpikuzr4BA1/1
Memo
STM5pYkxDNcJrpjrePR7TZm4rfttfKuoJYeUUJ3u6gPggfwsWfNxZ
{
  "owner": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM7Ec8YwPcxhY1EjkFopuvZWvbyvELrbdNs3uJ8f4taxR96sFmSE",
        1
      ]
    ]
  },
  "active": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM5ovBQr9XXxaH8D3RsK7BdqHeoQwYDkKWsXengL6CEsRNkHEzyU",
        1
      ]
    ]
  },
  "posting": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM7jShqZys7aNJ7a2ryk8JGn3FfdB7aZFQHJfTuBEncpikuzr4BA",
        1
      ]
    ]
  },
  "memo": "STM5pYkxDNcJrpjrePR7TZm4rfttfKuoJYeUUJ3u6gPggfwsWfNxZ"
}

Witness Votes

0 / 30
No active witness votes.
[]