|
zathras
|
 |
November 02, 2013, 09:31:54 PM |
|
Yeah, I think we should use the timestamp of the most recent bitcoin block, rather than the node's local clock.
I guess the full formula is actually (1-(0.5^y)) * 10% * total number of mastercoins bought at 1Exodus before the deadline
Could somebody confirm my vesting calculation is correct? Let's set the time to 2013-10-31 10:45:45 +0100 the output I get for the Exodus vesting is MSC 6103.51504811. Just a quick note on this one - I'm getting slightly different amounts, can you let me know what you're using for your fixed values? I'm using: * Seconds in a year: 31557600 * End of funding: 1377993600 * Total Reward Mastercoins: 56316.23576222 Using your example time (1383212745) I'm seeing 6099.57209817. |
|
|
|
|
superfluouso
|
|
November 02, 2013, 09:52:53 PM |
|
I saw that also but could not figure out how to sign the raw transaction. Would be nice if blockchain.info could also be used in addition to the console but I couldn't find a way to do it. |
|
|
|
|
|
puck2
|
|
November 03, 2013, 01:43:57 AM |
|
I am trying to create a sell order for a few fractions of Test Mastercoins. I find the following labels in the "Building new selling offer " page confusing and/or ambiguous:
* Amount
* Amount desired
Do these refer to total Test Mastercoins for sale and total amount desired?
These should read, perhaps, for clarity
* Amount for sale
* Total sale price
or
* Number of (Test) Mastercoins for sale
* Price per (Test) Mastercoin
|
|
|
|
|
|
Tachikoma
|
|
November 03, 2013, 09:57:19 AM |
|
I am trying to create a sell order for a few fractions of Test Mastercoins. I find the following labels in the "Building new selling offer " page confusing and/or ambiguous:
* Amount
* Amount desired
Do these refer to total Test Mastercoins for sale and total amount desired?
These should read, perhaps, for clarity
* Amount for sale
* Total sale price
or
* Number of (Test) Mastercoins for sale
* Price per (Test) Mastercoin
Which browser are you using? The placeholder text should offer more information. Amount says: "Total amount of MSC to sell" and the amount desired says "Total amount of Bitcoin". I figured most browser support placeholder text by now but if not I can probably add some hints to the fields to make it more clear. A little sidenote, I orginally build this just for developers so they had an easy way to compare implementation outputs. I did not really expect consumer to use it.
Yeah, I think we should use the timestamp of the most recent bitcoin block, rather than the node's local clock.
I guess the full formula is actually (1-(0.5^y)) * 10% * total number of mastercoins bought at 1Exodus before the deadline
Could somebody confirm my vesting calculation is correct? Let's set the time to 2013-10-31 10:45:45 +0100 the output I get for the Exodus vesting is MSC 6103.51504811. Just a quick note on this one - I'm getting slightly different amounts, can you let me know what you're using for your fixed values? I'm using: * Seconds in a year: 31557600 * End of funding: 1377993600 * Total Reward Mastercoins: 56316.23576222 Using your example time (1383212745) I'm seeing 6099.57209817. Thanks for checking. This is what I'm using now. time_difference = (tx_date - Mastercoin::END_TIME) / 60 / 60 / 24 / 365.25
exodus_vesting = (1-(0.5**time_difference)) * 0.1 * 563_162.23576222
tx_date = 1383212745 Mastercoin::END_TIME = 1377993600 time_difference = 5219145 Giving me a total of 6060.791436028762 (I initially used a rounded down value for the total amount of MSC, doh.) Congrats! Awesome that you managed to get it all to work. Now I have some more coins to buy for my own tests since buying from yourself is just silly. |
|
|
|
|
Bitoy
|
|
November 03, 2013, 12:27:13 PM |
|
Yeah, I think we should use the timestamp of the most recent bitcoin block, rather than the node's local clock.
I guess the full formula is actually (1-(0.5^y)) * 10% * total number of mastercoins bought at 1Exodus before the deadline
Could somebody confirm my vesting calculation is correct? Let's set the time to 2013-10-31 10:45:45 +0100 the output I get for the Exodus vesting is MSC 6103.51504811. Just a quick note on this one - I'm getting slightly different amounts, can you let me know what you're using for your fixed values? I'm using: * Seconds in a year: 31557600 * End of funding: 1377993600 * Total Reward Mastercoins: 56316.23576222 Using your example time (1383212745) I'm seeing 6099.57209817. I'm getting 6107.4878641923424 Seconds in a year: (60*60*24*365) 31536000 End of funding: 9/1/2013 Total Reward Mastercoins: 6107.4878641923424 My code is Dim Gencoins2 As Double = (1 - (0.5 ^ (DateDiff(DateInterval.Second, #9/1/2013#, #10/31/2013 10:45:45 AM#) / 31536000))) * 0.1 * 563162.36 |
|
|
|
|
|
Bitoy
|
|
November 03, 2013, 01:03:12 PM |
|
I would like to make a suggestion
Regarding the time limit, Currently the timelimit is in # blocks. My suggestion is to set it to days so that user will know when his offer will expire.
When making a payment,Seller sends payment in BTC to Buyer Address and a dust amount (ex. 0.00007) to the exodus address.
This will make parsing of payments easier.
|
|
|
|
|
|
Tachikoma
|
|
November 03, 2013, 01:39:29 PM |
|
I would like to make a suggestion
Regarding the time limit, Currently the timelimit is in # blocks. My suggestion is to set it to days so that user will know when his offer will expire.
Timelimit is not for the seller; it's for the person sending an Accept Offer message. When making a payment,Seller sends payment in BTC to Buyer Address and a dust amount (ex. 0.00007) to the exodus address.
This will make parsing of payments easier.
This is already in the spec. |
|
|
|
|
Bitoy
|
|
November 03, 2013, 02:12:11 PM |
|
I would like to make a suggestion
Regarding the time limit, Currently the timelimit is in # blocks. My suggestion is to set it to days so that user will know when his offer will expire.
Timelimit is not for the seller; it's for the person sending an Accept Offer message. When making a payment,Seller sends payment in BTC to Buyer Address and a dust amount (ex. 0.00007) to the exodus address.
This will make parsing of payments easier.
This is already in the spec. Yes the time limit is for the seller. What if the seller would like to place a time limit on his offer? Ie price is valid 7 days from now. Anyway it is just a thought. Thank you for your response. Is there already a transaction Id with a confirmed payment? |
|
|
|
|
|
|
prophetx
Legendary
 Offline
Activity: 1666
Merit: 1010
he who has the gold makes the rules
|
|
November 03, 2013, 04:22:28 PM |
|
Seems the fee was not set properly. I'm investigating.
Edit: I'm guessing you kept the fee set to 0.00001 ? This is lower then the required network fee. I've updated the code to force the fee to 0.0001 when it's set lower so other users don't make this mistake.
That is correct I did not change anything else other then the amount of test MSC to buy. So is this TX just going to hang out on the network with 0 confirms until the fees are lowered or something?? |
|
|
|
|
|
Bitoy
|
|
November 03, 2013, 04:23:06 PM |
|
The transaction "48d09647a8b233dbd2eecf16873bdcd99afa73ecbcd3c8b5ca39d79f0abfa1d5" is valid but there is no payment confirmation to the seller (13NRX88EZbS5q81x6XFrTECzrciPREo821). I was expecting a send to many transaction ie. 1. 13NRX88EZbS5q81x6XFrTECzrciPREo821 0.000101 Btc (Payment for 1 Test MSC coin) 2. Exodus Address .00006 btc
Seller
13NRX88EZbS5q81x6XFrTECzrciPREo821
Currency for Sale
#. Time, Amount
1. 11/2/2013 2:54:18 PM, 20
2. 11/2/2013 1:53:12 PM, 20 note: zero amount not valid
3. 10/28/2013 7:46:57 PM, 10
4. 10/28/2013 11:48:56 AM, 10
5. 10/25/2013 2:25:07 PM, 1
Accepted
Time,Amount
11/2/2013 8:17:50 PM, 20 (Accepted 4@#3 16@#2 )
11/2/2013 2:16:37 PM, 1 (Accepted 1@#3 )
10/28/2013 9:50:50 PM, 10 (Accepted 7@#4 and 3@#3 )
10/28/2013 4:15:23 PM, 2 (Accepted 2@#4)
10/28/2013 3:58:55 PM, 2 (Accepted 1@#5 and 1@#4)
|
|
|
|
|
|
Tachikoma
|
|
November 03, 2013, 04:27:32 PM |
|
I saw that also but could not figure out how to sign the raw transaction. Would be nice if blockchain.info could also be used in addition to the console but I couldn't find a way to do it. I need to go and do a bunch of updates to the tutorial, and set up a blockchain wallet but I think you may be able to use this https://blockchain.info/pushtxThat's only for sending a transaction. Not signing it. |
|
|
|
prophetx
Legendary
Offline
Activity: 1666
Merit: 1010
he who has the gold makes the rules
|
|
November 03, 2013, 05:08:18 PM |
|
I saw that also but could not figure out how to sign the raw transaction. Would be nice if blockchain.info could also be used in addition to the console but I couldn't find a way to do it. I need to go and do a bunch of updates to the tutorial, and set up a blockchain wallet but I think you may be able to use this https://blockchain.info/pushtxThat's only for sending a transaction. Not signing it. Sorry I had misread that. Could they use this to sign the tx in bitcoin-qt? the 3rd option is for a base58 private key, which can be exported from blockchain.info wallet advanced settings signrawtransaction <hex string> [{"txid":txid,"vout":n,"scriptPubKey":hex},...] [<privatekey1>,...] [sighash="ALL"] |
|
|
|
|
|
Tachikoma
|
|
November 03, 2013, 05:32:48 PM |
|
x-post from General thread. I've spend the last few days working on updating my Mastercoin-wallet (running on OS X and Unix-like, windows is possible as well) to supported distributed exchange messages and gave it it's own topic. For those who want to help test things this would be a great opportunity. I saw that also but could not figure out how to sign the raw transaction. Would be nice if blockchain.info could also be used in addition to the console but I couldn't find a way to do it. I need to go and do a bunch of updates to the tutorial, and set up a blockchain wallet but I think you may be able to use this https://blockchain.info/pushtxThat's only for sending a transaction. Not signing it. Sorry I had misread that. Could they use this to sign the tx in bitcoin-qt? the 3rd option is for a base58 private key, which can be exported from blockchain.info wallet advanced settings signrawtransaction <hex string> [{"txid":txid,"vout":n,"scriptPubKey":hex},...] [<privatekey1>,...] [sighash="ALL"] That could work, never done it myself though. |
|
|
|
|
Bitoy
|
|
November 03, 2013, 06:24:40 PM |
|
MyMastercoins.com http://mymastercoins.com/Default.aspxshow MSC and test MSC balance per address transactions per address (checked with mastercoin-explorer,masterchest,masterchain) calculates and validates MSC dev coins vb.net sql server |
|
|
|
|
|
TKeenan
|
|
November 03, 2013, 07:16:46 PM |
|
MyMastercoins.com http://mymastercoins.com/Default.aspxshow MSC and test MSC balance per address transactions per address (checked with mastercoin-explorer,masterchest,masterchain) calculates and validates MSC dev coins vb.net sql server Awesome!!! Way to go. Very cool work. |
|
|
|
|
|
Bitoy
|
|
November 04, 2013, 12:44:59 AM |
|
Thanks TKeenan. Btw I haven't turned on the transaction processing (data as of nov 4 only) because of debugging on distributed exchange. http://www.mymastercoins.com/Orders.aspx?CurrencyID=2MyMastercoins.com http://mymastercoins.com/Default.aspxshow MSC and test MSC balance per address transactions per address (checked with mastercoin-explorer,masterchest,masterchain) calculates and validates MSC dev coins vb.net sql server Awesome!!! Way to go. Very cool work. |
|
|
|
|
|
Bitoy
|
|
November 04, 2013, 03:49:36 AM |
|
Here is my implementation of the Distributed Trade processing. http://mymastercoins.com/Orders.aspx?CurrencyID=2Some notes CFSID = Currency for Sale ID. Available = No of Test MSC left for sale. If BTCDesired = 0. Set all Available to 0 (for that Currency). Buying If AmounttoPurchase > Available AmountPurchased = Available Comments are very welcomed =) |
|
|
|
|
|
Bitoy
|
|
November 04, 2013, 08:26:26 AM |
|
For the transaction above, is the btc payment( for the test btc) in the multi sig ? |
|
|
|
|
|
superfluouso
|
|
November 04, 2013, 08:35:41 AM |
|
Here is my implementation of the Distributed Trade processing. http://mymastercoins.com/Orders.aspx?CurrencyID=2Some notes CFSID = Currency for Sale ID. Available = No of Test MSC left for sale. If BTCDesired = 0. Set all Available to 0 (for that Currency). Buying If AmounttoPurchase > Available AmountPurchased = Available Comments are very welcomed =) This is pretty nice. I notice that completed transactions all show as "Waiting for payment" The seller ID's with links are a cool touch - do the existing ID's reference anything specific? |
|
|
|
|
|
