Bitcoin Forum
November 21, 2026, 11:11:32 PM *
News: Latest Bitcoin Core release: 32.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 [103] 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 ... 163 »
  Print  
Author Topic: MasterCoin: New Protocol Layer Starting From “The Exodus Address”  (Read 448581 times)
This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic.
Ola
Sr. Member
****
Offline

Activity: 311
Merit: 250


View Profile
November 21, 2013, 02:04:24 PM
 #2041

I have 2 things on my mind...and I think these points need to be address quickly to speed up development and foster outside development.


1) I think its high time that 2 developers, or at least Tachikoma is hired or contracted full time for at least a period of 2 years... this is a minimal relative cost of doing business considering the potential fast turn around of the initiative, due to having someone work on the project full time. At this point Tachikoma who blazes the trail, mostly leading developments and improvement shouldn't be scrounging around working to pay bills. His focus should be on developing and testing so we can have something dependable in no time:  Success in anything depends on FOCUS, and right now our main devs have jobs on the side trying to pay bills. We should take a page from the bitcoin foundation and emulate the hiring of Gavin Adresen.

"Concentrate all your thoughts upon the work at hand. The sun's rays do not burn until brought to a focus."


2) Is there a plan to develop something higher level to interface programmatically with mastercoin? an api maybe, although I couldn't fathom how it will work to do :

simple sends
confirmations
betting etc..

I also thinking of designing mastercoin into my system but do not know where to start, especially if this will be addressed later.

If you are in favor of one or two of these points please echo this post.

Nxter,Bitcoiner,Ether highlevel developer working to improve the world.
klee
Legendary
*
Offline

Activity: 1498
Merit: 1002



View Profile
November 21, 2013, 02:25:49 PM
 #2042

I have 2 things on my mind...and I think these points need to be address quickly to speed up development and foster outside development.


1) I think its high time that 2 developers, or at least Tachikoma is hired or contracted full time for at least a period of 2 years... this is a minimal relative cost of doing business considering the potential fast turn around of the initiative, due to having someone work on the project full time. At this point Tachikoma who blazes the trail, mostly leading developments and improvement shouldn't be scrounging around working to pay bills. His focus should be on developing and testing so we can have something dependable in no time:  Success in anything depends on FOCUS, and right now our main devs have jobs on the side trying to pay bills. We should take a page from the bitcoin foundation and emulate the hiring of Gavin Adresen.

"Concentrate all your thoughts upon the work at hand. The sun's rays do not burn until brought to a focus."


2) Is there a plan to develop something higher level to interface programmatically with mastercoin? an api maybe, although I couldn't fathom how it will work to do :

simple sends
confirmations
betting etc..

I also thinking of designing mastercoin into my system but do not know where to start, especially if this will be addressed later.

If you are in favor of one or two of these points please echo this post.
Echoing!
zbx
Member
**
Offline

Activity: 64
Merit: 10


View Profile
November 21, 2013, 02:33:24 PM
 #2043

I have 2 things on my mind...and I think these points need to be address quickly to speed up development and foster outside development.


1) I think its high time that 2 developers, or at least Tachikoma is hired or contracted full time for at least a period of 2 years... this is a minimal relative cost of doing business considering the potential fast turn around of the initiative, due to having someone work on the project full time. At this point Tachikoma who blazes the trail, mostly leading developments and improvement shouldn't be scrounging around working to pay bills. His focus should be on developing and testing so we can have something dependable in no time:  Success in anything depends on FOCUS, and right now our main devs have jobs on the side trying to pay bills. We should take a page from the bitcoin foundation and emulate the hiring of Gavin Adresen.

"Concentrate all your thoughts upon the work at hand. The sun's rays do not burn until brought to a focus."


2) Is there a plan to develop something higher level to interface programmatically with mastercoin? an api maybe, although I couldn't fathom how it will work to do :

simple sends
confirmations
betting etc..

I also thinking of designing mastercoin into my system but do not know where to start, especially if this will be addressed later.

If you are in favor of one or two of these points please echo this post.
Echoing!
+1
Ola
Sr. Member
****
Offline

Activity: 311
Merit: 250


View Profile
November 21, 2013, 02:37:27 PM
 #2044

ripper234 will this be a no brainer if at least 10 people echo this? I hope to everything we believe in Tachikoma does not think otherwise.

