Topic: Masterchest Wallet Alpha Testing Thread - page 2. (Read 13391 times)

Hey all,

Please note 0024 is available for download, corrects an issue where accept offers are displayed as expired while payment is pending.

Thanks
Zathras

Hey,

I ran this through virustotal and wasn't able to see any issues - I actually recommend putting an exception in for any resident shield or network proxy, as if it proxies all the network requests (RPC) to bitcoind/qt it slows things down by >50%.

Thanks
Zathras

I have downloaded the "MasterchestWalletAlpha_Bin.zip" once yesterday, and 3 times today, from the "Windows Wallet" link at http://www.mastercoinwallets.org/. The files extract just fine using either 7-zip or WinZip. But when I try to run the "Masterchest_Wallet.exe" program, my Norton deletes it, and gives me a message that the file contained the "SONAR.Heuristic.120" trojan.

I am still successfully using the "MasterchestWalletAlpha_Bin.zip" that I downloaded mid-March. But I wanted to update it.

Any ideas anyone?



EDIT: Okay, the same thing happens when I download the download zip from github at https://github.com/zathras-crypto/masterchest-wallet.


EDIT: I haven't determined what the problem was, so I bypassed Symantec. We'll see. Mastercoin works just fine.
I ran the computer using a Linux OS off a USB Flash drive. It seems to have deleted the anomaly.

Build 0023 is available, please update.  This fixes a critical bug that flags payments for DEx purchases in the block immediately following expiry as valid (incorrectly).

If you would like further explanation please see below.

Binary via Github: Download

Thanks
Zathras

In a Master Protocol distributed exchange transaction the seller decides on a 'payment window' - a length of time (in blocks) for the buyer to make payment after his acceptance has been confirmed in the blockchain.  After this payment window, the acceptance expires.

If for example the seller has specified a time limit of 10 blocks, and the buyer accepts the sell offer in block 300000, the buyer then has until block 300010 to make payment.

A bug in the way Masterchest processes expiration allowed these acceptances to remain pending for the block immediately following expiry in certain circumstances, thus potentially allowing a DEx payment to incorrectly be seen as valid if it was exactly one block late.

This bug was discovered via our consensus systems noting that Masterchest had deviated from the reference this morning (Masterchain.info - unaffected).  Masterchest softwares (wallet and block explorer) incorrectly validated the purchase accepted in https://masterchest.info/lookuptx.aspx?txid=0d2f2f864a51938721a17963aa63925da4cd67ab1072d9ae339c3c0073b1308c. 

This bug has now been corrected and all Masterchest users are strongly encouraged to update their wallet software.

OK thanks - just to double check are you fully re-indexed and fully synced (bitcoin wise)?  It looks like it from the screenshot, but bitcoin will throw a 500 if it can't find the transaction or block we're searching for.

The next library build will have some additional information provided when bitcoin returns internal server errors.

For an immediate fix on another topic, J.R. pointed me to a bug with empty history - was fixed in my smart property experimental branch but still buggy in master, so have committed that as an urgent fix.  If you get an exception because it's a fresh wallet or you've never done any Mastercoin transactions, please pull the download again for the fix.

Yes I did. Only thing that happened is that "stucked" block has been reseted back to 292151 (and with that 2 block decreasing on every new run).. I would try to install MC on some of my mining rigs, but I don´t have a free space for blockchain there and running it on VPN doesn´t seems to be a good idea So by Mastercoin until next update, I´ll keep an eye on You.

Thanks for the info.  The next version will have additional debugging in failed RPC calls.  FYI the wallet is disposable - have you tried deleting the entire (Masterchest) wallet folder and pulling the download again?

As I wrote - every time I ran Mastercoin wallet there is same error with block number decreased by 2.

Hey guys, sorry haven't been around much - head down coding

g0re79 can you post the output of 'getinfo' from your bitcoin installation?

Thanks
Zathras

Hi g0re79,

does an error occure between those two blocks each time?

Yes, it hanged on block 292147. I wiped out blockchain and now redownloading it again (with -rebuild). I will update this in couple of hours.

EDIT: The only thing that changed is that its now stucked on block 292145 (bitcoin wallet synced)
EDIT: With every new run it hangs with block decreased by 2 (292143 - 292141 - 292139 - 292137...)

Strange. RPC seems to be working, otherwise the initial check on startup would have failed. And in nuffsaid420's case MSC transactions were recognized which indicates a RPC connection as well as valid transaction fetching and parsing. When and how often does the exception occure? Several hundred times or only from now and then? Are "simple send" transactions the only ones found?

g0re79: does it stop at this point for you? (DEBUG: Block Analysis for: 292147)

Same error for me - Exception thrown in bitcoin rpc call: The remote server returned an error Internal Server Error (500). Both Bitcoin Core and Mastercon updated to latest versions, turning off AV and FW did not help, neither did port changing..

