300 BTC Coding Contest: Distributed Exchange (MasterCoin Developer Thread) - page 41.

Tachikoma

hero member

Activity: 938

Merit: 1000

Quote from: vokain on November 13, 2013, 05:01:20 PM

I voted for spoiling you guys a bit

Again, thank you devs for all that you're doing. I hold you guys in the highest esteem because it wasn't so much the monetary gain but the love of your work and craft and what that might mean for this world that inspired you.

Thanks, much appreciated. I have spend almost every free hour I have over the past weeks on Mastercoin because I believe in the protocol, what it can do, what it stands for and I can't wait to start using all the awesome features we are coding up

vokain

legendary

Activity: 1834

Merit: 1019

I voted for spoiling you guys a bit

Again, thank you devs for all that you're doing. I hold you guys in the highest esteem because it wasn't so much the monetary gain but the love of your work and craft and what that might mean for this world that inspired you.

Tachikoma

hero member

Activity: 938

Merit: 1000

I can rebase it back on your new spec if that helps?

dacoinminster

legendary

Activity: 1260

Merit: 1031

Rational Exuberance

Quote from: Tachikoma on November 13, 2013, 04:05:05 PM

hahah no problem. No reason to supply us with 100k for something that should take a day at most Wink

I know you are busy but could you make a decision on https://github.com/mastercoin-MSC/spec/pull/1 ? It doesn't matter either way but a decision needs to be made so we can move on. I'm kinda waiting on the outcome at the moment

Actually, we're taking this very seriously, because we don't want to be seen as going back on what we said. We may actually still do it at that higher price, which would be a HUGE payday for you guys, and would make us all very happy. Sorry for the uncertainty. This is still being hashed out and not everybody on the board has weighed in yet.

Regarding the pull request, sorry - I need to figure out how to turn on email notifications for github discussions. I'm sure it's trivial.

I've read through the discussion, and I'm going to merge this pull request once I figure out how to deal with the conflicts.

Tachikoma

hero member

Activity: 938

Merit: 1000

hahah no problem. No reason to supply us with 100k for something that should take a day at most Wink

I know you are busy but could you make a decision on https://github.com/mastercoin-MSC/spec/pull/1 ? It doesn't matter either way but a decision needs to be made so we can move on. I'm kinda waiting on the outcome at the moment

dacoinminster

legendary

Activity: 1260

Merit: 1031

Rational Exuberance

Sending dev MSC to you guys is a bit controversial at the previously quoted number. The board is currently discussing this, since at current prices the 1500 MSC we discussed sending earlier would be worth ~$100k, which is stupidly out of proportion with the amount of work involved with recognizing dev MSC.

I really need to get out of the habit of quoting prices in MSC. I'm guessing the actual send will be closer to the value it had when I first mentioned this. Something like $10k worth of MSC, if I recall correctly. This is currently under discussion.

I hope you guys weren't spending money in anticipation of a windfall!

This change is my fault (for quoting prices in MSC), and I apologize.

Bitoy

sr. member

Activity: 449

Merit: 250

Quote from: zathras on November 13, 2013, 05:34:57 AM

Quote from: Bitoy on November 13, 2013, 04:39:48 AM

To make coding shorter, I did peak and decode to get the data address then get the largest sequence as the receipient address.

Quick note, recipient address sequence number is not necessarily the largest - eg change output may be or if the data sequence number is 255 then the recipient will be smallest sequence (0)

Thanks Zarthas

If there are 3 address and the data sequence is 255 receipt must be sequence zero. I forgot about that

zathras

sr. member

Activity: 266

Merit: 250

Quote from: Bitoy on November 13, 2013, 04:39:48 AM

To make coding shorter, I did peak and decode to get the data address then get the largest sequence as the receipient address.

Quick note, recipient address sequence number is not necessarily the largest - eg change output may be or if the data sequence number is 255 then the recipient will be smallest sequence (0)

zbx

member

Activity: 64

Merit: 10

Quote from: Tachikoma on November 13, 2013, 04:32:58 AM

hmm weird. It's in the bounty topic.

His comment becomes visible to me when I click on the bounty topic.

Edit: Sorry, I was confused... I meant on Trello, which, I think, was updated after the Bitcointalk bounty topic.

Bitoy

sr. member

Activity: 449

Merit: 250

Quote from: zathras on November 13, 2013, 02:48:46 AM

Quote from: Bitoy on November 12, 2013, 06:56:22 PM

Quote from: zbx on November 12, 2013, 01:45:45 PM

Yeah, that's a transaction that I botched a couple of days ago. The sequence numbers are ascending instead of descending.

It is now valid because of the new specs in 1.2 "peek and decode". (Unless I read wrong

Sorry guys, I've been snowed the last week or so. I see JR has included my appendix in the latest revision of the spec Grin

which is great news - that means peek & decode is officially in so zbx's case in question would now be valid yep regardless of the bad sequence numbers (credit though; peek & decode was Tachikoma's idea, I just helped flesh it out and documented it

).