Nxter,Bitcoiner,Ether highlevel developer working to improve the world.
abuelau
Hero Member
*****
Offline

Activity: 750
Merit: 500


www.coinschedule.com


View Profile
November 21, 2013, 03:07:22 PM
 #2045

I have 2 things on my mind...and I think these points need to be address quickly to speed up development and foster outside development.


1) I think its high time that 2 developers, or at least Tachikoma is hired or contracted full time for at least a period of 2 years... this is a minimal relative cost of doing business considering the potential fast turn around of the initiative, due to having someone work on the project full time. At this point Tachikoma who blazes the trail, mostly leading developments and improvement shouldn't be scrounging around working to pay bills. His focus should be on developing and testing so we can have something dependable in no time:  Success in anything depends on FOCUS, and right now our main devs have jobs on the side trying to pay bills. We should take a page from the bitcoin foundation and emulate the hiring of Gavin Adresen.

"Concentrate all your thoughts upon the work at hand. The sun's rays do not burn until brought to a focus."


2) Is there a plan to develop something higher level to interface programmatically with mastercoin? an api maybe, although I couldn't fathom how it will work to do :

simple sends
confirmations
betting etc..

I also thinking of designing mastercoin into my system but do not know where to start, especially if this will be addressed later.

If you are in favor of one or two of these points please echo this post.
Echoing!
+1

+2

Know what's happening in cryptoworld: www.coinschedule.com
littleblue
Sr. Member
****
Offline

Activity: 285
Merit: 250


View Profile
November 21, 2013, 03:29:17 PM
 #2046

I have 2 things on my mind...and I think these points need to be address quickly to speed up development and foster outside development.


1) I think its high time that 2 developers, or at least Tachikoma is hired or contracted full time for at least a period of 2 years... this is a minimal relative cost of doing business considering the potential fast turn around of the initiative, due to having someone work on the project full time. At this point Tachikoma who blazes the trail, mostly leading developments and improvement shouldn't be scrounging around working to pay bills. His focus should be on developing and testing so we can have something dependable in no time:  Success in anything depends on FOCUS, and right now our main devs have jobs on the side trying to pay bills. We should take a page from the bitcoin foundation and emulate the hiring of Gavin Adresen.

"Concentrate all your thoughts upon the work at hand. The sun's rays do not burn until brought to a focus."


2) Is there a plan to develop something higher level to interface programmatically with mastercoin? an api maybe, although I couldn't fathom how it will work to do :

simple sends
confirmations
betting etc..

I also thinking of designing mastercoin into my system but do not know where to start, especially if this will be addressed later.

If you are in favor of one or two of these points please echo this post.
Echoing!
+1

+2
+3
genjix
Legendary
*
Offline

Activity: 1232
Merit: 1097


View Profile
November 21, 2013, 04:01:33 PM
 #2047

+4

I've worked with Animazing before on Electrum and he's a solid developer you want in your community.
romerun
Legendary
*
Offline

Activity: 1078
Merit: 1002


Bitcoin is new, makes sense to hodl.


View Profile
November 21, 2013, 04:59:28 PM
 #2048

where's the link to see the live webinar, i'm confused
JohnnyBTCSeed
Hero Member
*****
Offline

Activity: 881
Merit: 1000



View Profile
November 21, 2013, 05:00:57 PM
 #2049

+ 5
littleblue
Sr. Member
****
Offline

Activity: 285
Merit: 250


View Profile
November 21, 2013, 05:23:59 PM
 #2050

where's the link to see the live webinar, i'm confused
me too
Ola
Sr. Member
****
Offline

Activity: 311
Merit: 250


View Profile
November 21, 2013, 05:28:38 PM
 #2051

where's the link to see the live webinar, i'm confused
me too


here it is:   https://plus.google.com/u/0/events/cosfuleudovf9bbitllefb93874


and keep echoing if you believe this should be done: 
I have 2 things on my mind...and I think these points need to be address quickly to speed up development and foster outside development.


1) I think its high time that 2 developers, or at least Tachikoma is hired or contracted full time for at least a period of 2 years... this is a minimal relative cost of doing business considering the potential fast turn around of the initiative, due to having someone work on the project full time. At this point Tachikoma who blazes the trail, mostly leading developments and improvement shouldn't be scrounging around working to pay bills. His focus should be on developing and testing so we can have something dependable in no time:  Success in anything depends on FOCUS, and right now our main devs have jobs on the side trying to pay bills. We should take a page from the bitcoin foundation and emulate the hiring of Gavin Adresen.

