Masterchest Wallet Alpha Testing Thread

[g0re79]

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:

Code:

MASTERCHEST WALLET v0.3c
[2014-04-01T22:45:40] DEBUG: Thread 'workthread' starting...
[2014-04-01T22:45:40] STATUS: Connection to bitcoin RPC established & sanity check OK.
[2014-04-01T22:45:40] STATUS: Connection to database established & sanity check OK.
[2014-04-01T22:45:42] STATUS: Database starting at block 292147
[2014-04-01T22:45:42] STATUS: Network is at block 293631
[2014-04-01T22:45:42] STATUS: 1485 blocks to catch up
[2014-04-01T22:45:42] DEBUG: Block Analysis for: 292147

Mastercoin wallet.cfg:

Code:

bitcoinrpcserv=127.0.0.1
bitcoinrpcport=8332
bitcoinrpcuser=myrpcuser
bitcoinrpcpass=myrpcpass

bitcoin.conf

Code:

txindex=1
server=1
rpcport=8332
rpcconnect=127.0.0.1
rpcallowip=127.0.0.1
rpcuser=myrpcuser
rpcpassword=myrpcpass

[1714673084]

1714673084

[dexX7]

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)

[g0re79]

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)

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...)

[dexX7]

Hi g0re79,

does an error occure between those two blocks each time?

[zathras]

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)

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...)

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

[g0re79]

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)

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...)

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

Code:

"version" : 90000,
"protocolversion" : 70002,
"walletversion" : 60000,
"balance" : 0.99323521,
"blocks" : 293901,
"timeoffset" : 0,
"connections" : 8,
"proxy" : "",
"difficulty" : 5006860589.20540050,
"testnet" : false,
"keypoololdest" : 1368442926,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"errors" : ""

does an error occure between those two blocks each time?

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

[zathras]

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)

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...)

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

Code:

"version" : 90000,
"protocolversion" : 70002,
"walletversion" : 60000,
"balance" : 0.99323521,
"blocks" : 293901,
"timeoffset" : 0,
"connections" : 8,
"proxy" : "",
"difficulty" : 5006860589.20540050,
"testnet" : false,
"keypoololdest" : 1368442926,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"errors" : ""

does an error occure between those two blocks each time?

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

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?

[g0re79]

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?

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.

[zathras]

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.

[zathras]

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.

[BADecker]

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.

[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.

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

[zathras]

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

[mishax1]

Here's my experience with 0.3C build 0023..

After sending the payment I get this on the history tab:



and the sell offer appears on the exchange tab again:



and after the payment gets confirmed the history tab info changes to this:



and the sell order finally disappears from the exchange tab.

That is kinda confusing for a 1st time uesr.. 

edit:
just saw this

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

[zathras]

Here's my experience with 0.3C build 0023..

After sending the payment I get this on the history tab:



and the sell offer appears on the exchange tab again:



and after the payment gets confirmed the history tab info changes to this:



and the sell order finally disappears from the exchange tab.

That is kinda confusing for a 1st time uesr..  

edit:
just saw this

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

Hi, yep sorry about that, the previous fix on expiry was too aggressive and caused pending buys already paid to appear expired (self correcting one the payment was confirmed), that behaviour should now be fixed.

Thanks
Zathras

[zathras]

Hey all,

0025 is available for download, corrects an issue where action byte is not enforced for case 0x02 where no previous sell exists (should be invalidated) and applies formula fix for rounding on purchase amounts.

Please update.

Thanks
Zathras

[crazy_rabbit]

I'm a little confused at the moment, I'm on the exchange tab, and there are sell orders for "0.00" as well as Unit prices from .0799999998 till 3, yet the charge shows a giant green bar up to .4?

[mishax1]

I'm a little confused at the moment, I'm on the exchange tab, and there are sell orders for "0.00" as well as Unit prices from .0799999998 till 3, yet the charge shows a giant green bar up to .4?

Someone bought at 0.37 skipping all other orders - https://masterchest.info/lookuptx.aspx?TXID=46886cdcff50dab670d84788d0fe7fccea21f0a90ab91a5bd910b27c001b5272

And the graphs just jumped up to 0.37.

Hope this will change..

[crazy_rabbit]

I'm a little confused at the moment, I'm on the exchange tab, and there are sell orders for "0.00" as well as Unit prices from .0799999998 till 3, yet the charge shows a giant green bar up to .4?

Someone bought at 0.37 skipping all other orders - https://masterchest.info/lookuptx.aspx?TXID=46886cdcff50dab670d84788d0fe7fccea21f0a90ab91a5bd910b27c001b5272

And the graphs just jumped up to 0.37.

Hope this will change..

I see- I bet that person thought he would purchase everything UP to 0.37, not only at 0.37 skipping the orders. Indeed I hope there is a way to fix that, although perhaps there isn't.

[dexX7]

I see- I bet that person thought he would purchase everything UP to 0.37, not only at 0.37 skipping the orders. Indeed I hope there is a way to fix that, although perhaps there isn't.

I doubt this because you need to accept and pay for specific orders and there is no "buy now at x" mechanism in Masterchest. But it's actually a nice idea.. mask the atomic transactions in the background and simply "buy".

The charting is tricky due to the same reasons. If one wants, he could create a sell order at 0.5 BTC/MSC for 0.0001 MSC and raise the bars after buying this one. I have no idea how the charts could be constructed in a way which is more transparent. Any input regarding this topic is highly appreciated!