Author Topic: Unable to make any kind of transactions in Muse wallet.  (Read 4395 times)

0 Members and 1 Guest are viewing this topic.

Offline robrigo

Consider your account vested. Ideally the MUSE team should make the faucet handle this.

Code: [Select]
{
  "ref_block_num": 49965,
  "ref_block_prefix": 191616504,
  "expiration": "2018-04-02T02:05:51",
  "operations": [[
      "transfer_to_vesting",{
        "from": "robrigo",
        "to": "ashaman",
        "amount": "0.010000 2.28.0"
      }
    ]
  ],
  "extensions": [],
  "signatures": [
    "1f3d308a6ddcc663186a0b180e22e494ba3d4b8dbd09f9190a50720fca7adf6def2ee25c7c7366c4bcfcf3d0e8592626b0755805ea42eff6589c7c9189e727a183"
  ],
  "transaction_id": "8580bc26c89fcb7672160b5a6b8a73c055252ccc",
  "block_num": 6538030,
  "transaction_num": 0
}

Offline Ashaman

  • Newbie
  • *
  • Posts: 15
    • View Profile
Attempts to make any kind of transaction (transfer, transfer to vesting) using wallet.museblockchain.com produce the following error message
Code: [Select]
account exceeded maximum allowed bandwidth per vesting share account_vshares.
Attempts to vote result in "Unable to vote. please try again"
Happens in both Chrome and Firefox.

An attempt to vest some muse in cli_wallet also throws an error. Part of the message:
Code: [Select]
1671362ms wallet.cpp:849                sign_transaction     ] Caught exception while broadcasting tx 9e95e6f3852c8c11bdf0dec72f25d7bed119cf6d:  0 exception: unspecified
10 assert_exception: Assert Exception
(account_vshares * max_virtual_bandwidth) > (account_average_bandwidth * total_vshares): account exceeded maximum allowed bandwidth per vesting share account_vshares: 999 account_average_bandwidth: 97000000 max_virtual_bandwidth: 5824555244896037546 total_vesting_shares: ${total_vesting_shares}
    {"account_vshares":"999","account_average_bandwidth":"97000000","max_virtual_bandwidth":"5824555244896037546","total_vshares":"5012649678949759"}
    database.cpp:512 operator()
    {"trx":{"ref_block_num":4304,"ref_block_prefix":1218490240,"expiration":"2018-03-31T09:28:21","operations":[["transfer_to_vesting",{"from":"ashaman","to":"","amount":"57.000000 2.28.0"}]],"extensions":[],"signatures":["20583c4c6a07a8729aab7eac89d7a2c0be53063a84094917fd4358f7ac6ed70a5233576cf155e55a4f0bec6240e3df6190d0ae303f9644905e033e9dfac56844d5"]}}
    database.cpp:2755 _apply_transaction

    {"trx":{"ref_block_num":4304,"ref_block_prefix":1218490240,"expiration":"2018-03-31T09:28:21","operations":[["transfer_to_vesting",{"from":"ashaman","to":"","amount":"57.000000 2.28.0"}]],"extensions":[],"signatures":["20583c4c6a07a8729aab7eac89d7a2c0be53063a84094917fd4358f7ac6ed70a5233576cf155e55a4f0bec6240e3df6190d0ae303f9644905e033e9dfac56844d5"]}}
    database.cpp:712 push_transaction

Any idea what I can do about this? My research indicates this wouldn't happen if I had more vested Muse, but it won't let me vest any either?

This is the account in question https://muse-db.com/@ashaman
I registered, claimed my stake, and moved my remaining muse from OL so they would not be in the hands of a 3rd party.