"Concentrate all your thoughts upon the work at hand. The sun's rays do not burn until brought to a focus."


2) Is there a plan to develop something higher level to interface programmatically with mastercoin? an api maybe, although I couldn't fathom how it will work to do :

simple sends
confirmations
betting etc..

I also thinking of designing mastercoin into my system but do not know where to start, especially if this will be addressed later.

If you are in favor of one or two of these points please echo this post.
Echoing!

Nxter,Bitcoiner,Ether highlevel developer working to improve the world.
littleblue
Sr. Member
****
Offline

Activity: 285
Merit: 250


View Profile
November 21, 2013, 05:31:34 PM
Last edit: November 21, 2013, 05:41:47 PM by littleblue
 #2052

where's the link to see the live webinar, i'm confused
me too
i know:google+
rbdrbd
Sr. Member
****
Offline

Activity: 462
Merit: 250



View Profile
November 21, 2013, 05:45:20 PM
Last edit: November 21, 2013, 06:00:28 PM by rbdrbd
 #2053

I have 2 things on my mind...and I think these points need to be address quickly to speed up development and foster outside development.


1) I think its high time that 2 developers, or at least Tachikoma is hired or contracted full time for at least a period of 2 years... this is a minimal relative cost of doing business considering the potential fast turn around of the initiative, due to having someone work on the project full time. At this point Tachikoma who blazes the trail, mostly leading developments and improvement shouldn't be scrounging around working to pay bills. His focus should be on developing and testing so we can have something dependable in no time:  Success in anything depends on FOCUS, and right now our main devs have jobs on the side trying to pay bills. We should take a page from the bitcoin foundation and emulate the hiring of Gavin Adresen.

"Concentrate all your thoughts upon the work at hand. The sun's rays do not burn until brought to a focus."


2) Is there a plan to develop something higher level to interface programmatically with mastercoin? an api maybe, although I couldn't fathom how it will work to do :

simple sends
confirmations
betting etc..

I also thinking of designing mastercoin into my system but do not know where to start, especially if this will be addressed later.

If you are in favor of one or two of these points please echo this post.
Echoing!
+1

This is what I raised up in my post as well.

This project *absolutely* needs multiple full time developers. Mastercoin foundation needs to make that happen ASAP. At my business, I can hire 3 developers to work full time for me (as well as around 13 other assorted full time engineers) and we pull in less each year than the mastercoin foundation has sitting around. Not sure why this can't be done with Mastercoin as well. Run it like a business. Priority number 1.

Once we have a solid mastercoin API library that can work across multiple languages (optimally do basic parsing in C, then use swig, etc to take out to Python, Perl, Ruby, etc) then the skill bar level is DRASTICALLY lowered. At that point, you can get generic webdevs and generaic devs that have a good mid-level understanding of bitcoin/mastercoin to do the work. The ruby, etc library is good, but we need it available for a wide variety of langs, without a bunch of implementations that all have their own ideas how the blocks should be parsed (we get the problems we are seeing today). This should be priority number 2. Pay for a *reference* C implementation and bindings to other languages can be easily made. Any new standard that comes out in the business world (e.g. audio codecs, etc), they implement a standard reference implementation, and vendors follow suit with their implementations, comparing their test vector results to that. Otherwise you have a mess. Why doesn't mastercoin follow this best practice that has worked so well for the standards industry?

littleblue
Sr. Member
****
Offline

Activity: 285
Merit: 250


View Profile
November 21, 2013, 05:59:40 PM
 #2054

I have 2 things on my mind...and I think these points need to be address quickly to speed up development and foster outside development.


1) I think its high time that 2 developers, or at least Tachikoma is hired or contracted full time for at least a period of 2 years... this is a minimal relative cost of doing business considering the potential fast turn around of the initiative, due to having someone work on the project full time. At this point Tachikoma who blazes the trail, mostly leading developments and improvement shouldn't be scrounging around working to pay bills. His focus should be on developing and testing so we can have something dependable in no time:  Success in anything depends on FOCUS, and right now our main devs have jobs on the side trying to pay bills. We should take a page from the bitcoin foundation and emulate the hiring of Gavin Adresen.

"Concentrate all your thoughts upon the work at hand. The sun's rays do not burn until brought to a focus."