Debug log:

Mastercoin wallet.cfg:

bitcoin.conf

Hello,

I am working on an outdated Windows XP, not sure if that has anything to do with it. I am getting errors with the Mastercoin wallet syncing. I keep getting errors. I can clear the errors and it seems to keep syncing. It seems to be the same one that instinctIS is getting.
Also I cannot change the DEBUG level from low. When I click on the LOW item it doesnt do anything.




And the full debug log:

MASTERCHEST WALLET v0.3c
[2014-03-30T08:34:26] DEBUG: Thread 'workthread' starting...
[2014-03-30T08:34:26] STATUS: Connection to bitcoin RPC established & sanity check OK.
[2014-03-30T08:34:26] STATUS: Connection to database established & sanity check OK.
[2014-03-30T08:34:28] STATUS: Database starting at block 292433
[2014-03-30T08:34:28] STATUS: Network is at block 293247
[2014-03-30T08:34:28] STATUS: 815 blocks to catch up
[2014-03-30T08:34:28] DEBUG: Block Analysis for: 292433
[2014-03-30T08:34:35] DEBUG: Block Analysis for: 292434
[2014-03-30T08:37:26] DEBUG: Block Analysis for: 292435
[2014-03-30T08:37:30] DEBUG: Block Analysis for: 292436
[2014-03-30T08:37:31] DEBUG: Block Analysis for: 292437
[2014-03-30T08:40:24] DEBUG: Block Analysis for: 292438
[2014-03-30T08:40:31] DEBUG: Block Analysis for: 292439
[2014-03-30T08:40:42] DEBUG: Block Analysis for: 292440
[2014-03-30T08:40:49] DEBUG: Block Analysis for: 292441
[2014-03-30T08:40:52] DEBUG: Block Analysis for: 292442
[2014-03-30T08:41:05] DEBUG: Block Analysis for: 292443
[2014-03-30T08:41:34] DEBUG: Block Analysis for: 292444
[2014-03-30T08:41:46] DEBUG: Block Analysis for: 292445
[2014-03-30T08:41:58] DEBUG: Block Analysis for: 292446
[2014-03-30T08:42:11] DEBUG: Block Analysis for: 292447
[2014-03-30T08:42:14] DEBUG: Block Analysis for: 292448
[2014-03-30T08:42:23] DEBUG: Block Analysis for: 292449
[2014-03-30T08:42:39] DEBUG: Block Analysis for: 292450
[2014-03-30T08:42:49] DEBUG: Block Analysis for: 292451
[2014-03-30T08:43:03] DEBUG: Block Analysis for: 292452
[2014-03-30T08:43:18] BLOCKSCAN: Found MSC transaction (simple send): b2b1cf6d81a5e6cb5a80426f5ac0c18f6b468a4b8b5c685254499d2d9afc895d
[2014-03-30T08:43:24] DEBUG: Block Analysis for: 292453
[2014-03-30T08:43:31] DEBUG: Block Analysis for: 292454
[2014-03-30T08:43:50] DEBUG: Block Analysis for: 292455
[2014-03-30T08:44:09] DEBUG: Block Analysis for: 292456
[2014-03-30T08:44:19] DEBUG: Block Analysis for: 292457
[2014-03-30T08:56:39] DEBUG: Block Analysis for: 292458
[2014-03-30T08:56:42] DEBUG: Block Analysis for: 292459
[2014-03-30T08:56:44] DEBUG: Block Analysis for: 292460
[2014-03-30T08:56:45] DEBUG: Block Analysis for: 292461
[2014-03-30T08:56:48] DEBUG: Block Analysis for: 292462
[2014-03-30T08:56:50] DEBUG: Block Analysis for: 292463
[2014-03-30T08:57:04] DEBUG: Block Analysis for: 292464
[2014-03-30T08:57:05] DEBUG: Block Analysis for: 292465
[2014-03-30T08:57:18] DEBUG: Block Analysis for: 292466
[2014-03-30T08:57:31] DEBUG: Block Analysis for: 292467
[2014-03-30T08:57:35] DEBUG: Block Analysis for: 292468
[2014-03-30T08:57:38] DEBUG: Block Analysis for: 292469
[2014-03-30T08:57:40] DEBUG: Block Analysis for: 292470
[2014-03-30T08:57:41] BLOCKSCAN: Found MSC transaction (simple send): 8b1a3158b56a38ddb023e2199760654e8e36cd65a1b302628248d865dde96378
[2014-03-30T08:57:42] DEBUG: Block Analysis for: 292471
[2014-03-30T08:57:49] BLOCKSCAN: Found MSC transaction (simple send): 82cf64378f6d15f1f5595961bf76a71fd2358a343e09cb451a81891e848ccb3b
[2014-03-30T08:57:49] BLOCKSCAN: Found MSC transaction (simple send): a4197db8c2c9a2d9b1f9985f6b7a5bd0595a82a2533672c6b276971df1df4c60
[2014-03-30T08:57:53] DEBUG: Block Analysis for: 292472
[2014-03-30T08:57:59] DEBUG: Block Analysis for: 292473
[2014-03-30T08:58:00] DEBUG: Block Analysis for: 292474
[2014-03-30T08:58:12] DEBUG: Block Analysis for: 292475
[2014-03-30T08:58:34] DEBUG: Block Analysis for: 292476
[2014-03-30T08:58:39] DEBUG: Block Analysis for: 292477
[2014-03-30T08:58:40] DEBUG: Block Analysis for: 292478
[2014-03-30T08:58:42] DEBUG: Block Analysis for: 292479
[2014-03-30T08:58:56] DEBUG: Block Analysis for: 292480
[2014-03-30T08:58:57] DEBUG: Block Analysis for: 292481
[2014-03-30T09:08:52] DEBUG: Block Analysis for: 292482
[2014-03-30T09:09:05] DEBUG: Block Analysis for: 292483
[2014-03-30T09:09:18] DEBUG: Block Analysis for: 292484
[2014-03-30T09:09:24] DEBUG: Block Analysis for: 292485
[2014-03-30T09:09:29] DEBUG: Block Analysis for: 292486
[2014-03-30T09:09:54] DEBUG: Block Analysis for: 292487
[2014-03-30T09:09:57] DEBUG: Block Analysis for: 292488
[2014-03-30T09:10:27] DEBUG: Block Analysis for: 292489

