Masterchest Wallet Alpha Testing Thread

[littleblue]

Yup!

http://www.mastercoinwallets.org

good! very good!

thanks for great job!

[1714675964]

1714675964

[editor499]

Waiting for official release.

me too

[littleblue]

#2 Reindexing Bitcoin.....OMG! MUCH  MUCH  MUCH  TIME!

[SquareRobin]

When starting Masterchest_Wallet.exe v0.1a in a protected directory (such as C:\Program Files\Masterchest) I get an error "Internal error: Cannot open the shared memory region." after the message "Startup: Testing database connection...".  Running the exe as an Administrator fixes this.  Installing Masterchest in a regular directory fixes this.

(Still Reindexing...)

[zathras]

When starting Masterchest_Wallet.exe v0.1a in a protected directory (such as C:\Program Files\Masterchest) I get an error "Internal error: Cannot open the shared memory region." after the message "Startup: Testing database connection...".  Running the exe as an Administrator fixes this.  Installing Masterchest in a regular directory fixes this.

(Still Reindexing...)

Hi,

Sounds like a permissions issue.  You'll see that error if a write lock can't be obtained on the database.  You likely require admin rights to write inside C:\Program Files (go there in explorer and right click > New Folder and you'll likely see an icon indicating escalation to admin is required).  Either simply give your user account write permissions on this folder or as you noted extract it to a writable directory.

I'll put this all into an installer which can drop the binary in program files and set the permissions accordingly, but for now extracting to anywhere writable (or where you don't need admin rights to write) is sufficient.

Thanks
Zathras

[SquareRobin]

I suggest anyone thinking of eventually installing Masterchest to first start the bitcoin-qt reindexing process (as described in the Masterchest pdf), since it takes a long time to run.

[littleblue]

I suggest anyone thinking of eventually installing Masterchest to first start the bitcoin-qt reindexing process (as described in the Masterchest pdf), since it takes a long time to run.

very loooooooong  time

[littleblue]

...
DEBUG: Block Analysis for: 250225
DEBUG: Block Analysis for: 250226
DEBUG: Block Analysis for: 250227
DEBUG: Block Analysis for: 250228
DEBUG: Block Analysis for: 250229
DEBUG: Block Analysis for: 250230
DEBUG: Block Analysis for: 250231
DEBUG: Block Analysis for: 250232
DEBUG: Block Analysis for: 250233
DEBUG: Block Analysis for: 250234
DEBUG: Block Analysis for: 250235
DEBUG: Block Analysis for: 250236
DEBUG: Block Analysis for: 250237
DEBUG: Block Analysis for: 250238
DEBUG: Block Analysis for: 250239
DEBUG: Block Analysis for: 250240
DEBUG: Block Analysis for: 250241
DEBUG: Block Analysis for: 250242
DEBUG: Block Analysis for: 250243
...
what is this?

[littleblue]

经实践，这个钱包用不成。

用了这个后，比特币的钱包每次打开都要重新建立索引！！

彻底崩溃了。

[softron]

Nice where can i get test mastercoin

[zathras]

...
DEBUG: Block Analysis for: 250225
DEBUG: Block Analysis for: 250226
DEBUG: Block Analysis for: 250227
DEBUG: Block Analysis for: 250228
DEBUG: Block Analysis for: 250229
DEBUG: Block Analysis for: 250230
DEBUG: Block Analysis for: 250231
DEBUG: Block Analysis for: 250232
DEBUG: Block Analysis for: 250233
DEBUG: Block Analysis for: 250234
DEBUG: Block Analysis for: 250235
DEBUG: Block Analysis for: 250236
DEBUG: Block Analysis for: 250237
DEBUG: Block Analysis for: 250238
DEBUG: Block Analysis for: 250239
DEBUG: Block Analysis for: 250240
DEBUG: Block Analysis for: 250241
DEBUG: Block Analysis for: 250242
DEBUG: Block Analysis for: 250243
...
what is this?

That's the wallet using your bitcoin installation to scan blocks looking for Master Protocol messages

[dexX7]

Nice where can i get test mastercoin

Try http://mastercoin-faucet.com!

[pplwjd]

I have been paying much attention to the project. I'm trying the wallet and it's syncronizing now. I like the style and great job,guys. Thank you Zathras. By the way, I think it's a little technical and complicated, the easier the better. Maybe you guys can find somebody who have little knowledge about IT and cryptocoins to use and test it and give you their advice. In addition, when  selling  MSCs why not list all the selling list and let  users referring to the price now in the market.

[jakecnn]

So, after about 3 days of sync'ing the wallet I tried to do a send of TMSC. The response was that there's not enough funds in my wallet to cover the tx fee.
I got about 0.0004 BTC in that address.. What is the tx fee set to? 0.001?

[zathras]

So, after about 3 days of sync'ing the wallet I tried to do a send of TMSC. The response was that there's not enough funds in my wallet to cover the tx fee.
I got about 0.0004 BTC in that address.. What is the tx fee set to? 0.001?

There are additional costs beyond just the miners fee (which is set at 0.00011) for funding the outputs for the transaction.  The library currently requires an unspent output >the total fee (~0.00035-0.00040 BTC) in order to send a transaction.