2) Is there a plan to develop something higher level to interface programmatically with mastercoin? an api maybe, although I couldn't fathom how it will work to do :

simple sends
confirmations
betting etc..

I also thinking of designing mastercoin into my system but do not know where to start, especially if this will be addressed later.

If you are in favor of one or two of these points please echo this post.
Echoing!
+1

This is what I raised up in my post as well. To echo.

This project *absolutely* needs multiple full time developers. Mastercoin foundation needs to make that happen ASAP. At my business, I can hire 3 developers to work full time for me (as well as around 13 other assorted full time engineers) and we pull in less each year than the mastercoin foundation has sitting around. Not sure why this can't be done with Mastercoin as well. Run it like a business. Priority number 1.

Once we have a solid mastercoin API library that can work across multiple languages (optimally do basic parsing in C, then use swig, etc to take out to Python, Perl, Ruby, etc) then the skill bar level is DRASTICALLY lowered. At that point, you can get generic webdevs and generaic devs that have a good mid-level understanding of bitcoin/mastercoin to do the work. The ruby, etc library is good, but we need it available for a wide variety of langs, without a bunch of implementations that all have their own ideas how the blocks should be parsed (we get the problems we are seeing today). This should be priority number 2. Pay for a *reference* C implementation and bindings to other languages can be easily made. Any new standard that comes out in the business world (e.g. audio codecs, etc), they implement a standard reference implementation, and vendors follow suit with their implementations, comparing their test vector results to that. Otherwise you have a mess. Why doesn't mastercoin follow this best practice that has worked so well for the standards industry?


+100
killerstorm
Legendary
*
Offline

Activity: 1022
Merit: 1033



View Profile
November 21, 2013, 06:12:47 PM
 #2055

Once we have a solid mastercoin API library that can work across multiple languages (optimally do basic parsing in C, then use swig, etc to take out to Python, Perl, Ruby, etc) then the skill bar level is DRASTICALLY lowered. At that point, you can get generic webdevs and generaic devs that have a good mid-level understanding of bitcoin/mastercoin to do the work.

Parsing transactions is an easy part. Maintaining the state is the hard part.

You need some means of representing the state, i.e. balance, pending orders and so on for each address.

Then you read a stream of messages and apply them one by one according to certain rules. E.g. for simple send you need this:

1. check if sending address balance is sufficient
2. decrease balance of sending address by X
3. increase balance of receiving address by X

To implement more complex rules you need more state variables for each address.

Now, the question is, are you going to implement it in C? How?

Implementing only parsing in C and rules in high-level language won't have an effect you're aiming for: parsing itself is straightforward, but rules aren't.

Example:

Quote
An address marked as savings can only do simple transfers (transaction type=0). All other transaction types require addresses without a reversibility time window.

This definitely makes sense: we do not want to define how savings feature interacts with all types of transactions

But what happens if I declare an address as savings after I have submitted an offer? Does it cancel a pending order? Or is this 'mark as savings' command ignored?

Different implementations might implement it in different ways, and getting it right is very, very tricky. On the other hand, deserialization is something a monkey can implement when it has the right tools

Chromia: a better dapp platform
lnternet
Sr. Member
****
Offline

Activity: 299
Merit: 253


View Profile
November 21, 2013, 06:38:27 PM
 #2056

I was wondering if/how/when it would be possible to implement a currency on a private website. Something like "Gold", which can be transferred between users of the site as well as outside, is safe, and leaves no worries for the developers. Can MSC do this yet?

1ntemetqbXokPSSkuHH4iuAJRTQMP6uJ9
rbdrbd
Sr. Member
****
Offline

Activity: 462
Merit: 250



View Profile
November 21, 2013, 06:41:18 PM
Last edit: November 21, 2013, 07:07:30 PM by rbdrbd
 #2057

Once we have a solid mastercoin API library that can work across multiple languages (optimally do basic parsing in C, then use swig, etc to take out to Python, Perl, Ruby, etc) then the skill bar level is DRASTICALLY lowered. At that point, you can get generic webdevs and generaic devs that have a good mid-level understanding of bitcoin/mastercoin to do the work.

Parsing transactions is an easy part. Maintaining the state is the hard part.

You need some means of representing the state, i.e. balance, pending orders and so on for each address.

