LTBCOINTEST appears to have broken, I issued 100,000 then 42 then 8, and it worked fine after issuing the 42, but issuing 8 seems to have reset the number of coins TOTAL to 8, as far as the system is concerned. When I try to pay a dividend, it uses "8" as the multiplier rather than 100,050. I still have more then 75k units between two addresses so clearly it is wrong, how can I correct this?
[font=Open Sans][color=white][/color][/font]
v 0.9.1 release (going on the server now)
ENHANCEMENTS:
* added tab name completion on the chat box (pretty neat)
* added up/down arrow history in the chatbox (pretty neat as well)
* using $.jqlog.debug() for most messages (so they will go away once we get on mainnet for everyone but developers)
* the system automatically bolds any chat lines with your handle mentioned in them
* added the ability to click on an open order and auto populate the buy info in the buy/sell page (idea from Adam Levine, thanks!)
* added versioning - version is shown on the options page
FIXES:
* fix for regression with last release that broke asset issuance (asset issuance should work again now)
* buy/sell: fixed the super annoying blank addresses in dropdown bug
* fixed: when overriding market rate it says "there is currently insufficent data"…it should only say that if there is indeed insufficient data
* fixed On buysell page: buy/sel quanntity left sometimes shows scientific notation
* fixed issue with order panes appearing after awhile while on the first step of buy/sell wizard (iif you went back to that from the second step)
* buy/sell: fixed text "flashing" issue when loading 2nd step
* buy/sell: fixed issue with duplicate open orders displaying
* fix for when transferring a locked asset, the locked setting not being correctly maintained (it would show up in the new address as a non-locked asset)
* fixed issue with BTC sends between two addresses in the same wallet not removing pending (cloud) icon from the destination address once confirmed
------
adam: let me know if the LTBCONTEST asset thing is still an issue
davidpbrown: I will look into your writeup tomorrow. thanks for that.
[quote author=xnova link=topic=188.msg1519#msg1519 date=1395476456]
v 0.9.1 release (going on the server now)
ENHANCEMENTS:
* added tab name completion on the chat box (pretty neat)
* added up/down arrow history in the chatbox (pretty neat as well)
* using $.jqlog.debug() for most messages (so they will go away once we get on mainnet for everyone but developers)
* the system automatically bolds any chat lines with your handle mentioned in them
* added the ability to click on an open order and auto populate the buy info in the buy/sell page (idea from Adam Levine, thanks!)
* added versioning - version is shown on the options page
FIXES:
* fix for regression with last release that broke asset issuance (asset issuance should work again now)
* buy/sell: fixed the super annoying blank addresses in dropdown bug
* fixed: when overriding market rate it says "there is currently insufficent data"…it should only say that if there is indeed insufficient data
* fixed On buysell page: buy/sel quanntity left sometimes shows scientific notation
* fixed issue with order panes appearing after awhile while on the first step of buy/sell wizard (iif you went back to that from the second step)
* buy/sell: fixed text "flashing" issue when loading 2nd step
* buy/sell: fixed issue with duplicate open orders displaying
* fix for when transferring a locked asset, the locked setting not being correctly maintained (it would show up in the new address as a non-locked asset)
* fixed issue with BTC sends between two addresses in the same wallet not removing pending (cloud) icon from the destination address once confirmed
------
adam: let me know if the LTBCONTEST asset thing is still an issue
davidpbrown: I will look into your writeup tomorrow. thanks for that.
[/quote]
Thanks for great work! Great wallet!
Bug report:
Send XCP error.failoverAPI: Call failed (failed over across all servers). Method: transmit; Last error: JSON-RPC Error:Type: Server error<br />Code: -32000<br />Message: {'message': 'TX rejected', 'code': -22}
I think the buying-an-asset price form is counterintuitive.
If you’re buying an asset, you would expect the unit price you input to be the unit price of that asset in the currency you’re paying with. In the screenshot below, I would expect to input the "LTBCOINTEST unit price in BTC", and have the field called that, rather than as it is. And shouldn’t the trade called LTBCOINTEST/BTC, to distinguish it from the opposite trade?
Also, the price field should be cleared when the user switches between "Unit Price" and "Sell Quantity", or else we’ll have people screwing up and placing orders that are not what they intended.
Just a heads up, the test server is having issues with insight. I’ve taken things down for an hour or so (hopefully that will be all), while I do a rebuild of the insight DB.
We will shortly have multiple servers up to better deal with these kinds of situations. We wanted to do initial testing on a single server to keep the complexity down, however.
Hi,
An asset i own doesn’t shown in the wallet.
I issued and sent an asset called: TESTASSETB and sent it to my address. I can see it throw my heavy wallet:GET_BALANCES RESULT: {'jsonrpc': '2.0', 'result': [{'amount': 149326511857, 'asset': 'XCP', 'address': 'mtiqNn9ZRBiibG7XrpkyHaCdix6P6w8yRb'}, {'amount': 1000,'asset': 'TESTASSETB', 'address': 'mtiqNn9ZRBiibG7XrpkyHaCdix6P6w8yRb'}], 'id':0}
But it no showing in the web lite wallet:
[quote author=bitcoiner link=topic=188.msg1536#msg1536 date=1395573607]
Hi,
An asset i own doesn’t shown in the wallet.
I issued and sent an asset called: TESTASSETB and sent it to my address. I can see it throw my heavy wallet:GET_BALANCES RESULT: {'jsonrpc': '2.0', 'result': [{'amount': 149326511857, 'asset': 'XCP', 'address': 'mtiqNn9ZRBiibG7XrpkyHaCdix6P6w8yRb'}, {'amount': 1000,'asset': 'TESTASSETB', 'address': 'mtiqNn9ZRBiibG7XrpkyHaCdix6P6w8yRb'}], 'id':0}
But it no showing in the web lite wallet:
[/quote]
It should has no problem. Try it again. I have maken the process several times,no problem.
[quote author=xcptime link=topic=188.msg1537#msg1537 date=1395574715]
It should has no problem. Try it again. I have maken the process several times,no problem.
[/quote]
Try what again? I did it yesturday and I can see that the asset is belong to this address but not showing in the lite wallet.
This bug was extremely frustrating to me. Only this morning did I figure out what was preventing me from creating/logging into a wallet.
Summary: you cannot register by triple-click copying/pasting the 12 word phrase using:
OS X Safari
OS X Chrome
1) Visit testnet.counterwallet.co using OS X safari or chrome
2) Click 'create new wallet’
3) Triple-click the suggested 12 word phrase to highlight it and copy it to your clipboard
4) Paste it into the “Log Into Your Wallet” field
Result:When you paste in the 12 words, the •••• bullets show, but the “Open Wallet” button remains deactivated:
Presumably some whitespace character is being copied/pasted and is messing up the validation script.
Workaround: Don’t triple-click. Instead carefully highlight the words instead of the entire input field. Or use firefox, which doesn’t have this bug.
Error on payment of dividend:
I tried to pay a dividend on a newly created asset. The confirmation message also prompted an error message:
Confirmation message was
[quote]You have paid a dividend of 1 LOVE per outstanding unit to holders of asset TESTQFIL. This action will take some time to complete, and will appear as a Pending Action until confirmed on the network. Until that time, the wallet will not reflect the change. Please be patient.[/quote]
Error was
[quote]failoverAPI: Call failed (failed over across all servers). Method: transmit; Last error: JSON-RPC Error:
Type: Server error
Code: -32000
Message: {‘code’: -22, ‘message’: ‘TX rejected’}[/quote]
The dividend was paid as expected; so, not clear what effect that error had.
Priming and Unconfirmed Balances:
The auto-priming of accounts could be made obvious; perhaps a toggle an * next to [Primed:] for whether auto-prime is enabled on an account. I don’t understand what Priming means for the coins, perhaps it’s colouring x11 satoshi but it would be useful to describe that in the Prime popup boxes.
So, slight confusion followed when I sent some BTC to my empty third account, the balance appeared quite quickly. I noticed there was then a [Primed:1] highlight I think was red, I clicked that out of curiosity and there was some message about please wait for BTC to confirm and that Primed number became then 0 in yellow. So, it wasn’t obvious to me whether I’d prompted that change and then spent a trivial BTC for the privilege; or if that was auto-prime and my click had no effect. The ~‘please wait for confirmation of BTC’ message, perhaps could suggest ‘account will auto-prime for 11 assets when BTC are confirmed’.
It seems not clear whether the declared BTC balance and I guess others, is available for spending or some is still unconfirmed. Perhaps unconfirmed assets could be declared separately to the Bal: as Pending:?
[Primed:0] doesn’t suggest how much BTC is needed for Priming but appears to require some. Also, the create additional Prime popup and [Wallet:options] don’t declare how much is needed either.
One [Pending Action] notification seems stuck for [Pending priming for My Address #3 for 10 more unspent outputs] remains, where account has 11 now and other similar notifications before and after that have aged.
Asset names and aging:
It is perhaps unfortunate that asset names are limited to A-Z - no numbers even. I guess random letter combinations might become more common and using the description important then… though what of those owners who change the description, is there a log of changes accessible to users? If I change my description from Gold to Silver, who will notice? Who will be first to grab the names for Gold; Silver; etc on launch. If naming is so limited, perhaps it might be easier to provide an auto-generated random name?
If all coins of one asset belong to a single address, could the owner perhaps opt to destroy that asset?
Asset Call time perhaps could do with having the timezone explicit - even if that’s just local-time rather than UTC.
Lastly, having a grand total of assets in all addresses might be useful.
I’m not sure if this is a bug or a feature request, but I’d like to be able to “un-override” market rate and trade options. When I click either of these override links:
I like the extra features I get, but I wish I could “un-override” the market rate configuration options. That or maybe a “start over / reset” button that re-initializes all the trade options.
[font=verdana]I have a question:[/font]
[font=Arial][color=rgb(32, 36, 39)][size=medium]Is there a Counterwallet that does not run on Testnet but on Mainnet?[/size][/color][/font]
[quote author=wksantiago link=topic=188.msg1570#msg1570 date=1395683449]
[font=verdana]I have a question:[/font]
[font=arial][color=rgb(32, 36, 39)][size=medium]Is there a Counterwallet that does not run on Testnet but on Mainnet?[/size][/color][/font]
[/quote]
That is what this testing is for. 
…once we are satisfied that the bugs have been worked out enough, it’s going on mainnet.
Counterwallet v0.9.2 going up on the server momentarily:
ENHANCEMENTS:
[font=verdana]* added the ASSET LEADERBOARD functionality, which shows the top 100 counterparty assets (that have actual trade data)[/font][font=verdana]* asset market info is now pre-compiled (i.e. calculated and stored) every 10 minutes, due to the addition of the asset leaderboard* added notification pane messages for bets and broadcasts
* servers store chat history now in database, and added get_chat_history() call.
* because of the above, chat history persists between server restarts (so you still get the newest line even if the counterwalletd service needs to be restarted)
* fixed up and enhanced the Asset Portfolio page
FIXES:
* modified address creation button to be more clear (people were missing the create watch address option as it was a combo button)
* buy/sell: order book display changed to percentages based adaptive display instead of absolute fee based (i.e. works as it should now
* chat handle completion on tab is now case insensitive
* choosing your handle when starting a chat for the first time now will tell you if the handle is in use or not
* fixes for nginx “crash” situation, fix correctly closing unused sockets in counterwalletd in one or two places
* address sweeping was borked. fixed.[/font]
[font=verdana]* chat was totally clearing history after 200 lines when it should have just been removing the first 5 lines
[/font][font=Verdana]* 0.9.2.1: bug fix for counterwalletd not properly rebuilding its app_config collection if the cwd DB version went up[/font][font=verdana]
Been heads down working on these fixes and changes, I will try to catch up with the posts here tomorrow. [size=1em]Will also be deploying on multiple servers tomorrow most likely…so if there are usage issues, that’s probably why. [/size][/font]
I was told to post here. I can’t transact with my wallet due to it reporting that it’s not primed. When I click the “primed” notifier on the wallet, it says i have no btc to prime it with. I was told in the chat that it’s a bug.
My address is mtHCR73yfEmUSXacJ7T1wUCgX7rr3RtgSh.
[quote author=binaryphile link=topic=188.msg1591#msg1591 date=1395764745]
I was told to post here. I can’t transact with my wallet due to it reporting that it’s not primed. When I click the “primed” notifier on the wallet, it says i have no btc to prime it with. I was told in the chat that it’s a bug.
My address is mtHCR73yfEmUSXacJ7T1wUCgX7rr3RtgSh.
[/quote]
You need to deposit test BTC into the wallet first to do anything (including prime the address). From there, you can burn it for test XCP, send it, etc.
The testnet btc faucet is dry.
[quote author=binaryphile link=topic=188.msg1602#msg1602 date=1395845445]
The testnet btc faucet is dry.
[/quote]
We do not operate the testnet faucet.
I guess I can’t use the wallet then.