STATUS UPDATE:The project has identified some development milestone which require additional resources to accomplish. If you are or know a experienced developer that is willing to contribute their time toward the collaborative development of our system, please reach out to me at:
medic@bitmark.co Here is a brief Sketch of the systems / components required:
1) Marking Data Processing and Storage
```Data over HTTP -> Processing Scripts -> Storage
a) To the left edge we layer on auth as required, auth is outwith "core" requirements and the system, and can be developed later / iteratively.
b) In the middle, "processing scripts", read a marking in it's data format, clean any data, expand any short names, construct a transaction to do the balance swap, ensure transaction can be settled, action it. This is "core" stuff required.
- note this step passes of much work to (2) -
c) To the right edge we have storage, something like couchdb I feel will do fine now. On that edge we can layer on caching, data export in different media types, and query engines like sparql. (expose the marking graph)These are outwith the "core" requirements and system, and can be developed later / iteratively.
```
2) Multi User Wallet API
```Data over HTTP API <-> User + Balance State and Storage <-> Blockchain
a) To the left edge we have a RESTful HTTP API, munge of linked data and web2 style REST api. Auth as required.
b) In the middle, the "multi user wallet" part pretty much a state machine controlling balances and actioning transfers, then storing that state.
c) To the right, interface to the blockchain of BTM to handle withdraws and deposits. Flow of data in both directions here.
```
markpfennig [2:55 PM]
Markus, markthis, any similar marking system are either just interfaces/proxies to [1] above, or UI wrappers around it.
markpfennig [3:02 PM]
1a) is really just rest/rww
1b) is pretty much just working with graph data and completing actions if parts of data match certain filters
1c) is graph storage, export as different formats, expose a graph of marking data
not too complex on 1 (edited)
markpfennig [3:07 PM]
2a) should just fall out as public class methods exposed over http in the nicest way possible, easy to do but hard to get right imho
2b) again isn't too hard, as long as it's tested to hell and back to be secure and have no errors (can't have balance affecting errors!) it should be fine
2c) again easy to hack, hard to do it right
markpfennig [3:08 PM]
1c, 2a, and 2c have been my hold up points, as want the right solution, and hard to envision or ideal software to do it or repurpose doesn't exist
markpfennig [3:08 PM]
massive disclaimer: my interpretation of "right" may not be needed, may be overkill, and may not be somebody elses idea of "right"
Additionally, as you can see Mark is diligently working to round up these resources through various other channels. I can assure you that we will deliver our flagship Site and API, among other things. However, we need these additional resources ASAP, and as soon as we can fill these gaps we can launch our product. Our Project had No IPO / Pre-Mine, so our lack of funds impedes our ability to hire a freelance developer (as this is what would be done under normal circumstances).
Thanks to all of you who have supported Project Bitmark