Then you read a stream of messages and apply them one by one according to certain rules. E.g. for simple send you need this:

1. check if sending address balance is sufficient
2. decrease balance of sending address by X
3. increase balance of receiving address by X

To implement more complex rules you need more state variables for each address.

Now, the question is, are you going to implement it in C? How?

Implementing only parsing in C and rules in high-level language won't have an effect you're aiming for: parsing itself is straightforward, but rules aren't.

Example:

Quote
An address marked as savings can only do simple transfers (transaction type=0). All other transaction types require addresses without a reversibility time window.

This definitely makes sense: we do not want to define how savings feature interacts with all types of transactions

But what happens if I declare an address as savings after I have submitted an offer? Does it cancel a pending order? Or is this 'mark as savings' command ignored?

Different implementations might implement it in different ways, and getting it right is very, very tricky. On the other hand, deserialization is something a monkey can implement when it has the right tools

Great points. I'm no bitcoin expert obviously, but I know with bitcoin there are blockchain parsers (such as https://github.com/znort987/blockparser) that can run through and compile stats on the block chain (e.g. simple aggregate metrics, a list of addresses with balances and their balances, etc). Obviously, the rules behind mastercoin are a very good deal more complex than bitcoin, but perhaps some kind of parser could be written (not necessarily in C) that could run either as a one-shot (parse through the chain and output) or resident (with streaming output).

Output would be in a simplified JSON-formatted structure, that comprise "absolute actions" that have been validated through the spec-derived rule set encoded into the parser itself.

e.g "address A sent address B 50 MSC". In this case, the parser has done all of the difficult parsing and validation (such as, the sending address having the balance, the transaction being a valid Class A/B/C one, whatever else)...it outputs this in JSON format, a higher level web tool can either read it from a file (streamed or as a static/batch run) or maybe attach to the process's event interface via TCP/IP and get it that way.

other examples:
"address C put out an offer for 50 MSC @ .50/ea. offer ID is 1234".
"address D bid on offer 1234 for 20 of the 50 MSC"
"address E created a smart property named 'foobar' with currency ID 4567"

This way, all higher level utilities could hook into this Mastercoin daemon, which would take care of implementing the guts of the spec and take it out to a higher level streamed, JSON encoded "absolute" API, which would focus on things that have actually happened, after all of the parsing and rule validation have been taken into effect. The daemon could be available for windows, linux and mac OS X. A JSON RPC-driven query interface would also be available to allow querying of specific smart properties, transaction IDs, etc.

Hell, write the thing in ruby and use Tachikoma's work as a base for it. Or make it in python (everyone loves python, and that way I'll want to hack on it! :p)

....We shall call it.... "mastercoind" (*pinkie over mouth*)

Maybe I am smoking crack here and this won't gain us much. Just thought I'd put it out there to get the ball rolling for potential solutions. If doing the above makes sense, it would bring us in line with the way bitcoin does things (e.g. bitcoind hooking into exchange sites, armory client, p2pool, pushpool daemon, bitcoin-qt, etc), and speed new development efforts up 20x, as what we're doing now seems a bit similar to forcing everyone who wants to build their own computer to create the CPU from scratch, instead of just buying the parts and slapping them together.
djohnston
Member
**
Offline

Activity: 114
Merit: 10


View Profile WWW
November 21, 2013, 07:04:51 PM
 #2058

Great presentation Ron. Well articulated my friend. I'll post the recording once it is uploaded.

https://plus.google.com/u/0/events/cosfuleudovf9bbitllefb93874


“The state is that great fiction by which everyone tries to live at the expense of everyone else.” ― Frédéric Bastiat
Tachikoma
Hero Member
*****
Offline

Activity: 938
Merit: 1000



View Profile WWW
November 21, 2013, 07:51:06 PM
 #2059

Quote
+1000

Thanks for all the +1's people. The thing is I'm not stuck in a dead-end job at the moment. I have a pretty awesome job already, although perhaps not as awesome as Mastercoin, so getting me to work fulltime on Mastercoin would require a pretty awesome offer. It's a good thing there is more talent attached to this project Smiley

Once we have a solid mastercoin API library that can work across multiple languages (optimally do basic parsing in C, then use swig, etc to take out to Python, Perl, Ruby, etc) then the skill bar level is DRASTICALLY lowered. At that point, you can get generic webdevs and generaic devs that have a good mid-level understanding of bitcoin/mastercoin to do the work.

