here is the tx hash

9d6c10c366036f3523b81437ebaa68f62cce89f9951e97022c129ae39008b475

so the .00025 are actually fees and are for sending out the transaction offer?

on the build page the only thing I changed was the "amount" from 10 to 4

I was trying to set up a buy to this offer

http://mastercoin-explorer.com/purchase_offers/new?address=13NRX88EZbS5q81x6XFrTECzrciPREo821&amount=10.0&currency_id=2&forced_fee=0.00001

Here is the latest blog update.  Also I have a link to a tutorial to test MSC-BTC transactions but I think I am having some issues, if someone want to check it out, perhaps I misread something.


Programming, Testing and More Testing of Mastercoin

News for week 44.2013.

There is a lot of excitement building up around Mastercoin and some important milestones have been set since last week’s blog.  But we have a lot of hard work cut out for us.  The developers are working hard on the next code contest and always looking for more folks to join the effort. Take some of your  spare time to check out the tutorial (see bottom) for conducting exchange transactions.

We now finally have a price graph of the MSC/BTC trades that have occurred, the Board has decided to engage a PR firm, we have a new addition to the Mastercoin repo’s on Github, there is a bounty open for building an MSC faucet, and a new proposal for enabling the limiting of spending of MSC on addressed that have been identified to have this feature enabled.  And if you are interested in the current economic distribution of Mastercoins here are the Top 50 MSC wallets....


http://blog.mastercoin.org/2013/11/02/programming-testing-and-more-testing/


Tutorial: Test MSC – BTC Distributed Exchange Transactions

http://blog.mastercoin.org/2013/11/02/tutorial-test-msc-btc-distributed-exchange-transactions/

then I went here, because the instructions say to decode the raw tx to do a check

http://mastercoin-explorer.com/raw/transactions/new

i got this page





but if i went here

https://coinb.in/decode-raw-transaction.html

I get

<code here>

ok another issue (I probably am doing something wrong but I cannot figure it out)

so i did sendrawtransaction

and got this




but a few blocks have passed now and none of those tx have any confirmation

also I have a question about the 0.00012 amount where is that going?

Isn't this already a part of the sendrawtransaction?  Or am I mistaken?  

Also in the "Amount" in the "Building new purchase offer"  what does this mean?

 I understood it to mean how many MSC I want to buy from the offer but perhaps I got it wrong because the sell offer wanted 0.0001 btc and my total out btc was 0.0025, and I put in 4 as the amount (assumed it would be 4 MSC).

thanks!

I think we might need a to-do list. Then I'll select something I can do from the list.
If it's sending test transactions maybe I can do that when there are clearer rules and instructions on how to make decentralized transactions.

Wow, that was fixed fast! And yes, everythings looks good now and behaves as expected.


Yes, you're right – I'll keep the main thread clean from bug reports.

You know I may have been operating on a bad assumption re the above; being as an unconfirmed transaction propagated throughout the network it would be added to the bottom of the (currently being mined) block template, thus transactions broadcast earlier would have a better chance of being first in the block.  It sounds like you're saying this is not the case? (Is there some kind of block reorganization etc?)  As I mentioned early on I'm quite new on this cryptocurrency 'scene' and have just been teaching myself by reading as much bitcoin literature (wikis, papers, forum posts etc) as I can get my hands on - so I'm certainly more than happy to be corrected if my interpretation is wrong!

Thanks for the additional info I'm just going to throw out an idea I've been playing with to see what you guys think (feel free to tear it apart if it's not a good idea!).  What about an additional optional message.  An 'acknowledge' if you will.   MSC/BTC exchange could function as per the discussion so far but have additional support for the user that created the sell to broadcast a message to 'acknowledge' a specific accept/Purchase Offer before it's confirmed in a block.  So:

Wallet broadcasts sell offer > Wallet sees a valid accept/Purchase offer in the block template > Wallet broadcasts an 'acknowledge' including the ID of the accept/Purchase offer it's agreeing to > Trade is considered locked in & waiting to be funded > Other parties see no point trying to accept this sell now and move on to the next

All of that can happen intra-block, as long as the user (specifically their wallet) participating in trading stays online.

Of course a wallet can also simply post a sell, go offline and have it bought by the first accept/Purchase in a block as per the current spec if their is no 'acknowledge' in that block sent by the seller.

I am concerned that perhaps doing anything at all with unconfirmed messages at a fundamental level regardless of how we structure it is a bad idea because we can't be 100% sure those unconfirmed transactions will be included in the next block.  Appreciate your thoughts

Of course.

Purchase offer:
http://mastercoin-explorer.com/transactions/ee77b1382633f8a5def69b444d319548b304ad93d8bb73505f7ff1c5755fac18
https://blockchain.info/tx/ee77b1382633f8a5def69b444d319548b304ad93d8bb73505f7ff1c5755fac18

Payment TX:
https://blockchain.info/tx/b9c6eb9e24c9c22ed7717c772d5bf5e4d50bef8e8e9e586113013dbaca33a79d

Maybe I was too slow?

Thanks for the explanation. The timeout is specified in number of blocks, is that correct? And does Mastercoin-explorer mark an purchase offer invalid if it is not paid within the required timeframe?

Tachikoma, maybe you can help me here. I created a purchase offer using Mastercoin-explorer:
http://mastercoin-explorer.com/transactions/264b5b2ae09af4c74ddf9d5948695e8e70d788c87668d2cff8a8dc2383d86406

This was in reaction to this selling offer:
http://mastercoin-explorer.com/transactions/9087a1b72536f3b2909943553ba6d4e320565eeea1e42379dd4337b532f09fd8

Creating the purchase offer went well so far (thanks for the great help section!) but I'm not entirely sure what to do now to execute the offer.
Status now is "Waiting on Payment". Should I just send payment to the seller's address now?

It doesn't necessarily have to be a hide, it can be a highlight/color change etc - just something to let the user know that there is already an accept visible on the blockchain for this sell and thus their accept is likely to be invalidated.  

You're correct in that there is nothing stopping the user (protocol wise) from sending their own accept and hoping it gets included earlier in the block than the accept already visible.

That's essentially the crux of the scalability problem - an exchange where the lowest ask sell can only be bought once every (on average) 10 minutes just doesn't scale. To avoid everyone trying to accept the same sell we need a way to consider that lowest sell 'pending acceptance' (or 'Purchase Offered') and have users look to the next lowest sell intra-block to make it scalable in my opinion.

Sure 1zAtHRASgdHvZDfHs6xJquMghga4eG7gy


No problems - the dev Mastercoins deliverable is likely to be another couple days work and should be quite straight forward to do Still working on adding exchange support to my wallet too - at the moment I'm playing with a bunch of variations on trading by unconfirmed transactions (which greatly increases the speed of the exchange but brings a whole new set of problems) - if I can get it right though our distributed Exchange will be as close to real-time as unconfirmed transaction propagation allows.

another question, which is more helpful for you:

a)  make a new thread on the project dev forum for people to post their test exchange transactions and offers, and issues they encounter

or

b) have people post issues to https://github.com/maran/mastercoin-explorer/issues/new