Note I'll need to cut a little code for this which I'll include in the coming Masterchest update. Somehow my current implementation isn't quite up to scratch Tongue

Code:

 
...
Else
   If isvalidtx = False Then  '### fall back to peek and decode
      'peek and decode routine here
   End If
End If
....

To make coding shorter, I did peak and decode to get the data address then get the largest sequence as the receipient address.

Tachikoma

hero member

Activity: 938

Merit: 1000

hmm weird. It's in the bounty topic.

zbx

member

Activity: 64

Merit: 10

Quote from: Tachikoma on November 13, 2013, 03:45:13 AM

I believe there is a bounty for a FIAT/MSC exchange. Your software idea sounds like it belongs there. Exchanges need to be fast in order to function so Go might be a good fit

dacoinminster said (on Trello) that a Fiat/MSC exchange wasn't going to be a project goal for now.

Tachikoma

hero member

Activity: 938

Merit: 1000

I believe there is a bounty for a FIAT/MSC exchange. Your software idea sounds like it belongs there. Exchanges need to be fast in order to function so Go might be a good fit

zbx

member

Activity: 64

Merit: 10

Hi. I'm thinking of making a submission to the coding contest. Would people here be interested in having an implementation of the Mastercoin protocol in Go, specifically one designed to be run as a server process, e.g. to be used in a trading engine, and handling the Bitcoin protocol over JSON-RPC? The priorities in design would be to make it fast, lean and robust. Does the project need software like that at this point (assuming that I can write it well... I'm very new to Go)? Does it need another independent implementation at all right now?

zathras

sr. member

Activity: 266

Merit: 250

Quote from: Bitoy on November 12, 2013, 06:56:22 PM

Quote from: zbx on November 12, 2013, 01:45:45 PM

Yeah, that's a transaction that I botched a couple of days ago. The sequence numbers are ascending instead of descending.

It is now valid because of the new specs in 1.2 "peek and decode". (Unless I read wrong

Sorry guys, I've been snowed the last week or so. I see JR has included my appendix in the latest revision of the spec Grin

which is great news - that means peek & decode is officially in so zbx's case in question would now be valid yep regardless of the bad sequence numbers (credit though; peek & decode was Tachikoma's idea, I just helped flesh it out and documented it

).

Note I'll need to cut a little code for this which I'll include in the coming Masterchest update. Somehow my current implementation isn't quite up to scratch Tongue

Code:

 
...
Else
   If isvalidtx = False Then  '### fall back to peek and decode
      'peek and decode routine here
   End If
End If
....

Bitoy

sr. member

Activity: 449

Merit: 250

Quote from: zbx on November 12, 2013, 01:45:45 PM

Yeah, that's a transaction that I botched a couple of days ago. The sequence numbers are ascending instead of descending.

It is now valid because of the new specs in 1.2 "peek and decode". (Unless I read wrong

grazcoin

sr. member

Activity: 284

Merit: 250

Quote from: Tachikoma on November 12, 2013, 11:55:43 AM

The problem is that I have no clue how I can find something that doesn't exist. I can't supply addresses that I don't know exist. I could query all currencies (there might be a lot in the future) and use data based on that but that would only bloat the verification-api without any real benefit.

I still vote to omit addresses that have no transactions for a certain currency_id.

If you don't find an address (which is a valid bitcoin address) in your database, simply report an empty address with all values 0.

Tachikoma

hero member

Activity: 938

Merit: 1000

Quote from: Bitoy on November 12, 2013, 12:28:27 PM

Hi Tachikoma

I've updated the parsing (all class A is now "peek and decode") and Master Explorer and MyMastercoins has the same balances (yehey!)

Except for one address
15a4XCuWmx2cCQVf8wZK7mqdvj5uwo1vby

MM=575 ME=570

It is TX
ecb77ee990de29745de949462e1f6e44584c310a0da12c9fbdf86dbe6ffabcfc

btw First line of your API there is a null address with balance 5.0
[{"address":null,"balance":"5.0"}

Woop! Awesome. As soon as I'm done with my current validation rewrite I will check out this transaction.

zbx

member

Activity: 64

Merit: 10

Yeah, that's a transaction that I botched a couple of days ago. The sequence numbers are ascending instead of descending.

Bitoy

sr. member

Activity: 449

Merit: 250

Hi Tachikoma

I've updated the parsing (all class A is now "peek and decode") and Master Explorer and MyMastercoins has the same balances (yehey!)

Except for one address
15a4XCuWmx2cCQVf8wZK7mqdvj5uwo1vby

MM=575 ME=570

It is TX
ecb77ee990de29745de949462e1f6e44584c310a0da12c9fbdf86dbe6ffabcfc

btw First line of your API there is a null address with balance 5.0
[{"address":null,"balance":"5.0"}

Topic: 300 BTC Coding Contest: Distributed Exchange (MasterCoin Developer Thread) - page 41. (Read 129207 times)