Parsing transactions is an easy part. Maintaining the state is the hard part.

You need some means of representing the state, i.e. balance, pending orders and so on for each address.

Then you read a stream of messages and apply them one by one according to certain rules. E.g. for simple send you need this:

1. check if sending address balance is sufficient
2. decrease balance of sending address by X
3. increase balance of receiving address by X

To implement more complex rules you need more state variables for each address.

Now, the question is, are you going to implement it in C? How?

Implementing only parsing in C and rules in high-level language won't have an effect you're aiming for: parsing itself is straightforward, but rules aren't.

Example:

Quote
An address marked as savings can only do simple transfers (transaction type=0). All other transaction types require addresses without a reversibility time window.

This definitely makes sense: we do not want to define how savings feature interacts with all types of transactions

But what happens if I declare an address as savings after I have submitted an offer? Does it cancel a pending order? Or is this 'mark as savings' command ignored?

Different implementations might implement it in different ways, and getting it right is very, very tricky. On the other hand, deserialization is something a monkey can implement when it has the right tools

I +1 Killerstorm's explanation. We absolutely need different Mastercoin implementations from the get-go to compare our interpretation of the spec. I already wrote an addition to the spec that should make comparing implementations very easy. For those interested you can read the initial draft of the verification API here.

Great presentation Ron. Well articulated my friend. I'll post the recording once it is uploaded.

https://plus.google.com/u/0/events/cosfuleudovf9bbitllefb93874

I enjoyed it as well. I was a bit sad though that none of the slides mentioned anything developed by me or the other developers. We all worked very hard to make Mastercoin more then an idea, to create something tangible. People who watched the presentation might have the idea that there is nothing yet.

Electrum: the convenience of a web wallet, without the risks | Bytesized Seedboxes BTC/LTC supported
rbdrbd
Sr. Member
****
Offline

Activity: 462
Merit: 250



View Profile
November 21, 2013, 08:13:14 PM
Last edit: November 21, 2013, 08:37:56 PM by rbdrbd
 #2060

I +1 Killerstorm's explanation. We absolutely need different Mastercoin implementations from the get-go to compare our interpretation of the spec. I already wrote an addition to the spec that should make comparing implementations very easy. For those interested you can read the initial draft of the verification API here.

I (respectfully) totally disagree. Why is this necessary? Do we need 10 different bitcoind implementations to compare the interpretation of the bitcoin spec? If the Mastercoin spec is open to multiple material differences based on its "interpretation", then that tells me that it needs to be revised to remove ambiguity. Currently, it has a lot of that and I've started asking questions to help close that gap around some of these new features. I know you and many others have done a ton in this area, and I'm sure others will help out as well. However, some small level of ambiguity will still persist, so to your point, I agree that we maybe need 2 full parser/stack implementations, but not 10. It's simply not something that the average mastercoin developer should have to deal with.

In the world of bitcoin, 90%+ of developers just hang off of bitcoind. That doesn't stop anyone from developing their own bitcoin parsing tools (e.g. sx, and others). It's just dumb to require everyone to develop their own block parsers just to be able to do anything with bitcoin. killerstorm may say the parsing mastercoin transactions is so simple a monkey could do it, but I don't know the first thing about parsing multi-sig transactions, for instance, and I'm sure the vast majority of devs on this board don't either (nor do they care). If I was going to add value to mastercoin, I'd rather work on the application I had in mind itself, rather than dinking around with bit fiddling to get my "interpretation" of the spec to show 907.3302929 MSC for transaction 3f04398298292fbcdd0f vs my buddy's showing a balance of 907.594029. Come on....waste of time.

Having each developer basically creating their own parser off the spec when we could have one mastercoind that 90% of devs use is not optimal, in my opinion. I'd think that we want 90% of devs on this creating end-user solutions that add real value around mastercoin's awesome feature set, NOT more parser implementations that result in the confusion and issues we've been seeing lately between masterchest, mymastercoins, and master-coin explorer. Imagine that x100.

I say, if you're the 10% of devs that want or need to create your own parser and spec engine, go for it. Otherwise, use mastercoind, hook into the realtime event feed, spend 10 minutes writing the code to parse apart the JSON for the events you want, and focus on your features.

That is the only way Mastercoin is going to win this race.
Pages: « 1 ... 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 [103] 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 ... 163 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!