I notice you're running build 0019, try the latest (0021) it has retry capability in the RPC calls if your bitcoin installation doesn't respond on the first try.  It's doubtful this will solve your issue (as it's an internal server error not connection error) but always good to be running the latest build.

Also, could you post the output on the debug panel?  

What antivirus platform are you running?  I've seen a few interfere with comms to RPC.  Any firewalling on the interface for bitcoin RPC? Is bitcoin fairly vanilla - any customization?  There are still some things that Masterchest won't support, for example force using IPv6 instead of IPv4 in bitcoin-core may cause problems (if you don't know what that is then don't worry you won't be using it).

Once we see which step it's up to in the debug panel perhaps I can give you a build with extra debugging at that step to shep some light on what's going on.  We do have users on Win8 x64 (unsure if IE10) using the wallet successfully, so I'm not sure if it's something specific to your local environment.

Thanks
Zathras

Nice app, congrats. However there is this issue that goes with your app but also others on Win8 x64 IE10 , and that is the error 500 which is returned by the bitcoin wallet/server .
As have said, the same behavior goes with any other rpc apps that are connecting via Explorer , and on the other hand all that are connecting via php or made in SciTE are passing just right.

http://seo2url.com/to_delete/500.png

Any ideas on why this happen are welcome, since they will help you + me + others.

Hehe I wasted about an hour rotating that original sync icon a bunch of times to make an animation but the result was pretty poor - I think the new (properly generated) one looks much better - thanks for the ideas

I can change some of the defaults around, I think there is an issue for that already.

I could always grep the logs for the number of times that page is hit if needed sure.

Doing some sort of ticketing is great if a reasonable turnaround can be achieved - the difficulty with things today is people want their answers (now! now! now!) and even say 8 hours which used to be a good customer service turnaround is seen as slow (not that many in the crypto world deliver service even close to same day though!).

I think a decent FAQ needs to be added to that support landing page at minimum though.

EDIT: Perhaps that's expecting a bit much (8 hrs) - this is a very young industry after all - too much time in the day job negotiating SLAs with helpdesk

I love you for the animated sync icon...

And I see you adopted some of my suggestions. Thanks!

A general question: is there a reason that you show TMSC as default in the DEX? Also the balances in the addresses view have the order "BTC", "TMSC", "MSC" - I'd almost say: switch it! MSC is the most important one, BTC the least important one. I think.

About the support page: it would be very interesting to see how often it's opened. I read in the main thread that some said "all wallets are not very usable" (I disagree!), so this would be a tool to get some real numbers to falsify this fact.

Maybe this is a crazy idea, but what do you think about some kind of text box on the support landing page and after a user submitted his problem it is forwarded to a newly created mailing list (e.g. support at mastercoin.org). And volunteers could sign up to respond to those support requests? I think Dom is probably the right person who is able to evaluate such an idea?

Build 0021 is up.

Minor bugfixes and some UI improvements (thanks for all the suggestions!).

Thanks
Zathras

Legend DexX - added.

Thanks
Zathras

EDIT: Notes are extremely useful, thanks

On the 'ugly' scrollbars - couldn't agree more however since this is WinForms and not WPF repainting scrollbars is very scrappy/hacky I think - if you have any suggestions here I'm open to them absolutely.