|
201
|
Alternate cryptocurrencies / Marketplace (Altcoins) / Re: MasterCoin Buyer/Seller Thread
|
on: November 27, 2013, 09:05:47 AM
|
Hey, anyone able to help me pls?
trying to suss out how to send mastercoins. Got the mastercoin advisor working ok.
when it says step 1
send all funds in your wallet to the address that owns the mastercoins.
what does that mean, im sure im being dumb here, my wallet owns the coins
many thanks in advance
Your wallet has multiple addresses. In order to ensure the transaction will be send from the right address you need to send all the coins in your wallet to the same address. A Mastercoin transaction is only valid when it originates from the address holding the coins. This is just a way to ensure this. |
|
|
|
|
203
|
Alternate cryptocurrencies / Altcoin Discussion / Re: MasterCoin: New Protocol Layer Starting From “The Exodus Address”
|
on: November 27, 2013, 08:57:34 AM
|
For the marketplace ("Distributed E-Commerce") feature down the line, how does metadata like pictures and such descriptive info get stored?
Well, with Class B we're limited to a touch over 7KB per transaction so technically we could fit in a thumbnail or small image, but personally (just my view) I come firmly down on the side of keeping things as light as possible. At first thought I'd posit if we need images we store them externally (eg link to a http resource or secondary blockchain that's fit for purpose as a storage provider). From my suggested amendment EDIT: Sorry old habits, this is actually part of the spec now  The size of a Mastercoin packet in a compressed public key is thus 31 bytes (33 bytes minus the first and last bytes for the key identifier (02) and ECDSA manipulation byte). The Mastercoin packet reserves the first byte for the sequence number, providing a total of 30 bytes per packet for Mastercoin transaction data. The range of sequence numbers in a Class B transaction is 1 to 255, providing for a total 7,650 bytes maximum actual transaction data storage per Mastercoin Class B transaction.
I would like to go further then that and actually use a sidechain for data like URLs, names, pictures and whatever. I haven't properly formalised how that would work yet but I think it should be explored. Are you linking to the right anchor? |
|
|
|
|
206
|
Alternate cryptocurrencies / Marketplace (Altcoins) / Re: MasterCoin Buyer/Seller Thread
|
on: November 26, 2013, 07:58:40 PM
|
Hello, I am trying to buy a couple Mastercoin to do experiments, and the giveaway thread is super slow to do something. I have setup a proof that I wont scam you over a couple bitcoin (since I own a business that had more than 1000 bitcoins in volume in a few months) : http://btcoracle.com/mastercoin.phpContact me by PM. I am willing to pay whatever is the best sell offer in the order book + 10% for 1 mastercoin. I only need 1 mastercoin since I need to run tests. Already send you some testcoins. |
|
|
|
|
207
|
Bitcoin / Project Development / Re: Proposal for Standardizing the Distribution Rate of Dev MSC via the MSC Protocol
|
on: November 26, 2013, 09:31:08 AM
|
Poll Question:
Do think that the Dev MSC "Distribution Rate" should be fixed by the MSC protocol, in order to mirror the Dev MSC "Generation Rate"?
A. Yes, full speed ahead! Lets distribute 100% of Dev MSC generated each month, proportionately to each developer's contributions. That's what they are for! When the Distributed bounty system is launched it should be set at this same predictable Distribution Rate.
B. Yes, however things are early and we should be conservative. Lets distribute 50% of Dev MSC generated each month, proportionately to each developer's contributions. Save up the other 50% of Dev MSC for the hand over to the distributed bounty system when its launched in the future.
C. No, the Dev MSC are just part of the Mastercoin open source project development funding budget, along with the BTC from the Exodus address. And we should not tie the funding budget to any set rate, but should instead alter it daily, weekly, monthly based on project needs.
I think these three options to answering the question roughly capture the three proposals in this thread.
We can word smith these a bit, but I'd like to post this fairly soon and leave it up for a week or two and see where we are before the Christmas holiday kicks in and folks disappear for a while until mid January. I believe this is a very important decision.
Yeah. I think a poll would be a good idea. We have discussed the options enough and if more discussion is needed we can do it in the topic that includes the voting. |
|
|
|
|
209
|
Alternate cryptocurrencies / Marketplace (Altcoins) / Re: 300 BTC Coding Contest: Distributed Exchange (MasterCoin Developer Thread)
|
on: November 25, 2013, 04:03:48 PM
|
My implementation has 9.6028 (out of a total 10) sold. That's quite a big difference. How about you Zathras?
This is how it's currently parsed: You made that sell offer in block 270137 and cancelled it in 270278 (with tx 9468118ef2fa89c66733ce64038706850c2a81807cfd611e907e66fcf1b1edad). While the sell offer was open the following accept offers were sent: 4deebd27cb461289f833f64d1dce1e8a287bacd7bc70dcdffb49565d2fc8409a 1AMfFzbrhhizKDpqebYVYFGaTwdtSt5ux2 1EAuHj8Z6rTCHPxXfaGzzPsZevC2mg1XAj NULL acceptoffer 1384701670 270147 0 1 9702 NULL NULL NULL NULL 989899999
f67cc2760446b1458c4012bbe7d5f6129badcf4ac6896f82a4de7ec238103216 13tKKPNwDZGKhBK8gAHns7bXe2wtqhvzDb 1EAuHj8Z6rTCHPxXfaGzzPsZevC2mg1XAj NULL acceptoffer 1384699499 270144 0 2 9677 NULL NULL NULL NULL 100000
339abf9b176253e60d1569120c2d6bca214edd4e6d8a69ef4fcdaf4f4a12cec6 1AMfFzbrhhizKDpqebYVYFGaTwdtSt5ux2 1EAuHj8Z6rTCHPxXfaGzzPsZevC2mg1XAj NULL acceptoffer 1384708399 270160 0 1 9761 NULL NULL NULL NULL 989899999
87018464d016a067e5c8fedc07551c027bd011f43f6d3a02e9a1e252b551ba82 1F73UPD5xBKgTSRd8q6QhuncVmDnJAHxYV 1EAuHj8Z6rTCHPxXfaGzzPsZevC2mg1XAj NULL acceptoffer 1384699499 270144 0 2 9678 NULL NULL NULL NULL 10000000
4259faeb7c9d017beed911e30adcc82a0b0e6ee95d189a5531c1194663f58e99 1AMfFzbrhhizKDpqebYVYFGaTwdtSt5ux2 1EAuHj8Z6rTCHPxXfaGzzPsZevC2mg1XAj NULL acceptoffer 1384703123 270149 0 1 9735 NULL NULL NULL NULL 100000000
baba8972de24528bd56ec4ab3ce5fcead28eb45ac418eb87aace08d3da062a9b 1AMfFzbrhhizKDpqebYVYFGaTwdtSt5ux2 1EAuHj8Z6rTCHPxXfaGzzPsZevC2mg1XAj NULL acceptoffer 1384704190 270151 0 1 9745 NULL NULL NULL NULL 10100000
ac7593ff4fb4a9bc6b053fc12af10e4fc04db73e0fb467d1dbc2466c86c5936b 1F73UPD5xBKgTSRd8q6QhuncVmDnJAHxYV 1EAuHj8Z6rTCHPxXfaGzzPsZevC2mg1XAj NULL acceptoffer 1384708399 270160 0 1 9762 NULL NULL NULL NULL 50000000
077487c7e8eeab2fb6fefd193dc81ebb5b97c43f2242cee7a110b15c2f6a5f69 1AMfFzbrhhizKDpqebYVYFGaTwdtSt5ux2 1EAuHj8Z6rTCHPxXfaGzzPsZevC2mg1XAj NULL acceptoffer 1384701670 270147 0 2 9699 NULL NULL NULL NULL 989899999
b87e18e9d8eb6a3e70eb347e06ae5788bc0695b602b3c374cd133a963ac36f0d 1F73UPD5xBKgTSRd8q6QhuncVmDnJAHxYV 1EAuHj8Z6rTCHPxXfaGzzPsZevC2mg1XAj NULL acceptoffer 1384701670 270147 0 2 9700 NULL NULL NULL NULL 10000000
57e8880da36ca97456828900b66c4699617875c3826ce263ab9a2d7572fe0885 1AMfFzbrhhizKDpqebYVYFGaTwdtSt5ux2 1EAuHj8Z6rTCHPxXfaGzzPsZevC2mg1XAj NULL acceptoffer 1384721530 270188 0 1 9893 NULL NULL NULL NULL 100000000
644dd238f7090afe9c7280edc0b839c800bccbd8342b5e24fd21d4817520c4db 13tKKPNwDZGKhBK8gAHns7bXe2wtqhvzDb 1EAuHj8Z6rTCHPxXfaGzzPsZevC2mg1XAj NULL acceptoffer 1384723170 270190 0 1 9896 NULL NULL NULL NULL 10000000
025d9ed3f1dd620c84f7e5418fdf5635b7d9ca08350fac51a22b39389228fe01 1F73UPD5xBKgTSRd8q6QhuncVmDnJAHxYV 1EAuHj8Z6rTCHPxXfaGzzPsZevC2mg1XAj NULL acceptoffer 1384729954 270202 0 1 9926 NULL NULL NULL NULL 100000000
760722e7b9c3130e6bcfbbf439d4790d34e017020aeea438039c0bc20df77b2c 1CcJFxoEW5PUwesMVxGrq6kAPJ1TJsSVqq 1EAuHj8Z6rTCHPxXfaGzzPsZevC2mg1XAj NULL acceptoffer 1384733133 270205 0 2 9934 NULL NULL NULL NULL 50000000
7d4d70eac81d514e30ce8762434b91cd1d1650bf492779a3992bbd6f0c2043aa 1AMfFzbrhhizKDpqebYVYFGaTwdtSt5ux2 1EAuHj8Z6rTCHPxXfaGzzPsZevC2mg1XAj NULL acceptoffer 1384741070 270219 0 1 9957 NULL NULL NULL NULL 300000000
bf56a1ec213fdfcff0f26c8a9ab7eb7588ed5c0ddb202a225e12b35a0617c06e 1F73UPD5xBKgTSRd8q6QhuncVmDnJAHxYV 1EAuHj8Z6rTCHPxXfaGzzPsZevC2mg1XAj NULL acceptoffer 1384720301 270180 0 1 9876 NULL NULL NULL NULL 50000000
27937e5ba11231560c650a64dbe5b02c5406c04863e4074991e70762cccff806 16rAwebBXhJAM9ALf3fLFbaHKz24r2o3UN 1EAuHj8Z6rTCHPxXfaGzzPsZevC2mg1XAj NULL acceptoffer 1384734558 270208 0 1 9939 NULL NULL NULL NULL 50000000
fffbde998c925d159c13020bb4e9c6d71cf1553e75624aeb174488102b7b0c0c 1AMfFzbrhhizKDpqebYVYFGaTwdtSt5ux2 1EAuHj8Z6rTCHPxXfaGzzPsZevC2mg1XAj NULL acceptoffer 1384738049 270215 0 1 9942 NULL NULL NULL NULL 1000000
be2005200503273686a26604076bb03a67fdaad6755d9599ae539ffde663491e 16rAwebBXhJAM9ALf3fLFbaHKz24r2o3UN 1EAuHj8Z6rTCHPxXfaGzzPsZevC2mg1XAj NULL acceptoffer 1384758541 270258 0 1 10021 NULL NULL NULL NULL 50000000
The following are identified as funds sent for purchases against that sell: 3cdcd1b8148a979f3930b1998b3282dfad2f623c9e85c9d924d4634621263294 1F73UPD5xBKgTSRd8q6QhuncVmDnJAHxYV 0.02
cf77f174b4cf4aaf8ba560070e2af97685e5f946f8cbd4eab6cb371fa50bfd0d 1AMfFzbrhhizKDpqebYVYFGaTwdtSt5ux2 0.0202
66fc6ef07a48f703387eac59c78d8f3c8c1f465d72dd6f4452ebfff24cf3f745 1AMfFzbrhhizKDpqebYVYFGaTwdtSt5ux2 1.8798
My matching & locking code and resulting state processing is still not right though so as to which are valid; I'm working on some fixes Let me put it in the following format for easier comparison: Payment offers and their attached data and bitcoin payments. Hash: fffbde998c925d159c13020bb4e9c6d71cf1553e75624aeb174488102b7b0c0c, AmountBought: 0.00030000 MSC, PaymentTransactions: [7d4d70eac81d514e30ce8762434b91cd1d1650bf492779a3992bbd6f0c2043aa]
Hash: 57e8880da36ca97456828900b66c4699617875c3826ce263ab9a2d7572fe0885, AmountBought: 0.00030000 MSC, PaymentTransactions: [23f77b6caedd9d5ebbdc56f0d688bee0cf5fd41d19f2aba71f989237326da4b4]
Hash: 339abf9b176253e60d1569120c2d6bca214edd4e6d8a69ef4fcdaf4f4a12cec6, AmountBought: 9.39900000 MSC, PaymentTransactions: [66fc6ef07a48f703387eac59c78d8f3c8c1f465d72dd6f4452ebfff24cf3f745]
Hash: baba8972de24528bd56ec4ab3ce5fcead28eb45ac418eb87aace08d3da062a9b, AmountBought: 0.10130000 MSC, PaymentTransactions:[339abf9b176253e60d1569120c2d6bca214edd4e6d8a69ef4fcdaf4f4a12cec6, cf77f174b4cf4aaf8ba560070e2af97685e5f946f8cbd4eab6cb371fa50bfd0d]
Hash: 4259faeb7c9d017beed911e30adcc82a0b0e6ee95d189a5531c1194663f58e99, AmountBought: 0.10130000 MSC, PaymentTransactions:[cf77f174b4cf4aaf8ba560070e2af97685e5f946f8cbd4eab6cb371fa50bfd0d, baba8972de24528bd56ec4ab3ce5fcead28eb45ac418eb87aace08d3da062a9b]
|
|
|
|
|
212
|
Bitcoin / Electrum / Re: Electrum 1.9 released
|
on: November 25, 2013, 12:44:06 PM
|
There is a wrong config in the 1.9.5 for OSX that doesn't let you connect in the first run. It only affects Mountain Lion and older, it is being reviewed. I don't think this is specific to OS X. |
|
|
|
|
213
|
Alternate cryptocurrencies / Altcoin Discussion / Re: MasterCoin: New Protocol Layer Starting From “The Exodus Address”
|
on: November 25, 2013, 12:41:17 PM
|
Could someone point us to information on how to receive / send Mastercoins at this point in time?
We would like to obtain MSC but with ambigous info on what kind of Bitcoin addresses can even receive them, cannot risk losing the precious BTC for using a wrong type of BTC wallet.
- can Mastercoins be received to an Electrum address with its private key known to the owner?
Yes. As long as you have access to the private key it should work. - does Mastercoin receiving address need to be brand new ie. never seen in the network?
It doesn't need to be but it would be good practice. You can use the original Mastercoin advisor by J.R. to send coins. If you are on OS X or Linux you can try my wallet software. And soon you will be able to use Zathras's wallet on Windows. |
|
|
|
|
216
|
Alternate cryptocurrencies / Altcoin Discussion / Re: mastercoind proposal to speed development: Please read, vote, and comment
|
on: November 24, 2013, 04:49:58 PM
|
Forgive my ignorance but what does this differently compared to the current implementations? Are you not just creating Yet An Other Mastercoin implementation?
I'm actually not creating another Mastercoin implementation at all, as I'm utilizing grazcoin's mastercoin-tools package for the heavy-lifting (the integration will initially be a bit ghetto, but hopefully that will smooth out with time). As I wrote in the initial post, the goal is to lower the knowledge requirements for mastercoin application development by making a program similar to bitcoind, where future mastercoin developers can just query using a simple API, instead of having to figure out blockchain parsing. This is much like how bitcoin developers today don't need to know about the guts of bitcoin's workings to create a simple bitcoin-related app, they just need to know how to interact with bitcoind's JSON RPC API. Ok thanks for clarifying you are not actually creating a client but a RPC wrapper on top of a client. I still think J.R. should be the one who writes the reference client since he can make decisions on how the spec should be interpreted. No offence intended, but who gave you the right to decide your implementation should be the reference one. It's not so much how the clients handles, you can strap an RPC client on top of any implementation, but the decisions you make in the underlying layers. I think an RPC accessible client on top of any library is a excellent idea, I just think that the word reference implementation should be removed. |
|
|
|
|
220
|
Alternate cryptocurrencies / Marketplace (Altcoins) / Re: MasterCoin Buyer/Seller Thread
|
on: November 23, 2013, 02:37:41 PM
|
Do those Dev. coins (TMSC) have any real value?
I think you are confusing Test Mastercoin with Development Mastercoin. Test Mastercoin's have no value and are considered only valuable for testing purposes. Development Mastercoins are real Mastercoin which are being vested over time to be used for bounties etc. |
|
|
|
|
Show Posts
