BitShares Forum
Main => General Discussion => Topic started by: toast on July 15, 2014, 04:11:56 pm
-
If you last pulled before ~8pm forum time then you need to wipe your chain directory and rebuild. We reset to smooth the delegate registration fee out a bit.
Theme song: https://www.youtube.com/watch?v=4SBN_ikibtg
This is the first dry run featuring market functionality. We did not test it very extensively which means you should expect things to break.
Please use this thread only for helping us debug, particularly market_* commands
Mac Wallet: http://bitshares.org/BitSharesXT-0.1.2.dmg
Known Issues:
Wallet Account Transaction Ledger displays ERROR for market transactions, that is a display bug.
The volume metric on the price history is hardcoded to 1... coming soon :)
Wallet Account Transaction Ledger does not currently display an entry showing your collateral returned to your account after covering a short position. (A display issue)
When listing the order book, "Margin Calls" show up in the ask table even though they shouldn't. This is a display issue as well.
Market Matching Algorithm:
while( highest_bid >= lowest_ask )
trade_quantity = min( highest_bid.quote_quantity, highest_ask.quote_quantity )
usd_paid_by_bid = trade_quantity
usd_received_by_ask = trade_quantity
xts_paid_by_ask = trade_quantity * ask_price
xts_received_by_bid = trade_quantity * bid_price
fees = xts_paid_by_ask - xts_received_by_bid
ask.balance -= xts_paid_by_ask
bid.balance -= usd_paid_by_bid
New Delegate Pay & Registration Fee Calculations
foreach block
total_accumulated_fees += all_transactions_fees
delegate_pay = total_accumulated_fees / (blocks_per_day*14)
delegate_registration = delegate_pay * blocks_per_hour * 2 / 101
total_accumulated_fees -= (delegate_pay)
Effectively if there are no new fees or transactions delegate pay will fall by about 1% per block.
Wallet Import Enhancements
Bitcoin wallet import has been fixed, and should work with Bitcoin Core, BitShares PTS, Armory, Electrum, and Multibit formats. Please test.
New Commands
default (unlocked) >>> blockchain_market_order_book USD XTS
BIDS (* Short Order) | ASKS
TOTAL QUANTITY PRICE | PRICE QUANTITY TOTAL COLLATERAL
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
9.8800 USD 98.80000 XTS 0.1 USD / XTS | 0.01333201790756645 USD / XTS 3.75037 XTS 0.0500 USD
15.0000 USD 1,500.00000 XTS 0.01 USD / XTS*| 1.23 USD / XTS 9,959.39033 XTS 12,250.0501 USD
| 1.3609963334667113 USD / XTS 29.39016 XTS 39.9999 USD
| 1.62007525615913535 USD / XTS 6.14169 XTS 9.9500 USD
| 6. USD / XTS 10.00000 XTS 60.0000 USD
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| MARGIN
| CALL PRICE QUANTITY TOTAL COLLATERAL
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| 1.62007525615913535 USD / XTS 6.14169 XTS 9.9500 USD 8.18893 XTS
| 1.3609963334667113 USD / XTS 29.39016 XTS 39.9999 USD 39.18689 XTS
| 0.01333201790756645 USD / XTS 3.75037 XTS 0.0500 USD 5.00050 XTS
default (unlocked) >>> wallet_account_transaction_history
RECEIVED BLOCK FROM TO AMOUNT FEE MEMO ID
----------------------------------------------------------------------------------------------------------------------------------------------------------------
2014-07-15T21:46:25 0 GENESIS founders 16,666,667.16466 XTS 0.00000 XTS claim genesis balance N/A
2014-07-15T21:47:32 392 founders ORDER-3eyFiYt5 10,000.00000 XTS 0.10000 XTS sell 10000 XTS @ 1.23 USD 88fef923
2014-07-15T21:47:50 ERROR ORDER-3eyFiYt5 UNKNOWN 8.08943 XTS 7.98993 XTS pay ask @ 1.23 USD / XTS 00000000
2014-07-15T21:47:50 ERROR ORDER-3eyFiYt5 UNKNOWN 32.52024 XTS 25.85359 XTS pay ask @ 1.23 USD / XTS 00000000
2014-07-15T21:47:50 ERROR ORDER-3eyFiYt5 founders 9.9500 USD 7.98993 XTS fill ask @ 1.23 USD / XTS 00000000
2014-07-15T21:47:50 ERROR ORDER-3eyFiYt5 founders 39.9999 USD 25.85359 XTS fill ask @ 1.23 USD / XTS 00000000
2014-07-15T21:52:23 421 founders ORDER-2VqCgSAF 10.0000 USD 0.10000 XTS buy 100 XTS @ 0.1 USD ee1be376
2014-07-15T21:52:40 ERROR ORDER-2VqCgSAF UNKNOWN 0.1200 USD 4.80000 XTS pay bid @ 0.1 USD / XTS 00000000
2014-07-15T21:52:40 ERROR ORDER-2VqCgSAF founders 1.20000 XTS 4.80000 XTS fill bid @ 0.1 USD / XTS 00000000
2014-07-15T21:52:40 ERROR ORDER-2VqCgSAF founders 1.20000 XTS 4.80000 XTS fill bid @ 0.1 USD / XTS 00000000
TYPE QUANTITY PRICE BALANCE COST COLLATERAL ID
--------------------------------------------------------------------------------------------------------------------------------
bid_order 95.12000 XTS 0.1 USD / XTS 9.5120 USD 9.5120 USD N/A XTS2VqCgSAFzaoGokbmaeT1SJTVDrCoNm18K
ask_order 9,959.39033 XTS 1.23 USD / XTS 9,959.39033 XTS 12,250.0501 USD N/A XTS3eyFiYt5K1LFpau9iJyVMnpTjDr1kxQuu
cover_order 29.39016 XTS 1.3609963334667113 USD / XTS 39.9999 USD 39.9998 USD 39.18689 XTS XTS3eyFiYt5K1LFpau9iJyVMnpTjDr1kxQuu
cover_order 6.14169 XTS 1.62007525615913535 USD / XTS 9.9500 USD 9.9499 USD 8.18893 XTS XTS3eyFiYt5K1LFpau9iJyVMnpTjDr1kxQuu
bid founders 100 XTS .1 USD // buy 100 XTS @ 0.1 USD / XTS
ask founders 10000 XTS 1.23 USD // sell 10,000 XTS @ 1.23 USD / XTS
short founders 20 1.12 USD // short 20 USD at 1.12 USD / XTS
ask / wallet_market_submit_ask <from_account_name> <quantity> <quantity_symbol> <quote_price> <quote_symbol>
bid / wallet_market_submit_bid <from_account_name> <quantity> <quantity_symbol> <quote_price> <quote_symbol>
short / wallet_market_submit_short <from_account_name> <quantity> <quote_price> <quote_symbol>
-
BM already found a hard fork.
"30 minute rule" if you find a hard fork within 30 minutes it's still the same dry run.
Hang tight everyone
-
LOL false alarm you're actually good to go
-
+5%
building again.
-
Can not build:
[ 93%] Building CXX object programs/client/CMakeFiles/bitshares_client.dir/main.cpp.o
Linking CXX executable bitshares_client
../../libraries/bitcoin/libbitcoin.a(armory.cpp.o): In function `bts::bitcoin::import_armory_wallet(fc::path const&, std::string const&)':
/home/jakub/projekty/bitshares_toolkit/libraries/bitcoin/armory.cpp:73: undefined reference to `fc::romix::romix(unsigned int, unsigned int, std::string)'
/home/jakub/projekty/bitshares_toolkit/libraries/bitcoin/armory.cpp:74: undefined reference to `fc::romix::deriveKey(std::string const&)'
collect2: error: ld returned 1 exit status
make[2]: *** [programs/client/bitshares_client] Error 1
make[1]: *** [programs/client/CMakeFiles/bitshares_client.dir/all] Error 2
make: *** [all] Error 2
Did you update fc via 'git submodule update'?
-
got something to work on .............
-
Can not build:
[ 93%] Building CXX object programs/client/CMakeFiles/bitshares_client.dir/main.cpp.o
Linking CXX executable bitshares_client
../../libraries/bitcoin/libbitcoin.a(armory.cpp.o): In function `bts::bitcoin::import_armory_wallet(fc::path const&, std::string const&)':
/home/jakub/projekty/bitshares_toolkit/libraries/bitcoin/armory.cpp:73: undefined reference to `fc::romix::romix(unsigned int, unsigned int, std::string)'
/home/jakub/projekty/bitshares_toolkit/libraries/bitcoin/armory.cpp:74: undefined reference to `fc::romix::deriveKey(std::string const&)'
collect2: error: ld returned 1 exit status
make[2]: *** [programs/client/bitshares_client] Error 1
make[1]: *** [programs/client/CMakeFiles/bitshares_client.dir/all] Error 2
make: *** [all] Error 2
Did you update fc via 'git submodule update'?
Yes, thx, just removed my post.
-
Regarding the win binaries - It is no problem for me waiting couple of hours or even a day or two. Just put the info in the OP or in separate thread when they are available.
Thanks.
-
Oh, last one was over. Waiting for Win binaries then, my machine gets a break :)
-
Guess in this run I won't register a delegate:
Required "456,475.97790 XTS"
:'(
-
Guess in this run I won't register a delegate:
Required "456,475.97790 XTS"
:'(
lol
have same concerns :)
-
Order matching seems not to be implemented:
dxtr-wallet (unlocked) >>> blockchain_market_order_book
quote_symbol: USD
base_symbol: XTS
BIDS | ASKS
TOTAL QUANTITY PRICE | PRICE QUANTITY TOTAL COLLATERAL
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
1.0000 USD 0.10000 XTS 10. USD / XTS*| 6.31578947368421052 USD / XTS 14.25000 XTS 90.0000 USD 19.00000 XTS
10.0000 USD 1.00000 XTS 10. USD / XTS*| 11. USD / XTS 10.00000 XTS 110.0000 USD
| 120. USD / XTS 10.00000 XTS 1,200.0000 USD
* Short Order
highest bid (10. USD / XTS* ) >= lowest ask ( 6.31578947368421052 USD / XTS ) ...
-
Guess in this run I won't register a delegate:
Required "456,475.97790 XTS"
:'(
lol
have same concerns :)
Dudes, you gotta build and register as fast as you can.
@toast,
Any manual or guide about how to test the market features ?
-
Order matching seems not to be implemented:
dxtr-wallet (unlocked) >>> blockchain_market_order_book
quote_symbol: USD
base_symbol: XTS
BIDS | ASKS
TOTAL QUANTITY PRICE | PRICE QUANTITY TOTAL COLLATERAL
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
1.0000 USD 0.10000 XTS 10. USD / XTS*| 6.31578947368421052 USD / XTS 14.25000 XTS 90.0000 USD 19.00000 XTS
10.0000 USD 1.00000 XTS 10. USD / XTS*| 11. USD / XTS 10.00000 XTS 110.0000 USD
| 120. USD / XTS 10.00000 XTS 1,200.0000 USD
* Short Order
highest bid (10. USD / XTS* ) >= lowest ask ( 6.31578947368421052 USD / XTS ) ...
It is implemented... the lowest ask is a collateral / cover position that will only get executed when the highest bid is less than 6.3.... the real lowest ask is 11.
From OP:
When listing the order book, "Margin Calls" show up in the ask table even though they shouldn't. This is a display issue as well.
-
20010 insufficient_funds: insufficient funds
"required":"936,261.18318 XTS"
-
BAH! 10million is a bit much. lol
20010 insufficient_funds: insufficient funds
{"required":"10,675,001.72123 XTS"
-
Guess in this run I won't register a delegate:
Required "456,475.97790 XTS"
:'(
lol
have same concerns :)
Dudes, you gotta build and register as fast as you can.
@toast,
Any manual or guide about how to test the market features ?
Guys... if you wait a bit the fee comes down quickly. The new calculation for registration fee and delegate pay is as follows:
foreach block
total_accumulated_fees += all_transactions_fees
delegate_pay = (total_accumulated_fees / 101) * delegate_pay_rate_percent;
total_accumulated_fees -= (total_accumulated_fees / 101)
delegate_registration_fee = delegate_pay * blocks_per_week * 2 / 101
-
Guess in this run I won't register a delegate:
Required "456,475.97790 XTS"
:'(
lol
have same concerns :)
Dudes, you gotta build and register as fast as you can.
@toast,
Any manual or guide about how to test the market features ?
Guys... if you wait a bit the fee comes down quickly. The new calculation for registration fee and delegate pay is as follows:
foreach block
total_accumulated_fees += all_transactions_fees
delegate_pay = (total_accumulated_fees / 101) * delegate_pay_rate_percent;
total_accumulated_fees -= (total_accumulated_fees / 101)
delegate_registration_fee = delegate_pay * blocks_per_week * 2 / 101
Effectively, the fee falls at 1% per block.
-
how many people has more then 10 million XTS to become a delegate......? it is insane
insufficient_funds: insufficient funds
{"required":"9,418,195.82612 XTS","available":" XTS"}
-
The fee is constantly increasing (so far).
There are less than 10 registered delegates.
Decentralisation ?
-
20010 insufficient_funds: insufficient funds
"required":"936,261.18318 XTS"
lol
sent me some funds please, obviously only for market testing...
liondani (unlocked) >>> wallet_account_create liondani
"XTS7yMLAdUFEDdEjuyy75NncKP6N4LDf3SRrdxQEFa4nZLyVaHWaE"
-
how many people has more then 10 million XTS to become a delegate......? it is insane
insufficient_funds: insufficient funds
{"required":"9,418,195.82612 XTS","available":"9,315,232.83328 XTS"}
It is insane, but constantly falling... since you posted it is already down to: "delegate_reg_fee": "6,687,493.63941 XTS". You can monitor this value by calling "config" on the CLI.
-
With risk to repeat myself:
Why dont we have upper and lower bounds on the delegate registration fee.
As we have approval voting inplace there is no need for skyrocketing the delegate registration fee.
Any registered delegate still needs approval to stay elected.
There is no need to tie the registration fee with expected earnings.
-
Something needs to be done about delegate registration fees.
2014-07-15T18:16:37 544 bitcoiners bitcoiners 0.00000 XTS 856,060.89468 XTS register bitcoiners as a delegate 92fe4244
-
BM, did anyone spend 10M xts to register ? it look like network has 101 delegates now. :-* :-* :-* :-*
how many people has more then 10 million XTS to become a delegate......? it is insane
insufficient_funds: insufficient funds
{"required":"9,418,195.82612 XTS","available":"9,315,232.83328 XTS"}
It is insane, but constantly falling... since you posted it is already down to: "delegate_reg_fee": "6,687,493.63941 XTS". You can monitor this value by calling "config" on the CLI.
-
if it would be the original chain would really a delegate get back his money in 2 weeks?
No ! So on real conditions everybody would wait the fees to get reasonable.... and what would happen in the mean time with the network security with no delegate present?
-
Something needs to be done about delegate registration fees.
2014-07-15T18:16:37 544 bitcoiners bitcoiners 0.00000 XTS 856,060.89468 XTS register bitcoiners as a delegate 92fe4244
The registration fees are doing their job of rate-limiting delegate signup. They are currently 4 million, and in an hour will be under 60K if no one else signs up and pays the huge price. In 2 hours it will be under 6000 (assuming few fees are collected during that time).
-
Which command will allow me to get some USD with my XTS ?
-
if it would be the original chain would really a delegate get back his money in 2 weeks?
No ! So on real conditions everybody would wait the fees to get reasonable.... and what would happen in the mean time with the network security with no delegate present?
Initial delegates are trustworthy and new delegates can sign up over the course of the first few days and the chain will be secure.
-
Which command will allow me to get some USD with my XTS ?
Working on a how to... posting shortly.
-
Something needs to be done about delegate registration fees.
2014-07-15T18:16:37 544 bitcoiners bitcoiners 0.00000 XTS 856,060.89468 XTS register bitcoiners as a delegate 92fe4244
The registration fees are doing their job of rate-limiting delegate signup. They are currently 4 million, and in an hour will be under 60K if no one else signs up and pays the huge price. In 2 hours it will be under 6000 (assuming few fees are collected during that time).
so that means only the BitSharesX whales will have the oportumity to be the first delegates, and I assume the last ones as well...
-
This is how you get $$$ (currently no one selling, I bought all 11)
wallet_market_submit_ask dxtr 100 XTS 10 USD
In above you sell 100XTS from dxtr account to anyone willing to buy it at 10$/piece.
-
It seems that my node can not sync with the network.
harvey (unlocked) >>> wallet_list_my_accounts
NAME (* delegate) KEY REGISTERED FAVORITE APPROVED BLOCK PRODUCTION ENABLED
harvey-xts XTS6bp1riWPpUr3v4VGbKRambXQU3JypHwncVryGjFoVouCT6oT8z NO NO 0 N/A
longclaw * XTS5BxLgYL7czZJ2nH5HEbGyXcGuRQyAqRvxgYjmuASuVaSBgqhst 2014-07-15T17:25:30 NO 1 YES
raven * XTS8dUTpfgjUae3jDJcUrJXUxzYnt51pQRLXfJn7uPeCV8QuVh8rY 2014-07-15T17:32:50 NO 1 YES
harvey (unlocked) >>> getinfo
{
"blockchain_head_block_num": 801,
"blockchain_head_block_age": "6 minutes old",
"blockchain_head_block_timestamp": "20140715T185940",
"blockchain_average_delegate_participation": 73.722627737226276,
"blockchain_delegate_pay_rate": 71475283,
"blockchain_blocks_left_in_round": 7,
"blockchain_confirmation_requirement": 1,
"blockchain_share_supply": 199992780978243,
"blockchain_random_seed": "9e7efcd2b987d48cb3cb3a29f4e3960b7519e789",
"blockchain_database_version": 114,
"blockchain_version": 107,
"network_num_connections": 10,
"network_num_connections_max": 200,
"network_protocol_version": 104,
"ntp_time": null,
"ntp_error": null,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "3 years 2 months in the future",
"wallet_unlocked_until_timestamp": "20170915T045019",
"wallet_block_production_enabled": true,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null,
"wallet_version": 100
}
after I wipe the ~/.BitsharesXTS, it will catch the latest block and stuck again:
(wallet closed) >>> getinfo
{
"blockchain_head_block_num": 850,
"blockchain_head_block_age": "3 minutes old",
"blockchain_head_block_timestamp": "20140715T190800",
"blockchain_average_delegate_participation": 84.87394957983193,
"blockchain_delegate_pay_rate": 43895392,
"blockchain_blocks_left_in_round": 59,
"blockchain_confirmation_requirement": 1,
"blockchain_share_supply": 199995566547318,
"blockchain_random_seed": "233b6dc83c73f21c677298759b90a4db9a177bcf",
"blockchain_database_version": 114,
"blockchain_version": 107,
"network_num_connections": 9,
"network_num_connections_max": 200,
"network_protocol_version": 104,
"ntp_time": null,
"ntp_error": null,
"wallet_open": false,
"wallet_unlocked": null,
"wallet_unlocked_until": null,
"wallet_unlocked_until_timestamp": null,
"wallet_block_production_enabled": null,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null,
"wallet_version": 100
}
-
Something needs to be done about delegate registration fees.
2014-07-15T18:16:37 544 bitcoiners bitcoiners 0.00000 XTS 856,060.89468 XTS register bitcoiners as a delegate 92fe4244
The registration fees are doing their job of rate-limiting delegate signup. They are currently 4 million, and in an hour will be under 60K if no one else signs up and pays the huge price. In 2 hours it will be under 6000 (assuming few fees are collected during that time).
I am confused. How is one to know when sign up fee is going to be "optimal"? How long should one wait before registering to get "best" price?
-
Some funds please :)
XTS7yMLAdUFEDdEjuyy75NncKP6N4LDf3SRrdxQEFa4nZLyVaHWaE
-
Error updating email for account using web_wallet
RPC Server Error: In method 'wallet_account_update_registration': 20028 invalid_pay_rate: invalid pay rate
-
Some funds please :)
XTS7yMLAdUFEDdEjuyy75NncKP6N4LDf3SRrdxQEFa4nZLyVaHWaE
Sent.
-
Something needs to be done about delegate registration fees.
2014-07-15T18:16:37 544 bitcoiners bitcoiners 0.00000 XTS 856,060.89468 XTS register bitcoiners as a delegate 92fe4244
The registration fees are doing their job of rate-limiting delegate signup. They are currently 4 million, and in an hour will be under 60K if no one else signs up and pays the huge price. In 2 hours it will be under 6000 (assuming few fees are collected during that time).
so that means only the BitSharesX whales will have the oportumity to be the first delegates, and I assume the last ones as well...
Ridiculous. Even at todays BTSX prices on BTER the current signup fee is only $1800 and falling. That is hardly whale level.
-
Everyone please be mindful that wallet_account_balance always returns the correct value and report it if not. Someone in the last dry run reported a problem with it: https://bitsharestalk.org/index.php?topic=5523.msg74085#msg74085
-
Also, Bitcoin wallet import has been fixed, and should work with Bitcoin Core, BitShares PTS, Armory, Electrum, and Multibit formats. Please test.
-
To create USD you can do a short sell of USD:
wallet_market_submit_short dxtr 10 1 USD
Here you short sell 1 USD expecting USD/XTS ratio go up than 10 (it means you have to pay more for the same amount of XTS => USD is weaker, so short sell was a good idea), however it creates a Margin Call order, that triggers automatically if price of USD/XTS goes under 6.(6) XTS - this means USD got stronger than XTS from previous moment, and you can buy the same amount of XTS for less USD (not what we expected).
-
please , can someone post some seed nodes? From my side the ports at 107.170.30.182 are not working.
-
It seems delegate registration fees are changing quite randomly. It dropped down below 100,000 XTS and now back up to over 10 million..
>> blockchain_get_config
{
"blockchain_id": "5a50ec8c2433e7d5fce13187be2db73d112dcdc6b3766751fbff6162e90836b0",
"symbol": "XTS",
"name": "BitShares XTS",
"version": 107,
"genesis_timestamp": "20140715T000000",
"block_interval": 10,
"target_block_size": 25600,
"max_block_size": 51200,
"max_blockchain_size": 107374182400,
"address_prefix": "XTS",
"min_block_fee": 1,
"inactivity_fee_apr": 10,
"delegate_num": 101,
"delegate_reg_fee": "11,444,627.53767 XTS",
"name_size_max": 63,
"memo_size_max": 19,
"data_size_max": 65536,
"symbol_size_max": 5,
"symbol_size_min": 3,
"asset_reg_fee": "1,155,907,381.30560 XTS",
"asset_shares_max": 1000000000000000,
"proposal_vote_message_max": 1024,
"max_pending_queue_size": 100,
"max_trx_per_second": 10
}
>> blockchain_get_config
{
"blockchain_id": "5a50ec8c2433e7d5fce13187be2db73d112dcdc6b3766751fbff6162e90836b0",
"symbol": "XTS",
"name": "BitShares XTS",
"version": 107,
"genesis_timestamp": "20140715T000000",
"block_interval": 10,
"target_block_size": 25600,
"max_block_size": 51200,
"max_blockchain_size": 107374182400,
"address_prefix": "XTS",
"min_block_fee": 1,
"inactivity_fee_apr": 10,
"delegate_num": 101,
"delegate_reg_fee": "116,088.31803 XTS",
"name_size_max": 63,
"memo_size_max": 19,
"data_size_max": 65536,
"symbol_size_max": 5,
"symbol_size_min": 3,
"asset_reg_fee": "11,724,920.12160 XTS",
"asset_shares_max": 1000000000000000,
"proposal_vote_message_max": 1024,
"max_pending_queue_size": 100,
"max_trx_per_second": 10
}
-
Funds please?
Account Key: XTS542XFkGR9Fvj4hdQZYivZeEEDQCHv3gqA7TUzPPG4eUJ3SSKpm
thx
-
It seems delegate registration fees are changing quite randomly. It dropped down below 100,000 XTS and now back up to over 10 million..
>> blockchain_get_config
{
"blockchain_id": "5a50ec8c2433e7d5fce13187be2db73d112dcdc6b3766751fbff6162e90836b0",
"symbol": "XTS",
"name": "BitShares XTS",
"version": 107,
"genesis_timestamp": "20140715T000000",
"block_interval": 10,
"target_block_size": 25600,
"max_block_size": 51200,
"max_blockchain_size": 107374182400,
"address_prefix": "XTS",
"min_block_fee": 1,
"inactivity_fee_apr": 10,
"delegate_num": 101,
"delegate_reg_fee": "11,444,627.53767 XTS",
"name_size_max": 63,
"memo_size_max": 19,
"data_size_max": 65536,
"symbol_size_max": 5,
"symbol_size_min": 3,
"asset_reg_fee": "1,155,907,381.30560 XTS",
"asset_shares_max": 1000000000000000,
"proposal_vote_message_max": 1024,
"max_pending_queue_size": 100,
"max_trx_per_second": 10
}
>> blockchain_get_config
{
"blockchain_id": "5a50ec8c2433e7d5fce13187be2db73d112dcdc6b3766751fbff6162e90836b0",
"symbol": "XTS",
"name": "BitShares XTS",
"version": 107,
"genesis_timestamp": "20140715T000000",
"block_interval": 10,
"target_block_size": 25600,
"max_block_size": 51200,
"max_blockchain_size": 107374182400,
"address_prefix": "XTS",
"min_block_fee": 1,
"inactivity_fee_apr": 10,
"delegate_num": 101,
"delegate_reg_fee": "116,088.31803 XTS",
"name_size_max": 63,
"memo_size_max": 19,
"data_size_max": 65536,
"symbol_size_max": 5,
"symbol_size_min": 3,
"asset_reg_fee": "11,724,920.12160 XTS",
"asset_shares_max": 1000000000000000,
"proposal_vote_message_max": 1024,
"max_pending_queue_size": 100,
"max_trx_per_second": 10
}
No it goes with what BM said - the price melts down to amount the next candidate is willing to pay, if he pays - it is automatically increasing total_fees and reseting the clock waiting for next rich candidate for a delegate to participate.
But it goes along with: Rich get richer, poor get poorer...
-
Funds please?
Account Key: XTS542XFkGR9Fvj4hdQZYivZeEEDQCHv3gqA7TUzPPG4eUJ3SSKpm
thx
Sent.
-
Something needs to be done about delegate registration fees.
2014-07-15T18:16:37 544 bitcoiners bitcoiners 0.00000 XTS 856,060.89468 XTS register bitcoiners as a delegate 92fe4244
The registration fees are doing their job of rate-limiting delegate signup. They are currently 4 million, and in an hour will be under 60K if no one else signs up and pays the huge price. In 2 hours it will be under 6000 (assuming few fees are collected during that time).
so that means only the BitSharesX whales will have the oportumity to be the first delegates, and I assume the last ones as well...
Ridiculous. Even at todays BTSX prices on BTER the current signup fee is only $1800 and falling. That is hardly whale level.
I think you are wrong. To get a delegate right now it costs 6,312,291 XTS
that means 6,312,291*0.0000203 BTC = 128.1395073 BTC * $620 = $79,446
liondani (unlocked) >>> config
{
"blockchain_id": "5a50ec8c2433e7d5fce13187be2db73d112dcdc6b3766751fbff6162e90836b0",
"symbol": "XTS",
"name": "BitShares XTS",
"version": 107,
"genesis_timestamp": "20140715T000000",
"block_interval": 10,
"target_block_size": 25600,
"max_block_size": 51200,
"max_blockchain_size": 107374182400,
"address_prefix": "XTS",
"min_block_fee": 1,
"inactivity_fee_apr": 10,
"delegate_num": 101,
"delegate_reg_fee": "6,312,291.61188 XTS",
"name_size_max": 63,
"memo_size_max": 19,
"data_size_max": 65536,
"symbol_size_max": 5,
"symbol_size_min": 3,
"asset_reg_fee": "637,541,452.80000 XTS",
"asset_shares_max": 1000000000000000,
"proposal_vote_message_max": 1024,
"max_pending_queue_size": 100,
"max_trx_per_second": 10
}
-
Is this thread gonna be about expensive play dough?
On another note, I said that ‘I will not try to be a delegate’ (post is dilated now due to semi-smooth start to this run).
So I made the right decision and end up saving a lot of fake money! Should I jump with joy?
-
I can not cover a short position (I think I'm doing it right way, and have sufficient funds...):
dxtr-wallet (unlocked) >>> blockchain_market_list_shorts USD
TYPE QUANTITY PRICE BALANCE COST COLLATERAL ID
--------------------------------------------------------------------------------------------------------------------------------
short_order 111.11111 XTS 0.9 USD / XTS 111.11111 XTS 99.9999 USD N/A XTS7H8Bnrk5iFHP9rXcj6Kj5VJPRbd6aWJPz
dxtr-wallet (unlocked) >>> wallet_market_cover dxtr 10 USD XTS7H8Bnrk5iFHP9rXcj6Kj5VJPRbd6aWJPz
10 assert_exception: Assert Exception
order_to_cover.valid():
{}
th_a wallet.cpp:3215 cover_short
{"from_account_name":"dxtr","real_quantity_usd":10,"quote_symbol":"USD","owner_address":"XTS7H8Bnrk5iFHP9rXcj6Kj5VJPRbd6aWJPz","sign":true}
th_a wallet.cpp:3288 cover_short
{}
th_a common_api_client.cpp:1299 wallet_market_cover
{"command":"wallet_market_cover"}
th_a cli.cpp:538 execute_command
-
By popular demand, the delegate fee calculation is clearly way more volatile than I intended so we are going to reset this dryrun before we get too far into it.
New calculations:
delegate_pay = total_accumulated_fees / (blocks_per_day*14)
delegate_registration = delegate_pay * blocks_per_hour * 2 / 101
The effect of this change is that delegate pay will rise much slower, and registration will have a much smaller impact on delegate pay. (14 days vs 2 hours).
-
Loading blockchain from "/var/bts/chain"
Loading config "/var/bts/config.json"
------------ error --------------
10001 db_in_use_exception: Database in Use
Unable to open database /var/bts/peers.leveldb
IO error: lock /var/bts/peers.leveldb/LOCK: Resource temporarily unavail
able
{"db":"/var/bts/peers.leveldb","msg":"IO error: lock /var/bts/peers.leveldb/
LOCK: Resource temporarily unavailable"}
p2p level_pod_map.hpp:45 open
zsh: segmentation fault /var/bts/bitshares_toolkit/programs/client/bitshares_cl
ient --data-dir 6553
also ports are not releasing and full reboot is required.
-
Is this thread gonna be about expensive play dough?
On another note, I said that ‘I will not try to be a delegate’ (post is dilated now due to semi-smooth start to this run).
So I made the right decision and end up saving a lot of fake money! Should I jump with joy?
It is obvious not a problem with Dry Runs and fake money, we are only discussing it now so maybe we prevent problems on the original chain run...
I guess on the real chain everything will be smoother due to real coin value...
-
Some funds please :)
XTS7yMLAdUFEDdEjuyy75NncKP6N4LDf3SRrdxQEFa4nZLyVaHWaE
Sent.
thank you :)
-
We've reset, please wipe your chain directory to reconnect
-
Loading blockchain from "/var/bts/chain"
Loading config "/var/bts/config.json"
------------ error --------------
10001 db_in_use_exception: Database in Use
Unable to open database /var/bts/peers.leveldb
IO error: lock /var/bts/peers.leveldb/LOCK: Resource temporarily unavail
able
{"db":"/var/bts/peers.leveldb","msg":"IO error: lock /var/bts/peers.leveldb/
LOCK: Resource temporarily unavailable"}
p2p level_pod_map.hpp:45 open
zsh: segmentation fault /var/bts/bitshares_toolkit/programs/client/bitshares_cl
ient --data-dir 6553
also ports are not releasing and full reboot is required.
had same issue
and was fixed after a hard reset...
On this Dry Run and Dry Run 6 if I can remember well (linux Mint 17 64bit)
-
Tried to import my private key but I have this error:
default (unlocked) >>> wallet_account_create spartako
default (unlocked) >>>wallet_import_private_key 5...BTC..PRIVATE...KEY.... spartako
10 assert_exception: Assert Exception
oacct.valid(): just imported a key but now the key has no owner
{}
th_a client.cpp:1733 wallet_import_private_key
{}
th_a common_api_client.cpp:563 wallet_import_private_key
{"command":"wallet_import_private_key"}
th_a cli.cpp:538 execute_command
EDIT: even if there is this error after wallet_rescan_blockchain command the balance is CORRECT
-
I had to up my RAM allocation to compile this Dry Run version.
Off we go:
wallet_approve_delegate fox
-
Tried to import my private key but I have this error:
default (unlocked) >>> wallet_account_create spartako
default (unlocked) >>>wallet_import_private_key 5...BTC..PRIVATE...KEY.... spartako
10 assert_exception: Assert Exception
oacct.valid(): just imported a key but now the key has no owner
{}
th_a client.cpp:1733 wallet_import_private_key
{}
th_a common_api_client.cpp:563 wallet_import_private_key
{"command":"wallet_import_private_key"}
th_a cli.cpp:538 execute_command
EDIT: even if there is this error after wallet_rescan_blockchain command the balance is CORRECT
Known issue, Toast is on it.
-
I just updated the OP with example commands.
-
I just updated the OP with Mac GUI
-
I made an wallet_account_export_to_json before I wipe the directories and I rebuild....
After rebuild I made "succesfull" wallet_create_from_json and the wallet is there but not the funds!
I made a blockchain_rescan but wallet_account_balance is at zero funds....
any thought's or is it normal due the reset?
PS please sent me some funds again at XTS7yMLAdUFEDdEjuyy75NncKP6N4LDf3SRrdxQEFa4nZLyVaHWaE
-
I made an wallet_account_export_to_json before I wipe the directories and I rebuild....
After rebuild I made "succesfull" wallet_create_from_json and the wallet is there but not the funds!
I made a blockchain_rescan but wallet_account_balance is at zero funds....
any thought's or is it normal due the reset?
PS please sent me some funds again at XTS7yMLAdUFEDdEjuyy75NncKP6N4LDf3SRrdxQEFa4nZLyVaHWaE
It's expected because nobody made a transfer to you to those keys on the new chain
-
I made an wallet_account_export_to_json before I wipe the directories and I rebuild....
After rebuild I made "succesfull" wallet_create_from_json and the wallet is there but not the funds!
I made a blockchain_rescan but wallet_account_balance is at zero funds....
any thought's or is it normal due the reset?
PS please sent me some funds again at XTS7yMLAdUFEDdEjuyy75NncKP6N4LDf3SRrdxQEFa4nZLyVaHWaE
It's expected because nobody made a transfer to you to those keys on the new chain
You can try transferring to the same account key you posted from earlier in the reset and see if it works
-
Can someone explain the reason we had to erase the block chain? Just curious
-
some funds pls XTS72nAmESGdWTRRTHeUmsTEvS2dCQe93KHoq2PbWijBE5qK3gCYM thx
-
Can someone explain the reason we had to erase the block chain? Just curious
We did a hard fork and it was easier to reset than do it live since not many people had joined at that time
-
You purposely forked?
-
please sent me some funds again at XTS7yMLAdUFEDdEjuyy75NncKP6N4LDf3SRrdxQEFa4nZLyVaHWaE
-
You purposely forked?
yes
-
By popular demand, the delegate fee calculation is clearly way more volatile than I intended so we are going to reset this dryrun before we get too far into it.
New calculations:
delegate_pay = total_accumulated_fees / (blocks_per_day*14)
delegate_registration = delegate_pay * blocks_per_hour * 2 / 101
The effect of this change is that delegate pay will rise much slower, and registration will have a much smaller impact on delegate pay. (14 days vs 2 hours).
Seems registration fee went from very high to now very low
"delegate_reg_fee": "0.00121 XTS",
Is this expected? Should it not be a bit higher?
-
still asking for half million for registration :P :P :P :P :P :P :P :P :P :P :P :P :P 8) 8) 8) 8) 8) 8) :o :o :o :o :o :o
config
{
"blockchain_id": "5a50ec8c2433e7d5fce13187be2db73d112dcdc6b3766751fbff6162e90836b0",
"symbol": "XTS",
"name": "BitShares XTS",
"version": 107,
"genesis_timestamp": "20140715T000000",
"block_interval": 10,
"target_block_size": 25600,
"max_block_size": 51200,
"max_blockchain_size": 107374182400,
"address_prefix": "XTS",
"min_block_fee": 1,
"inactivity_fee_apr": 10,
"delegate_num": 101,
"delegate_reg_fee": "4,775,949.86100 XTS",
"name_size_max": 63,
"memo_size_max": 19,
"data_size_max": 65536,
"symbol_size_max": 5,
"symbol_size_min": 3,
"asset_reg_fee": "482,370,935.96160 XTS",
"asset_shares_max": 1000000000000000,
"proposal_vote_message_max": 1024,
"max_pending_queue_size": 100,
"max_trx_per_second": 10
}
By popular demand, the delegate fee calculation is clearly way more volatile than I intended so we are going to reset this dryrun before we get too far into it.
New calculations:
delegate_pay = total_accumulated_fees / (blocks_per_day*14)
delegate_registration = delegate_pay * blocks_per_hour * 2 / 101
The effect of this change is that delegate pay will rise much slower, and registration will have a much smaller impact on delegate pay. (14 days vs 2 hours).
Seems registration fee went from very high to now very low
"delegate_reg_fee": "0.00121 XTS",
Is this expected? Should it not be a bit higher?
-
still asking for half million for registration :P :P :P :P :P :P :P :P :P :P :P :P :P 8) 8) 8) 8) 8) 8) :o :o :o :o :o :o
config
{
"blockchain_id": "5a50ec8c2433e7d5fce13187be2db73d112dcdc6b3766751fbff6162e90836b0",
"symbol": "XTS",
"name": "BitShares XTS",
"version": 107,
"genesis_timestamp": "20140715T000000",
"block_interval": 10,
"target_block_size": 25600,
"max_block_size": 51200,
"max_blockchain_size": 107374182400,
"address_prefix": "XTS",
"min_block_fee": 1,
"inactivity_fee_apr": 10,
"delegate_num": 101,
"delegate_reg_fee": "4,775,949.86100 XTS",
"name_size_max": 63,
"memo_size_max": 19,
"data_size_max": 65536,
"symbol_size_max": 5,
"symbol_size_min": 3,
"asset_reg_fee": "482,370,935.96160 XTS",
"asset_shares_max": 1000000000000000,
"proposal_vote_message_max": 1024,
"max_pending_queue_size": 100,
"max_trx_per_second": 10
}
By popular demand, the delegate fee calculation is clearly way more volatile than I intended so we are going to reset this dryrun before we get too far into it.
New calculations:
delegate_pay = total_accumulated_fees / (blocks_per_day*14)
delegate_registration = delegate_pay * blocks_per_hour * 2 / 101
The effect of this change is that delegate pay will rise much slower, and registration will have a much smaller impact on delegate pay. (14 days vs 2 hours).
Seems registration fee went from very high to now very low
"delegate_reg_fee": "0.00121 XTS",
Is this expected? Should it not be a bit higher?
You are on an outdated chain, rebuild and wipe you data-dir
default (locked) >>> config
{
"blockchain_id": "4b9f25c5e7204fd2af460d7a63fad3ce758e873ade2679c6ac14cfb62d4f05a7",
"symbol": "XTS",
"name": "BitShares XTS",
"version": 107,
"genesis_timestamp": "20140715T000001",
"block_interval": 10,
"target_block_size": 25600,
"max_block_size": 51200,
"max_blockchain_size": 107374182400,
"address_prefix": "XTS",
"min_block_fee": 1,
"inactivity_fee_apr": 10,
"delegate_num": 101,
"delegate_reg_fee": "0.00128 XTS",
"name_size_max": 63,
"memo_size_max": 19,
"data_size_max": 65536,
"symbol_size_max": 5,
"symbol_size_min": 3,
"asset_reg_fee": "21.77280 XTS",
"asset_shares_max": 1000000000000000,
"proposal_vote_message_max": 1024,
"max_pending_queue_size": 100,
"max_trx_per_second": 10
}
-
This seems strange.
I tried covering part of a cover_order, but now it is gone from order list.. Is this expected?
>>> wallet_market_order_list USD XTS
TYPE QUANTITY PRICE BALANCE COST COLLATERAL ID
--------------------------------------------------------------------------------------------------------------------------------
cover_order 3.75037 XTS 0.01333201790756645 USD / XTS 0.0500 USD 0.0499 USD 5.00050 XTS XTS5u2Utwb2E7AiBcG1HmjvuxSMpKPzw9KNu
>>> wallet_market_cover bitcoiners 0.1 USD XTS5u2Utwb2E7AiBcG1HmjvuxSMpKPzw9KNu
>>> wallet_account_transaction_history
...
2014-07-15T23:39:25 1048 bitcoiners ORDER-5u2Utwb2 0.1000 USD 0.10000 XTS cover ORDER-5u2Utwb2 2cbd1f18
>>> wallet_market_order_list USD XTS
No market orders found.
-
what am i doing wrong when attempting to buy USD
default (unlocked) >>> wallet_market_submit_bid clout 700 XTS 0.016308636848902 USD
20010 insufficient_funds: insufficient funds
{"required":"11.4160 USD","available":"0.0000 USD"}
th_a wallet.cpp:373 withdraw_to_transaction
{"amount":114160,"asset_id":22,"from_account_address":"XTS9JQK4uL4JttHv2x9gCECSqE4q33Z3sPs9","trx":{"expiration":"19700101T000000","delegate_slate_id":null,"operations":[],"signatures":[]},"required_signatures":["XTSE9E61MPc1u33V3EBcuNZmDUtpBfsNjLhR"]}
th_a wallet.cpp:374 withdraw_to_transaction
{"from_account_name":"clout","real_quantity":700,"quantity_symbol":"XTS","quote_price":0.016308636848901999,"quote_symbol":"USD","sign":true}
th_a wallet.cpp:2972 submit_bid
{}
th_a common_api_client.cpp:1251 wallet_market_submit_bid
{"command":"wallet_market_submit_bid"}
th_a cli.cpp:538 execute_command
-
I have imported my btc wallet using wallet_import_armory and have rescaned blockchain,but no balance found.why?
-
what am i doing wrong when attempting to buy USD
default (unlocked) >>> wallet_market_submit_bid clout 700 XTS 0.016308636848902 USD
20010 insufficient_funds: insufficient funds
{"required":"11.4160 USD","available":"0.0000 USD"}
th_a wallet.cpp:373 withdraw_to_transaction
{"amount":114160,"asset_id":22,"from_account_address":"XTS9JQK4uL4JttHv2x9gCECSqE4q33Z3sPs9","trx":{"expiration":"19700101T000000","delegate_slate_id":null,"operations":[],"signatures":[]},"required_signatures":["XTSE9E61MPc1u33V3EBcuNZmDUtpBfsNjLhR"]}
th_a wallet.cpp:374 withdraw_to_transaction
{"from_account_name":"clout","real_quantity":700,"quantity_symbol":"XTS","quote_price":0.016308636848901999,"quote_symbol":"USD","sign":true}
th_a wallet.cpp:2972 submit_bid
{}
th_a common_api_client.cpp:1251 wallet_market_submit_bid
{"command":"wallet_market_submit_bid"}
th_a cli.cpp:538 execute_command
This command is actually sell USD for 700XTS @0.016308636848902 USD/XTS
If you want to buy USD, try this.
ask clout 700 XTS 0.016308636848902 USD
-
what am i doing wrong when attempting to buy USD
default (unlocked) >>> wallet_market_submit_bid clout 700 XTS 0.016308636848902 USD
20010 insufficient_funds: insufficient funds
{"required":"11.4160 USD","available":"0.0000 USD"}
th_a wallet.cpp:373 withdraw_to_transaction
{"amount":114160,"asset_id":22,"from_account_address":"XTS9JQK4uL4JttHv2x9gCECSqE4q33Z3sPs9","trx":{"expiration":"19700101T000000","delegate_slate_id":null,"operations":[],"signatures":[]},"required_signatures":["XTSE9E61MPc1u33V3EBcuNZmDUtpBfsNjLhR"]}
th_a wallet.cpp:374 withdraw_to_transaction
{"from_account_name":"clout","real_quantity":700,"quantity_symbol":"XTS","quote_price":0.016308636848901999,"quote_symbol":"USD","sign":true}
th_a wallet.cpp:2972 submit_bid
{}
th_a common_api_client.cpp:1251 wallet_market_submit_bid
{"command":"wallet_market_submit_bid"}
th_a cli.cpp:538 execute_command
This command is actually sell USD for 700XTS @0.016308636848902 USD/XTS
If you want to buy USD, try this.
ask clout 700 XTS 0.016308636848902 USD
isn't that backward?
-
import from multibit wallet failed.
default (unlocked) >>> wallet_import_multibit /home/alt/MultiBit/multibit.wallet xxxxxxxxx nobody2
Successfully imported 0 keys from: multibit.wallet
-
the fee to register as delegate is only 0.1 XTS now?
2014-07-15T23:37:43 1039 delegate-alt delegate-alt 0.00000 XTS 0.10129 XTS register delegate-alt as a delegate 172c9dc2
2014-07-15T23:38:12 1041 delegate-alt delegate-dorian 0.00000 XTS 0.10129 XTS register delegate-dorian as a delegate edf13390
2014-07-15T23:38:17 1041 delegate-alt delegate-baozi 0.00000 XTS 0.10065 XTS register delegate-baozi as a delegate 38e5c7ca
-
isn't that backward?
Nope.
Ask -- is asking to sell XTS at some price in USD (equivalent to bidding to buy USD for some XTS amount)
Bid -- is biding to buy XTS at some price in USD (equivalent to asking to sell USD for some XTS amount)
-
our chain forked ----" "blockchain_head_block_age": "63 minutes old","
ocked) >>> info
{
"blockchain_head_block_num": 1034,
"blockchain_head_block_age": "63 minutes old",
"blockchain_head_block_timestamp": "20140715T233700",
"blockchain_average_delegate_participation": 20.654396728016359,
"blockchain_delegate_pay_rate": 18,
"blockchain_blocks_left_in_round": 77,
"blockchain_confirmation_requirement": 1,
"blockchain_accumulated_fees": "21.89463 XTS",
"blockchain_share_supply": 199999997792460,
"blockchain_random_seed": "57ba59f7a2ee52c976d3e0385d409c327d1d52f6",
"blockchain_database_version": 114,
"blockchain_version": 107,
"network_num_connections": 8,
"network_num_connections_max": 200,
"network_protocol_version": 104,
"ntp_time": null,
"ntp_error": null,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "15 weeks in the future",
"wallet_unlocked_until_timestamp": "20141026T214645",
"wallet_block_production_enabled": false,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null,
"wallet_version": 100
}
-
Except xts is the "base" so I think it is backwards... unless bid means want to buy base using quote asset
Sent from my SCH-I535 using Tapatalk
-
Typical market terminology should be used
Market order sell
Market order buy
Limit order sell/buy
Stop-market
Stop and stop limit
-
Except xts is the "base" so I think it is backwards... unless bid means want to buy base using quote asset
Sent from my SCH-I535 using Tapatalk
help wallet_market_submit_bid
Usage:
wallet_market_submit_bid <from_account_name> <quantity> <quantity_symbol> <quote_price> <quote_symbol> Used to place a request to buy a quantity of assets at a price specified in another asset
Used to place a request to buy a quantity of assets at a price specified in another asset
Parameters:
from_account_name (account_name, required): the account that will provide funds for the bid
quantity (real_amount, required): the quantity of items you would like to buy
quantity_symbol (asset_symbol, required): the type of items you would like to buy
quote_price (real_amount, required): the price you would like to pay
quote_symbol (asset_symbol, required): the type of asset you would like to pay with
It doesn't really distinguish base or otherwise. Just what asset your bidding on and at what price you want to pay. This could be made a little clearer perhaps.
-
BUG........
i am stuck at "blockchain_head_block_num": 1034, for 10 mins now.
and got following error....
--- there are now 6 active connections to the p2p network
--- there are now 5 active connections to the p2p network
(wallet closed) >>>
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffe6ffd700 (LWP 28286)]
0x000000000062f56b in fc::exception::to_detail_string (this=this@entry=0x7fffdc026dc0, ll=..., ll@entry=...) at /home/daniel/.bitshares_toolkit/libraries/fc/src/exception.cpp:142
142 /home/daniel/.bitshares_toolkit/libraries/fc/src/exception.cpp: No such file or directory.
(gdb)
-
This is my balance :D
default (unlocked) >>> wallet_account_balance
ACCOUNT BALANCE
------------------------------------------------------------
alt 199,967,998.0003 USD
489,897.20000 XTS
This is the transactions history
2014-07-16T00:44:05 1434 alt ORDER-4nRtXFXW 100.00000 XTS 0.10000 XTS sell 100 XTS @ 1e+08 USD c1e0b1c4
2014-07-16T00:47:04 1452 alt ORDER-Nnwz8BnB 1.00000 XTS 0.10000 XTS short 1e+08 USD @ 1e+08 USD/XTS 5570da9d
2014-07-16T00:47:20 ERROR ORDER-4nRtXFXW UNKNOWN 0.99967 XTS 0.00000 XTS pay ask @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-4nRtXFXW alt 99,967,999.0003 USD 0.00000 XTS fill ask @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB UNKNOWN 1,240.0000 USD 999.99999 XTS pay bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB UNKNOWN 60.0000 USD 10.00000 XTS pay bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB UNKNOWN 12,245.0503 USD 9,955.32532 XTS pay bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB UNKNOWN 8,927.8001 USD 9,919.77780 XTS pay bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB UNKNOWN 70.0000 USD 10.00000 XTS pay bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB UNKNOWN 8.0000 USD 10.00000 XTS pay bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB UNKNOWN 7,000.0000 USD 9,999.99993 XTS pay bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB UNKNOWN 99,967,999.0003 USD 0.00000 XTS pay bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB UNKNOWN 4,990.0001 USD 9,980.00016 XTS pay bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB UNKNOWN 3.0000 USD 10.00000 XTS pay bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB UNKNOWN 0.1600 USD 1.00000 XTS pay bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB alt 0.00000 XTS 10.00000 XTS fill bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB alt 0.00000 XTS 10.00000 XTS fill bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB alt 0.99967 XTS 0.00000 XTS fill bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB alt 0.00000 XTS 10.00000 XTS fill bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB alt 0.00001 XTS 999.99999 XTS fill bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB alt 0.00012 XTS 9,955.32532 XTS fill bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB alt 0.00008 XTS 9,919.77780 XTS fill bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB alt 0.00000 XTS 10.00000 XTS fill bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB alt 0.00007 XTS 9,999.99993 XTS fill bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB alt 0.00004 XTS 9,980.00016 XTS fill bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB alt 0.00000 XTS 1.00000 XTS fill bid @ 99999999. USD / XTS 00000000
2014-07-16T00:48:53 1463 alt ORDER-CCFJNYAZ 1.00000 XTS 0.10000 XTS short 1e+08 USD @ 1e+08 USD/XTS 336c1e64
2014-07-16T00:49:10 ERROR ORDER-4nRtXFXW UNKNOWN 1.00000 XTS 0.00000 XTS pay ask @ 99999999. USD / XTS 00000000
2014-07-16T00:49:10 ERROR ORDER-4nRtXFXW alt 99,999,999.0000 USD 0.00000 XTS fill ask @ 99999999. USD / XTS 00000000
2014-07-16T00:49:10 ERROR ORDER-4nRtXFXW alt 99,999,999.0000 USD 0.00000 XTS fill ask @ 99999999. USD / XTS 00000000
2014-07-16T00:49:10 ERROR ORDER-CCFJNYAZ UNKNOWN 99,999,999.0000 USD 0.00000 XTS pay bid @ 99999999. USD / XTS 00000000
2014-07-16T00:49:10 ERROR ORDER-CCFJNYAZ alt 1.00000 XTS 0.00000 XTS fill bid @ 99999999. USD / XTS 00000000
-
Think of bitstamp. You sell xts by asking for usd. You bid with usd to buy btc.
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
-
"blockchain_head_block_age": "39 minutes old",
"blockchain_average_delegate_participation": 30.421686746987952,
liondani (unlocked) >>> info
{
"blockchain_head_block_num": 1268,
"blockchain_head_block_age": "39 minutes old",
"blockchain_head_block_timestamp": "20140716T001630",
"blockchain_average_delegate_participation": 30.421686746987952,
"blockchain_delegate_pay_rate": 25,
"blockchain_blocks_left_in_round": 45,
"blockchain_confirmation_requirement": 1,
"blockchain_accumulated_fees": "31.24339 XTS",
"blockchain_share_supply": 199999996857584,
"blockchain_random_seed": "21bace54494ffa1a3ec179bb49a70142d86e3c62",
"blockchain_database_version": 114,
"blockchain_version": 107,
"network_num_connections": 8,
"network_num_connections_max": 200,
"network_protocol_version": 104,
"ntp_time": "20140716T005503",
"ntp_error": -0.036746000000000001,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "12 days in the future",
"wallet_unlocked_until_timestamp": "20140727T122835",
"wallet_block_production_enabled": false,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null,
"wallet_version": 100
}
-
isn't that backward?
Nope.
Ask -- is asking to sell XTS at some price in USD (equivalent to bidding to buy USD for some XTS amount)
Bid -- is biding to buy XTS at some price in USD (equivalent to asking to sell USD for some XTS amount)
thats backward. it a USD market. you are buying and selling USD. also my shorts are not getting matched with bids (or asks in this case) that are in the order book.
-
20010 insufficient_funds: insufficient funds
"required":"936,261.18318 XTS"
wipe your data folder and rebuild... (there was a hard fork)
"delegate_reg_fee": "0.00178 XTS",
liondani (unlocked) >>> config
{
"blockchain_id": "4b9f25c5e7204fd2af460d7a63fad3ce758e873ade2679c6ac14cfb62d4f05a7",
"symbol": "XTS",
"name": "BitShares XTS",
"version": 107,
"genesis_timestamp": "20140715T000001",
"block_interval": 10,
"target_block_size": 25600,
"max_block_size": 51200,
"max_blockchain_size": 107374182400,
"address_prefix": "XTS",
"min_block_fee": 1,
"inactivity_fee_apr": 10,
"delegate_num": 101,
"delegate_reg_fee": "0.00178 XTS",
"name_size_max": 63,
"memo_size_max": 19,
"data_size_max": 65536,
"symbol_size_max": 5,
"symbol_size_min": 3,
"asset_reg_fee": "30.24000 XTS",
"asset_shares_max": 1000000000000000,
"proposal_vote_message_max": 1024,
"max_pending_queue_size": 100,
"max_trx_per_second": 10
}
-
My new balance
default (unlocked) >>> wallet_account_balance
ACCOUNT BALANCE
------------------------------------------------------------
alt 110,000,000,899.9999 USD
489,796.00000 XTS
-
Margin Call not get executed in some cases, not sure it's a bug or due to market depth.
Maybe order matching need to enabled/disabled the same with margin call.
This is my balance :D
default (unlocked) >>> wallet_account_balance
ACCOUNT BALANCE
------------------------------------------------------------
alt 199,967,998.0003 USD
489,897.20000 XTS
This is the transactions history
2014-07-16T00:44:05 1434 alt ORDER-4nRtXFXW 100.00000 XTS 0.10000 XTS sell 100 XTS @ 1e+08 USD c1e0b1c4
2014-07-16T00:47:04 1452 alt ORDER-Nnwz8BnB 1.00000 XTS 0.10000 XTS short 1e+08 USD @ 1e+08 USD/XTS 5570da9d
2014-07-16T00:47:20 ERROR ORDER-4nRtXFXW UNKNOWN 0.99967 XTS 0.00000 XTS pay ask @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-4nRtXFXW alt 99,967,999.0003 USD 0.00000 XTS fill ask @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB UNKNOWN 1,240.0000 USD 999.99999 XTS pay bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB UNKNOWN 60.0000 USD 10.00000 XTS pay bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB UNKNOWN 12,245.0503 USD 9,955.32532 XTS pay bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB UNKNOWN 8,927.8001 USD 9,919.77780 XTS pay bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB UNKNOWN 70.0000 USD 10.00000 XTS pay bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB UNKNOWN 8.0000 USD 10.00000 XTS pay bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB UNKNOWN 7,000.0000 USD 9,999.99993 XTS pay bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB UNKNOWN 99,967,999.0003 USD 0.00000 XTS pay bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB UNKNOWN 4,990.0001 USD 9,980.00016 XTS pay bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB UNKNOWN 3.0000 USD 10.00000 XTS pay bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB UNKNOWN 0.1600 USD 1.00000 XTS pay bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB alt 0.00000 XTS 10.00000 XTS fill bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB alt 0.00000 XTS 10.00000 XTS fill bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB alt 0.99967 XTS 0.00000 XTS fill bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB alt 0.00000 XTS 10.00000 XTS fill bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB alt 0.00001 XTS 999.99999 XTS fill bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB alt 0.00012 XTS 9,955.32532 XTS fill bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB alt 0.00008 XTS 9,919.77780 XTS fill bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB alt 0.00000 XTS 10.00000 XTS fill bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB alt 0.00007 XTS 9,999.99993 XTS fill bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB alt 0.00004 XTS 9,980.00016 XTS fill bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB alt 0.00000 XTS 1.00000 XTS fill bid @ 99999999. USD / XTS 00000000
2014-07-16T00:48:53 1463 alt ORDER-CCFJNYAZ 1.00000 XTS 0.10000 XTS short 1e+08 USD @ 1e+08 USD/XTS 336c1e64
2014-07-16T00:49:10 ERROR ORDER-4nRtXFXW UNKNOWN 1.00000 XTS 0.00000 XTS pay ask @ 99999999. USD / XTS 00000000
2014-07-16T00:49:10 ERROR ORDER-4nRtXFXW alt 99,999,999.0000 USD 0.00000 XTS fill ask @ 99999999. USD / XTS 00000000
2014-07-16T00:49:10 ERROR ORDER-4nRtXFXW alt 99,999,999.0000 USD 0.00000 XTS fill ask @ 99999999. USD / XTS 00000000
2014-07-16T00:49:10 ERROR ORDER-CCFJNYAZ UNKNOWN 99,999,999.0000 USD 0.00000 XTS pay bid @ 99999999. USD / XTS 00000000
2014-07-16T00:49:10 ERROR ORDER-CCFJNYAZ alt 1.00000 XTS 0.00000 XTS fill bid @ 99999999. USD / XTS 00000000
-
My new balance
default (unlocked) >>> wallet_account_balance
ACCOUNT BALANCE
------------------------------------------------------------
alt 110,000,000,899.9999 USD
489,796.00000 XTS
some balance for test,thanks.
XTSEcqxbtU2GaaC2AvnHcr4gtjpgzD6snMYc
-
isn't that backward?
Nope.
Ask -- is asking to sell XTS at some price in USD (equivalent to bidding to buy USD for some XTS amount)
Bid -- is biding to buy XTS at some price in USD (equivalent to asking to sell USD for some XTS amount)
thats backward. it a USD market. you are buying and selling USD. also my shorts are not getting matched with bids (or asks in this case) that are in the order book.
is XTS/USD a usd market? or is USD/XTS a usd market. They both are. Its just your preference of how you look at it. Either way your trading USD for XTS.
a bid for XTS/USD is the same as an ask for USD/XTS
if you want to buy USD you bid on USD priced in XTS (your selling XTS)
if you want to sell USD you ask on USD priced in XTS (your buying XTS)
[this is more akin to how the function call is arranged]
wallet_market_submit_bid <from_account_name> <quantity> <quantity_symbol> <quote_price> <quote_symbol>
said another way:
if you want to buy USD you bid some amount of XTS for the USD your buying
if you want to sell USD you ask for some amount of XTS for the USD your selling
-
import my pts wallet failed :(
wallet.dat: file size not a multiple of the pagesize
wallet.dat: file size not a multiple of the pagesize
13 11DbException: Db::open: Invalid argument
Db::open: Invalid argument:
{"what":"Db::open: Invalid argument"}
th_a bitcoin.cpp:338 import_bitcoin_wallet
error importing bitcoin wallet wallet.dat
{"wallet_dat":"wallet.dat","account_name":"webber"}
th_a wallet.cpp:3529 import_bitcoin_wallet
{}
th_a common_api_client.cpp:579 wallet_import_bitcoin
{"command":"wallet_import_bitcoin"}
th_a cli.cpp:538 execute_command
-
My new balance
default (unlocked) >>> wallet_account_balance
ACCOUNT BALANCE
------------------------------------------------------------
alt 110,000,000,899.9999 USD
489,796.00000 XTS
some balance for test,thanks.
XTSEcqxbtU2GaaC2AvnHcr4gtjpgzD6snMYc
seems like a wrong address
-
My new balance
default (unlocked) >>> wallet_account_balance
ACCOUNT BALANCE
------------------------------------------------------------
alt 110,000,000,899.9999 USD
489,796.00000 XTS
some balance for test,thanks.
XTSEcqxbtU2GaaC2AvnHcr4gtjpgzD6snMYc
seems like a wrong address
sorry,try again.
XTS5jzw5uNYjQfX4dxSMs7BhtQAfyCk9HqfE5EmcFvwnBsphwJ8vo
-
The download from the first post on this thread for the Mac client is not working. When trying to open for the first time getting: An error occurred while trying to start.
-
sent
2014-07-16T01:47:28 1814 alt webber 100.00000 XTS 0.10000 XTS 5bfd8767
2014-07-16T01:47:44 1816 alt webber 10,000.0000 USD 0.10000 XTS 745882be
-
Is market depth enough to avoid following case happen when margin call? the collateral to sell on market could be not enough to destroy the BitUSD they backed(endorsement).
When BitUSD/XTS price are dropping too quickly, the guarantee is that all the BitUSD related with the collateral need to be destroyed,
Dead approach:
so how about the call price, which BitUSD/XTS is relative higher than real price, should be executed when match ordering with higher priority? wait, this is not fair to the XTS buyer force....they need to pay more BitUSD that they will not agree...
Another approach:
How about the system sell all the left BitUSD that collateral can not back on the market? seems a dead approach too. So before the market orders which will cause price dropping quick get executed, the margin call should sell at the call price first, enough market depth is required to guarantee the margin call sell at that price. Otherwise, the market order matching need to be frozen to wait for more mature condition?
Margin Call not get executed in some cases, not sure it's a bug or due to market depth.
Maybe order matching need to enabled/disabled the same with margin call.
This is my balance :D
default (unlocked) >>> wallet_account_balance
ACCOUNT BALANCE
------------------------------------------------------------
alt 199,967,998.0003 USD
489,897.20000 XTS
This is the transactions history
2014-07-16T00:44:05 1434 alt ORDER-4nRtXFXW 100.00000 XTS 0.10000 XTS sell 100 XTS @ 1e+08 USD c1e0b1c4
2014-07-16T00:47:04 1452 alt ORDER-Nnwz8BnB 1.00000 XTS 0.10000 XTS short 1e+08 USD @ 1e+08 USD/XTS 5570da9d
2014-07-16T00:47:20 ERROR ORDER-4nRtXFXW UNKNOWN 0.99967 XTS 0.00000 XTS pay ask @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-4nRtXFXW alt 99,967,999.0003 USD 0.00000 XTS fill ask @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB UNKNOWN 1,240.0000 USD 999.99999 XTS pay bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB UNKNOWN 60.0000 USD 10.00000 XTS pay bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB UNKNOWN 12,245.0503 USD 9,955.32532 XTS pay bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB UNKNOWN 8,927.8001 USD 9,919.77780 XTS pay bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB UNKNOWN 70.0000 USD 10.00000 XTS pay bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB UNKNOWN 8.0000 USD 10.00000 XTS pay bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB UNKNOWN 7,000.0000 USD 9,999.99993 XTS pay bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB UNKNOWN 99,967,999.0003 USD 0.00000 XTS pay bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB UNKNOWN 4,990.0001 USD 9,980.00016 XTS pay bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB UNKNOWN 3.0000 USD 10.00000 XTS pay bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB UNKNOWN 0.1600 USD 1.00000 XTS pay bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB alt 0.00000 XTS 10.00000 XTS fill bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB alt 0.00000 XTS 10.00000 XTS fill bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB alt 0.99967 XTS 0.00000 XTS fill bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB alt 0.00000 XTS 10.00000 XTS fill bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB alt 0.00001 XTS 999.99999 XTS fill bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB alt 0.00012 XTS 9,955.32532 XTS fill bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB alt 0.00008 XTS 9,919.77780 XTS fill bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB alt 0.00000 XTS 10.00000 XTS fill bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB alt 0.00007 XTS 9,999.99993 XTS fill bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB alt 0.00004 XTS 9,980.00016 XTS fill bid @ 99999999. USD / XTS 00000000
2014-07-16T00:47:20 ERROR ORDER-Nnwz8BnB alt 0.00000 XTS 1.00000 XTS fill bid @ 99999999. USD / XTS 00000000
2014-07-16T00:48:53 1463 alt ORDER-CCFJNYAZ 1.00000 XTS 0.10000 XTS short 1e+08 USD @ 1e+08 USD/XTS 336c1e64
2014-07-16T00:49:10 ERROR ORDER-4nRtXFXW UNKNOWN 1.00000 XTS 0.00000 XTS pay ask @ 99999999. USD / XTS 00000000
2014-07-16T00:49:10 ERROR ORDER-4nRtXFXW alt 99,999,999.0000 USD 0.00000 XTS fill ask @ 99999999. USD / XTS 00000000
2014-07-16T00:49:10 ERROR ORDER-4nRtXFXW alt 99,999,999.0000 USD 0.00000 XTS fill ask @ 99999999. USD / XTS 00000000
2014-07-16T00:49:10 ERROR ORDER-CCFJNYAZ UNKNOWN 99,999,999.0000 USD 0.00000 XTS pay bid @ 99999999. USD / XTS 00000000
2014-07-16T00:49:10 ERROR ORDER-CCFJNYAZ alt 1.00000 XTS 0.00000 XTS fill bid @ 99999999. USD / XTS 00000000
-
ubuntu 14.02 cmake . make error
sudo apt-get update
sudo apt-get install cmake git libreadline-dev uuid-dev g++ libdb++-dev libdb-dev zip libssl-dev openssl build-essential python-dev autotools-dev libicu-dev build-essential libbz2-dev libboost-dev libboost-all-dev
git clone https://github.com/BitShares/bitshares_toolkit.git
cd bitshares_toolkit
git submodule init
git submodule update
cmake .
make
error:
[ 16%] Building C object libraries/fc/vendor/scrypt-jane/CMakeFiles/scrypt.dir/scrypt-jane.c.o
cc: error: unrecognized command line option ‘-no-integrated-as’
make[2]: *** [libraries/fc/vendor/scrypt-jane/CMakeFiles/scrypt.dir/scrypt-jane.c.o] Error 1
make[1]: *** [libraries/fc/vendor/scrypt-jane/CMakeFiles/scrypt.dir/all] Error 2
make: *** [all] Error 2
ubuntu@vm10-128-1-183:~/bitshares_toolkit$
-
stuck at block 1034 for 2 hours
tiger (unlocked) >>> info
{
"blockchain_head_block_num": 1034,
"blockchain_head_block_age": "2 hours old",
"blockchain_head_block_timestamp": "20140715T233700",
"blockchain_average_delegate_participation": 10.171198388721047,
"blockchain_delegate_pay_rate": 18,
"blockchain_blocks_left_in_round": 77,
"blockchain_confirmation_requirement": 1,
"blockchain_accumulated_fees": "21.89463 XTS",
"blockchain_share_supply": 199999997792460,
"blockchain_random_seed": "57ba59f7a2ee52c976d3e0385d409c327d1d52f6",
"blockchain_database_version": 114,
"blockchain_version": 107,
"network_num_connections": 2,
"network_num_connections_max": 200,
"network_protocol_version": 104,
"ntp_time": "20140716T020335",
"ntp_error": -0.014847000000000001,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "12 days in the future",
"wallet_unlocked_until_timestamp": "20140727T154955",
"wallet_block_production_enabled": false,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null,
"wallet_version": 100
}
tiger (unlocked) >>> info
tiger (unlocked) >>> about
{
"bitshares_toolkit_revision": "23cd03536932cfbc081de47586316586c2fb16c4",
"bitshares_toolkit_revision_age": "2 hours ago",
"fc_revision": "06fe9e0303b10f8cd6ef6a8da506495e5b113c39",
"fc_revision_age": "14 hours ago",
"compile_date": "compiled on Jul 15 2014 at 21:41:11"
}
-
stuck at block 1034 for 2 hours
tiger (unlocked) >>> info
{
"blockchain_head_block_num": 1034,
"blockchain_head_block_age": "2 hours old",
"blockchain_head_block_timestamp": "20140715T233700",
"blockchain_average_delegate_participation": 10.171198388721047,
"blockchain_delegate_pay_rate": 18,
"blockchain_blocks_left_in_round": 77,
"blockchain_confirmation_requirement": 1,
"blockchain_accumulated_fees": "21.89463 XTS",
"blockchain_share_supply": 199999997792460,
"blockchain_random_seed": "57ba59f7a2ee52c976d3e0385d409c327d1d52f6",
"blockchain_database_version": 114,
"blockchain_version": 107,
"network_num_connections": 2,
"network_num_connections_max": 200,
"network_protocol_version": 104,
"ntp_time": "20140716T020335",
"ntp_error": -0.014847000000000001,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "12 days in the future",
"wallet_unlocked_until_timestamp": "20140727T154955",
"wallet_block_production_enabled": false,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null,
"wallet_version": 100
}
tiger (unlocked) >>> info
tiger (unlocked) >>> about
{
"bitshares_toolkit_revision": "23cd03536932cfbc081de47586316586c2fb16c4",
"bitshares_toolkit_revision_age": "2 hours ago",
"fc_revision": "06fe9e0303b10f8cd6ef6a8da506495e5b113c39",
"fc_revision_age": "14 hours ago",
"compile_date": "compiled on Jul 15 2014 at 21:41:11"
}
I guess it's not because of fork
It's because you missed block 1035.
I have meet this situation several times.
-
update your source code first.
git pull
git submodule update
ubuntu 14.02 cmake . make error
sudo apt-get update
sudo apt-get install cmake git libreadline-dev uuid-dev g++ libdb++-dev libdb-dev zip libssl-dev openssl build-essential python-dev autotools-dev libicu-dev build-essential libbz2-dev libboost-dev libboost-all-dev
git clone https://github.com/BitShares/bitshares_toolkit.git
cd bitshares_toolkit
git submodule init
git submodule update
cmake .
make
error:
[ 16%] Building C object libraries/fc/vendor/scrypt-jane/CMakeFiles/scrypt.dir/scrypt-jane.c.o
cc: error: unrecognized command line option ‘-no-integrated-as’
make[2]: *** [libraries/fc/vendor/scrypt-jane/CMakeFiles/scrypt.dir/scrypt-jane.c.o] Error 1
make[1]: *** [libraries/fc/vendor/scrypt-jane/CMakeFiles/scrypt.dir/all] Error 2
make: *** [all] Error 2
ubuntu@vm10-128-1-183:~/bitshares_toolkit$
-
how did you work around with this problem?
stuck at block 1034 for 2 hours
tiger (unlocked) >>> info
{
"blockchain_head_block_num": 1034,
"blockchain_head_block_age": "2 hours old",
"blockchain_head_block_timestamp": "20140715T233700",
"blockchain_average_delegate_participation": 10.171198388721047,
"blockchain_delegate_pay_rate": 18,
"blockchain_blocks_left_in_round": 77,
"blockchain_confirmation_requirement": 1,
"blockchain_accumulated_fees": "21.89463 XTS",
"blockchain_share_supply": 199999997792460,
"blockchain_random_seed": "57ba59f7a2ee52c976d3e0385d409c327d1d52f6",
"blockchain_database_version": 114,
"blockchain_version": 107,
"network_num_connections": 2,
"network_num_connections_max": 200,
"network_protocol_version": 104,
"ntp_time": "20140716T020335",
"ntp_error": -0.014847000000000001,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "12 days in the future",
"wallet_unlocked_until_timestamp": "20140727T154955",
"wallet_block_production_enabled": false,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null,
"wallet_version": 100
}
tiger (unlocked) >>> info
tiger (unlocked) >>> about
{
"bitshares_toolkit_revision": "23cd03536932cfbc081de47586316586c2fb16c4",
"bitshares_toolkit_revision_age": "2 hours ago",
"fc_revision": "06fe9e0303b10f8cd6ef6a8da506495e5b113c39",
"fc_revision_age": "14 hours ago",
"compile_date": "compiled on Jul 15 2014 at 21:41:11"
}
I guess it's not because of fork
It's because you missed block 1035.
I have meet this situation several times.
-
how did you work around with this problem?
stuck at block 1034 for 2 hours
tiger (unlocked) >>> info
{
"blockchain_head_block_num": 1034,
"blockchain_head_block_age": "2 hours old",
"blockchain_head_block_timestamp": "20140715T233700",
"blockchain_average_delegate_participation": 10.171198388721047,
"blockchain_delegate_pay_rate": 18,
"blockchain_blocks_left_in_round": 77,
"blockchain_confirmation_requirement": 1,
"blockchain_accumulated_fees": "21.89463 XTS",
"blockchain_share_supply": 199999997792460,
"blockchain_random_seed": "57ba59f7a2ee52c976d3e0385d409c327d1d52f6",
"blockchain_database_version": 114,
"blockchain_version": 107,
"network_num_connections": 2,
"network_num_connections_max": 200,
"network_protocol_version": 104,
"ntp_time": "20140716T020335",
"ntp_error": -0.014847000000000001,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "12 days in the future",
"wallet_unlocked_until_timestamp": "20140727T154955",
"wallet_block_production_enabled": false,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null,
"wallet_version": 100
}
tiger (unlocked) >>> info
tiger (unlocked) >>> about
{
"bitshares_toolkit_revision": "23cd03536932cfbc081de47586316586c2fb16c4",
"bitshares_toolkit_revision_age": "2 hours ago",
"fc_revision": "06fe9e0303b10f8cd6ef6a8da506495e5b113c39",
"fc_revision_age": "14 hours ago",
"compile_date": "compiled on Jul 15 2014 at 21:41:11"
}
I guess it's not because of fork
It's because you missed block 1035.
I have meet this situation several times.
just waitting or restart.
来自我的 HUAWEI P7-L00 上的 Tapatalk
-
some funds for testing please, thanks :D
XTS5KdjNisUJ9bWD9UGowJy2Qa8feMES3XVLuVzQ5guFTxN6osKkb
-
some funds for testing please, thanks :D
XTS5KdjNisUJ9bWD9UGowJy2Qa8feMES3XVLuVzQ5guFTxN6osKkb
Sent.
-
some funds for testing please, thanks :D
XTS5KdjNisUJ9bWD9UGowJy2Qa8feMES3XVLuVzQ5guFTxN6osKkb
Sent.
received and voted, thanks again.
-
stuck at block 1034 .....
-
For continuity, you might switch the order of <quote_symbol> and <base_symbol> of the following 2 commands
blockchain_market_list_asks <quote_symbol> <base_symbol> [limit]
blockchain_market_list_bids <quote_symbol> <base_symbol> [limit]
The base always come first in a pair and the quote second
XTS/USD currently translates to blockchain_market_list_bids USD XTS (which is backwards)
and should be similar to the order for the command
wallet_market_submit_bid <from_account_name> <quantity> <quantity_symbol> <quote_price> <quote_symbol>
where <quantity> is your base
obviously this change would be purely cosmetic.
Unfortunately in trading XTS/USD is used (reads "XTS priced in USD"), and in math translates to USD/XTS (reads "USD per XTS"). So it's a little counter intuitive and often difficult when reading to figure out which is being referred to.
-
BitSharesXT quit unexpectedly.
I'm not able to load the client. It quits before opening.
-
stuck at block 2271
(wallet closed) >>> getinfo
{
"blockchain_head_block_num": 2271,
"blockchain_head_block_age": "89 minutes old",
"blockchain_head_block_timestamp": "20140716T030500",
"blockchain_average_delegate_participation": 15.855572998430141,
"blockchain_delegate_pay_rate": 58,
"blockchain_blocks_left_in_round": 52,
"blockchain_confirmation_requirement": 1,
"blockchain_share_supply": 199999992930142,
"blockchain_random_seed": "1b7bd524049868fe753fd7c89c551b85b14f5327",
"blockchain_database_version": 114,
"blockchain_version": 107,
"network_num_connections": 8,
"network_num_connections_max": 200,
"network_protocol_version": 104,
"ntp_time": "20140716T043352",
"ntp_error": -0.026741999999999998,
"wallet_open": false,
"wallet_unlocked": null,
"wallet_unlocked_until": null,
"wallet_unlocked_until_timestamp": null,
"wallet_block_production_enabled": null,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null,
"wallet_version": 100
}
-
stuck at block 2271
(wallet closed) >>> getinfo
{
"blockchain_head_block_num": 2271,
"blockchain_head_block_age": "89 minutes old",
"blockchain_head_block_timestamp": "20140716T030500",
"blockchain_average_delegate_participation": 15.855572998430141,
"blockchain_delegate_pay_rate": 58,
"blockchain_blocks_left_in_round": 52,
"blockchain_confirmation_requirement": 1,
"blockchain_share_supply": 199999992930142,
"blockchain_random_seed": "1b7bd524049868fe753fd7c89c551b85b14f5327",
"blockchain_database_version": 114,
"blockchain_version": 107,
"network_num_connections": 8,
"network_num_connections_max": 200,
"network_protocol_version": 104,
"ntp_time": "20140716T043352",
"ntp_error": -0.026741999999999998,
"wallet_open": false,
"wallet_unlocked": null,
"wallet_unlocked_until": null,
"wallet_unlocked_until_timestamp": null,
"wallet_block_production_enabled": null,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null,
"wallet_version": 100
}
me too
-
Wait for 10 hours, still stuck at block 888.
(wallet closed) >>> getinfo
{
"blockchain_head_block_num": 888,
"blockchain_head_block_age": "10 hours old",
"blockchain_head_block_timestamp": "20140715T191420",
"blockchain_average_delegate_participation": 2.8378758078111828,
"blockchain_delegate_pay_rate": 30136187,
"blockchain_blocks_left_in_round": 21,
"blockchain_confirmation_requirement": 1,
"blockchain_share_supply": 199996956227035,
"blockchain_random_seed": "5f626e10fdc76cf6e2e310a5b95b88f3d8b49ce7",
"blockchain_database_version": 114,
"blockchain_version": 107,
"network_num_connections": 4,
"network_num_connections_max": 200,
"network_protocol_version": 104,
"ntp_time": null,
"ntp_error": null,
"wallet_open": false,
"wallet_unlocked": null,
"wallet_unlocked_until": null,
"wallet_unlocked_until_timestamp": null,
"wallet_block_production_enabled": null,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null,
"wallet_version": 100
}
-
I believe the seed node(s) are not functioning properly.
I have read many reports of stuck at 1034 and 2071. I too cannot get a fresh client to sync properly with the network. My latest attempt was to force my client to connect to a single seed node. Here is the output:
2:~/bitshares_toolkit/programs/client$ ./bitshares_client --p2p-port 8902 --max-connections 1 --clear-peer-database --resync-blockchain --connect-to 107.170.30.182:8903 --disable-default-peers --disable-peer-advertising
Deleting old copy of the blockchain in "/home/XTSAdmin/.BitSharesXTS/chain"
Loading config "/home/XTSAdmin/.BitSharesXTS/config.json"
Initializing genesis state from built-in genesis file
Please be patient, this could take a few minutes.
Successfully re-indexed 0 blocks in 0 seconds.
Not starting RPC server, use --server to enable the RPC interface
Attempting to map P2P port 8902 with UPNP...
Erasing old peer database
Listening for P2P connections on port 8902
Attempting to connect to peer 107.170.30.182:8903
--- there are now 1 active connections to the p2p network
--- syncing with p2p network, 2271 blocks left to fetch
--- syncing with p2p network, our last block was created 7 hours ago
--- syncing with p2p network, our last block was created 6 hours ago
--- syncing with p2p network, our last block was created 5 hours ago
I am disconnecting peer 107.170.30.182:8903 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- syncing with p2p network, 1236 blocks left to fetch
(wallet closed) >>>
Note: the client first tells us there are 2271 blocks to fetch.
Note: the client is disconnected at block 1034, reconnects and looks for the 1236 blocks to fetch, but fails to do so.
(wallet closed) >>> about
{
"bitshares_toolkit_revision": "23cd03536932cfbc081de47586316586c2fb16c4",
"bitshares_toolkit_revision_age": "5 hours ago",
"fc_revision": "06fe9e0303b10f8cd6ef6a8da506495e5b113c39",
"fc_revision_age": "16 hours ago",
"compile_date": "compiled on Jul 16 2014 at 03:06:57"
}
(wallet closed) >>> config
{
"blockchain_id": "4b9f25c5e7204fd2af460d7a63fad3ce758e873ade2679c6ac14cfb62d4f05a7"
...
}
Does anyone have a peer node IP:PORT properly synced beyond block 2071 that I may connect to?
-
I think these are legitimate forks caused by broken market functionality... the seed nodes are all stuck as well.
I'm gonna lock this until we figure it out (tomorrow).
-
asset addition overflowed {"amount":5837168575529231657,"asset_id":0} + {"amount":5837448775871972696,"asset_id":0} = {"amount":-6772126722308347263,"asset_id":0}
{"a":{"amount":5837168575529231657,"asset_id":0},"b":{"amount":5837448775871972696,"asset_id":0},"c":{"amount":-6772126722308347263,"asset_id":0}}
th_a asset.cpp:29 operator+=
{"quote_id":22,"base_id":0}
th_a chain_database.cpp:294 execute
{}
This is the reason why the server is hung, every time the order matching attempts to execute we get this bug. This is triggered by alts transactions that are creating an ungodly amount of USD by manipulating the ratios in a thin market. I need to review his transaction history and put in guards that protect the block processing even if market operations fail.
-
It is also apparent that I have the quote/base system all turned around in my head because I was thinking in MATH terms.
When I see USD / XTS I *think* USD per XTS and not USD priced in XTS; however, upon reviewing bter they list BTSX/BTC as BTCX priced in BTC and BTSX per BTC. This is further complicated by the fact that i think "BASE" as the bottom half of a fraction and "QUOTE" as what you get when you divide 100 XTS * 5 USD / XTS => 500 USD.
I am going to do a quick review of all code and make sure that we have our terminology correct.
-
Definition of 'Base Currency'
The first currency quoted in a currency pair on forex. It is also typically considered the domestic currency or accounting currency. For accounting purposes, a firm may use the base currency to represent all profits and losses.
It is sometimes referred to as the "primary currency".
Investopedia explains 'Base Currency'
For example, if you were looking at the CAD/USD currency pair, the Canadian dollar would be the base currency and the U.S. dollar would be the quote currency. The price represents how much of the quote currency is needed for you to get one unit of the base currency.
-
I am disconnecting peer 84.238.140.192:48666 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 107.170.90.142:8901 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 128.199.180.112:8901 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 107.170.134.144:8901 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 107.170.30.182:8902 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 107.170.30.182:8901 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 107.170.30.182:8903 for reason: You offered us a block that we reject as invalid
--- in sync with p2p network
roy (unlocked) >>> info
{
"blockchain_head_block_num": 1034,
"blockchain_head_block_age": "15 hours old",
"blockchain_head_block_timestamp": "20140715T233700",
"blockchain_average_delegate_participation": 1.8787202380952381,
"blockchain_delegate_pay_rate": 18,
"blockchain_blocks_left_in_round": 77,
"blockchain_confirmation_requirement": 1,
"blockchain_accumulated_fees": "21.89463 XTS",
"blockchain_share_supply": 199999997792460,
"blockchain_random_seed": "57ba59f7a2ee52c976d3e0385d409c327d1d52f6",
"blockchain_database_version": 114,
"blockchain_version": 107,
"network_num_connections": 1,
"network_num_connections_max": 200,
"network_protocol_version": 104,
"ntp_time": "20140716T141405",
"ntp_error": 0.19447700000000001,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "28 hours in the future",
"wallet_unlocked_until_timestamp": "20140717T180032",
"wallet_block_production_enabled": false,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null,
-
Some new constraints coming for Dry Run 10:
All market-issued assets will have a minimum/maximum price ratio set to be wide enough to cover all eventualities. IE: BitUSD would be limited to .0005 USD per XTS and $500 USD per XTS which is simply assuming the market cap for XTS will be between $1 trillion USD and $1 million USD.
When a short position is blown out beyond the ability to cover all trading in that asset stops as this likely represents a large transient of BTS X falling in value by 50% in a very short period of time. To resume the market someone has to sell dollars at the specified price.
I am implementing the minimum market depth.
-
I have imported my btc wallet using wallet_import_armory and have rescaned blockchain,but no balance found.why?
import from multibit wallet failed.
default (unlocked) >>> wallet_import_multibit /home/alt/MultiBit/multibit.wallet xxxxxxxxx nobody2
Successfully imported 0 keys from: multibit.wallet
import my pts wallet failed :(
wallet.dat: file size not a multiple of the pagesize
wallet.dat: file size not a multiple of the pagesize
13 11DbException: Db::open: Invalid argument
Db::open: Invalid argument:
{"what":"Db::open: Invalid argument"}
th_a bitcoin.cpp:338 import_bitcoin_wallet
error importing bitcoin wallet wallet.dat
{"wallet_dat":"wallet.dat","account_name":"webber"}
th_a wallet.cpp:3529 import_bitcoin_wallet
{}
th_a common_api_client.cpp:579 wallet_import_bitcoin
{"command":"wallet_import_bitcoin"}
th_a cli.cpp:538 execute_command
Noted: https://github.com/BitShares/bitshares_toolkit/issues/90#issuecomment-49181420
Are other people experiencing similar problems?
-
Are other people experiencing similar problems?
I'm still unable to test it due to the client not loading... I get a "BitSharesXT quit unexpectedly." message every time.
-
I was able to import my PTS wallet but all of my registration transactions keep getting stuck as pending. Anybody else having that problem?
Sent from my iPhone using Tapatalk
-
Is there a single place to go to understand how to get setup to participate n dry runs?
I git cloned and built bitshares_toolkit on ubuntu - that went ok.
I am unsure what to do next - I can run ./bitshares_client and think I created a wallet but I am unsure what else to do.
-
Most of what you can do is in the github wiki.
https://github.com/BitShares/bitshares_toolkit/wiki
Otherwise type help and it will list all available commands.
Sent from my iPhone using Tapatalk
-
Is there a single place to go to understand how to get setup to participate n dry runs?
I git cloned and built bitshares_toolkit on ubuntu - that went ok.
I am unsure what to do next - I can run ./bitshares_client and think I created a wallet but I am unsure what else to do.
try:
wallet_create_account
then ask for funds with the key it returns
-
please send some testing funds to:
XTS6tKJcsagvFFco1519r5jWnRGmtcsYbRk2vs5V1e9LF85hZCkDL
-
Is there a single place to go to understand how to get setup to participate n dry runs?
I git cloned and built bitshares_toolkit on ubuntu - that went ok.
I am unsure what to do next - I can run ./bitshares_client and think I created a wallet but I am unsure what else to do.
This is my script every time i do a full recomplie.
Change paths accordingly.
#!/bin/sh
cd /Users/matias/Documents/Dev
rm -rf bitshares_toolkit
git clone https://github.com/BitShares/bitshares_toolkit.git
cd bitshares_toolkit
git submodule update --init
cd programs
git clone https://github.com/BitShares/qt_wallet.git
git clone https://github.com/BitShares/web_wallet.git
cd /Users/matias/Documents/Dev/bitshares_toolkit
# OPTIONAL: Im removing -stdlib=libc++ because my gcc doesnt like it
# find . -name CMakeLists.txt | xargs grep -l stdlib | xargs perl -i -p -e 's/\-stdlib=libc\+\+//g;'
cd programs/qt_wallet
export CMAKE_PREFIX_PATH=/Users/matias/Qt/5.2.0/clang_64
cmake -DINCLUDE_QT_WALLET=ON ../../../bitshares_toolkit
make buildweb
make
-
some funds please ?
XTS7ZkfAEvDhK6JbQXQ4P7tDbJMbdJB6KizTn6S9brAX4Qk7a23Pa
-
I am stuck at block 420...
liondani (locked) >>> info
{
"blockchain_head_block_num": 420,
"blockchain_head_block_age": "21 hours old",
"blockchain_head_block_timestamp": "20140715T215220",
"blockchain_average_delegate_participation": 1.3098171443392557,
"blockchain_delegate_pay_rate": 14,
"blockchain_blocks_left_in_round": 85,
"blockchain_confirmation_requirement": 1,
"blockchain_accumulated_fees": "16.99340 XTS",
"blockchain_share_supply": 199999998282583,
"blockchain_random_seed": "85bd85b72bdefa9cfe5d2bd09369c3ee993e0fa8",
"blockchain_database_version": 114,
"blockchain_version": 107,
"network_num_connections": 7,
"network_num_connections_max": 200,
"network_protocol_version": 104,
"ntp_time": "20140716T190010",
"ntp_error": -0.016788000000000001,
"wallet_open": true,
"wallet_unlocked": false,
"wallet_unlocked_until": null,
"wallet_unlocked_until_timestamp": null,
"wallet_block_production_enabled": null,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null,
"wallet_version": 100
}
--- there are now 6 active connections to the p2p network
--- there are now 7 active connections to the p2p network
-
Have we forked? Outernat is still running and producing blocks...
-
Dry run 9 is long dead, IDK why Dan re-opened the thread