I actually wrote an appendix regarding the cost of Master Protocol messages, you can read it here if you're interested https://github.com/mastercoin-MSC/spec#appendix-e---understanding-the-cost-of-master-protocol-messages

Thanks
Zathras

[JakeThePanda]

No Mac wallet?

[jakecnn]

I successfully did a TMSC send with the wallet, but something is wrong - I had 0.418 TMSC before and sent 0.018.
The wallet shows the right balance afterwards(0.4), but masterchest and masterchain show 0.297 .
Is it because of open sellorders? I've never cancelled them I think.
Here is the log:

Code:

Recipient address is valid.
Raw transaction hex:
0100000001060c0a8e198b835bb18304fa8d19c08c52375f6bb63d25f998a61dc7c43d77fe0000000000ffffffff0450f00000000000001976a9142543163c517c4a59b2f4f6dd19a09d21c0093be288ac70170000000000001976a914946cb2e08075bcbaf157e47bcb67eb2b2339d24288ac70170000000000001976a9143c66ad4a06411af4e5a0d9f34e244969bee3adb088ace02e000000000000475121022b733322d7e855766a5bc4ad8f9707115980095d60d4ac138d507319702aa54321029B07F670D5FC1B4E93BE50BF51499F3C967BBD8BC133E1D012DDE615A2383B2652ae00000000
Raw transaction decode:
{"result":{"txid":"9d62eeb6588cb982bf4712ac35f55af69cb739f9e1ad270b25592d069b9206b9","version":1,"locktime":0,"vin":[{"txid":"fe773dc4c71da698f9253db66b5f37528cc0198dfa0483b15b838b198e0a0c06","vout":0,"scriptSig":{"asm":"","hex":""},"sequence":4294967295}],"vout":[{"value":0.00061520,"n":0,"scriptPubKey":{"asm":"OP_DUP OP_HASH160 2543163c517c4a59b2f4f6dd19a09d21c0093be2 OP_EQUALVERIFY OP_CHECKSIG","hex":"76a9142543163c517c4a59b2f4f6dd19a09d21c0093be288ac","reqSigs":1,"type":"pubkeyhash","addresses":["14Q2NNiF5YzDZCjo7vrBuHdbZcmHRJyW3j"]}},{"value":0.00006000,"n":1,"scriptPubKey":{"asm":"OP_DUP OP_HASH160 946cb2e08075bcbaf157e47bcb67eb2b2339d242 OP_EQUALVERIFY OP_CHECKSIG","hex":"76a914946cb2e08075bcbaf157e47bcb67eb2b2339d24288ac","reqSigs":1,"type":"pubkeyhash","addresses":["1EXoDusjGwvnjZUyKkxZ4UHEf77z6A5S4P"]}},{"value":0.00006000,"n":2,"scriptPubKey":{"asm":"OP_DUP OP_HASH160 3c66ad4a06411af4e5a0d9f34e244969bee3adb0 OP_EQUALVERIFY OP_CHECKSIG","hex":"76a9143c66ad4a06411af4e5a0d9f34e244969bee3adb088ac","reqSigs":1,"type":"pubkeyhash","addresses":["16WNYdM4whfD9gV3shX35rmHqbYzTJ6xEG"]}},{"value":0.00012000,"n":3,"scriptPubKey":{"asm":"1 022b733322d7e855766a5bc4ad8f9707115980095d60d4ac138d507319702aa543 029b07f670d5fc1b4e93be50bf51499f3c967bbd8bc133e1d012dde615a2383b26 2 OP_CHECKMULTISIG","hex":"5121022b733322d7e855766a5bc4ad8f9707115980095d60d4ac138d507319702aa54321029b07f670d5fc1b4e93be50bf51499f3c967bbd8bc133e1d012dde615a2383b2652ae","reqSigs":1,"type":"multisig","addresses":["14Q2NNiF5YzDZCjo7vrBuHdbZcmHRJyW3j","14inwuhpBTew2C8EenXW2L7xMDWx9Jti5h"]}}]},"error":null,"id":"1"}

Signing appears successful.
Transaction sent, ID: 9e52649ea61ad6d69c228c6b252d261fc6ae62fba25228c2c10a609f22969d90

[Tesca]

Tried to get it working but stumbled upon some hurdles:
I've got some error messages on start because it couldn't find my username/passwort etc. Found out that preceding spaces (in front of the line) in the bitcoin-qt config file were the source of the error.
Next i got some errors because i forgot to start bitcoint-qt which isn't that much of a problem but, the text in the messages seems strange: "Exception thrown getting block hash: der Wert darf nicht NULL sein. Parametername: value". Shouldn't there a real value instead of the word 'value' be written? Or is the punctuation out of order? Anyway it is kind of confusing.

I also noticed it take quite a while for it to synchronize, it would be helpfull i there would be something like a progressbar to get a sense of how long it takes.

[zathras]

I successfully did a TMSC send with the wallet, but something is wrong - I had 0.418 TMSC before and sent 0.018.
The wallet shows the right balance afterwards(0.4), but masterchest and masterchain show 0.297 .
Is it because of open sellorders? I've never cancelled them I think.
Here is the log:

Code:

Recipient address is valid.
Raw transaction hex:
0100000001060c0a8e198b835bb18304fa8d19c08c52375f6bb63d25f998a61dc7c43d77fe0000000000ffffffff0450f00000000000001976a9142543163c517c4a59b2f4f6dd19a09d21c0093be288ac70170000000000001976a914946cb2e08075bcbaf157e47bcb67eb2b2339d24288ac70170000000000001976a9143c66ad4a06411af4e5a0d9f34e244969bee3adb088ace02e000000000000475121022b733322d7e855766a5bc4ad8f9707115980095d60d4ac138d507319702aa54321029B07F670D5FC1B4E93BE50BF51499F3C967BBD8BC133E1D012DDE615A2383B2652ae00000000
Raw transaction decode:
{"result":{"txid":"9d62eeb6588cb982bf4712ac35f55af69cb739f9e1ad270b25592d069b9206b9","version":1,"locktime":0,"vin":[{"txid":"fe773dc4c71da698f9253db66b5f37528cc0198dfa0483b15b838b198e0a0c06","vout":0,"scriptSig":{"asm":"","hex":""},"sequence":4294967295}],"vout":[{"value":0.00061520,"n":0,"scriptPubKey":{"asm":"OP_DUP OP_HASH160 2543163c517c4a59b2f4f6dd19a09d21c0093be2 OP_EQUALVERIFY OP_CHECKSIG","hex":"76a9142543163c517c4a59b2f4f6dd19a09d21c0093be288ac","reqSigs":1,"type":"pubkeyhash","addresses":["14Q2NNiF5YzDZCjo7vrBuHdbZcmHRJyW3j"]}},{"value":0.00006000,"n":1,"scriptPubKey":{"asm":"OP_DUP OP_HASH160 946cb2e08075bcbaf157e47bcb67eb2b2339d242 OP_EQUALVERIFY OP_CHECKSIG","hex":"76a914946cb2e08075bcbaf157e47bcb67eb2b2339d24288ac","reqSigs":1,"type":"pubkeyhash","addresses":["1EXoDusjGwvnjZUyKkxZ4UHEf77z6A5S4P"]}},{"value":0.00006000,"n":2,"scriptPubKey":{"asm":"OP_DUP OP_HASH160 3c66ad4a06411af4e5a0d9f34e244969bee3adb0 OP_EQUALVERIFY OP_CHECKSIG","hex":"76a9143c66ad4a06411af4e5a0d9f34e244969bee3adb088ac","reqSigs":1,"type":"pubkeyhash","addresses":["16WNYdM4whfD9gV3shX35rmHqbYzTJ6xEG"]}},{"value":0.00012000,"n":3,"scriptPubKey":{"asm":"1 022b733322d7e855766a5bc4ad8f9707115980095d60d4ac138d507319702aa543 029b07f670d5fc1b4e93be50bf51499f3c967bbd8bc133e1d012dde615a2383b26 2 OP_CHECKMULTISIG","hex":"5121022b733322d7e855766a5bc4ad8f9707115980095d60d4ac138d507319702aa54321029b07f670d5fc1b4e93be50bf51499f3c967bbd8bc133e1d012dde615a2383b2652ae","reqSigs":1,"type":"multisig","addresses":["14Q2NNiF5YzDZCjo7vrBuHdbZcmHRJyW3j","14inwuhpBTew2C8EenXW2L7xMDWx9Jti5h"]}}]},"error":null,"id":"1"}

Signing appears successful.
Transaction sent, ID: 9e52649ea61ad6d69c228c6b252d261fc6ae62fba25228c2c10a609f22969d90

Thanks for testing!

Yep, that's just because the first version of the wallet didn't support DEx state processing (it parses the messages but doesn't process them).  The next alpha is going up today and that should display your sell offers automatically if they exist, so you can cancel them easy enough (right click sell > cancel).

Thanks!
Zathras

[zathras]

Tried to get it working but stumbled upon some hurdles:
I've got some error messages on start because it couldn't find my username/passwort etc. Found out that preceding spaces (in front of the line) in the bitcoin-qt config file were the source of the error.
Next i got some errors because i forgot to start bitcoint-qt which isn't that much of a problem but, the text in the messages seems strange: "Exception thrown getting block hash: der Wert darf nicht NULL sein. Parametername: value". Shouldn't there a real value instead of the word 'value' be written? Or is the punctuation out of order? Anyway it is kind of confusing.

I also noticed it take quite a while for it to synchronize, it would be helpfull i there would be something like a progressbar to get a sense of how long it takes.

Thanks for testing

I hope to be able to spend some time trapping errors a little better.  Part of the sanity checks involve checking for an expected return value to a particular blockhash to further sanity check we're talking with a bitcoin RPC server on a valid blockchain.  That error gets thrown when we don't get the expected value back (in this case because bitcoin wasn't running).  The code shouldn't actually get that far - it should terminate when there is no connection to bitcoin available, I'll double check the exit code there.

Thanks!
Zathras