The first transaction is 100% complete: 0.2 btc for this graphic by mickmarona, mediated by bitspill https://i.imgur.com/84Px8y3.png
Even got a writeup by Bitcoinist! http://bitcoinist.net/the-rein-project-completes-first-freelance-contract/
Topic: [ANN] Rein - Decentralized Freelance Market - page 2. (Read 10543 times)
Today is a great day. Digital artist Mike Christ has bid and his bid accepted for a digital painting for Rein Project itself! The job is for 0.2 BTC and 0.002 BTC will go to mediator bitspill at conclusion of the job.
Here is the offer which when funded made for Rein's first official in-process job!
Here is the offer which when funded made for Rein's first official in-process job!
Code:
-----BEGIN BITCOIN SIGNED MESSAGE-----
Rein Offer
Job name: Twitter Header Image for Rein
Worker: mickmarona
Description: Friday
Bid amount (BTC): 0.2
Primary escrow address: 3GLQ2Sg25CHmmGbGPs1wREtSnAMXunvwpk
Mediator escrow address: 3FRpKRAb3iN5Mmdq9k37vrHLXfuJmkuZWR
Job ID: e7p8ma77yy106ky35cw9
Job creator: weex
Job creator public key: 0300d36a92be6d3c0b0d0aff5b14486b28013152acc4b55fc0ec84c4a209a3f234
Mediator public key: 025a19c3aa027e9114a2f79b6e2f76d85c5b3fb59723ea9dba97e019f1f751d0eb
Worker public key: 03172adca6a57a9713439f635e0057bca785c8769b69b9fafbb26ede2f3d111dc3
Primary escrow redeem script: 52210300d36a92be6d3c0b0d0aff5b14486b28013152acc4b55fc0ec84c4a209a3f23421025a19c3aa027e9114a2f79b6e2f76d85c5b3fb59723ea9dba97e019f1f751d0eb2103172adca6a57a9713439f635e0057bca785c8769b69b9fafbb26ede2f3d111dc353ae
Mediator escrow redeem script: 21025a19c3aa027e9114a2f79b6e2f76d85c5b3fb59723ea9dba97e019f1f751d0ebad51210300d36a92be6d3c0b0d0aff5b14486b28013152acc4b55fc0ec84c4a209a3f2342103172adca6a57a9713439f635e0057bca785c8769b69b9fafbb26ede2f3d111dc352ae
-----BEGIN SIGNATURE-----
1dezq4MkERrT5vRKyMTLsugNz74JVy4U6
IE0droTbyG7yZ4lBT++/kyPCrw0B/n9MykV8dPvWqcuidINYWAu92QaOZIbXW+X5GxAt8VR2eN8xCIGHnPoOT4c=
-----END BITCOIN SIGNED MESSAGE-----
Brave New Coin did a pretty thorough story. Great to see the freelancing market stats in it. http://bravenewcoin.com/news/bitcoin-only-decentralized-marketplace-rein-targets-growing-freelance-industry
Since Bitcointalk user bitspill signed up to be the first mediator, the first job has been posted.
Though it's not shown, bitspill's fee is 1% which the job creator pays on top of an accepted bid amount.
Code:
-----BEGIN BITCOIN SIGNED MESSAGE-----
Rein Job
Job name: Enable Rein to connct over Tor
Job ID: 36gf31ibfk727fwbcjr1
Category: Software
Description: Please bid to Tor-enable Rein. The job will be considered complete when a pull request is merged for https://github.com/ReinProject/python-rein/issues/1 notably giving Rein a global switch --tor that makes all network communications go through a Tor browser.
Mediator: bitspill
Mediator contact: [email protected]
Mediator public key: 025a19c3aa027e9114a2f79b6e2f76d85c5b3fb59723ea9dba97e019f1f751d0eb
Mediator master address: 12AR5UHwzpqScrYiJvgJeNbp222eWv6vRF
Job creator: weex
Job creator contact: [email protected]
Job creator public key: 0300d36a92be6d3c0b0d0aff5b14486b28013152acc4b55fc0ec84c4a209a3f234
Job creator master address: 1wexCMzikX7yxcWwzmbKHrtmxShqfthpe
-----BEGIN SIGNATURE-----
1dezq4MkERrT5vRKyMTLsugNz74JVy4U6
IFtFdR7EsWJuwUGFsSCijGF5v9U1otHinLzk72gEfEiZWDx5MH0LymtvW1QffohrV320/oB20pZkno1RdlmX8zs=
-----END BITCOIN SIGNED MESSAGE-----
Though it's not shown, bitspill's fee is 1% which the job creator pays on top of an accepted bid amount.
Added new setup guide: How To Setup Rein to Start Earning Bitcoin
Python-rein Data Model
An installation guide would be much appreciated.
https://github.com/ReinProject/python-rein/blob/master/README.md is probably the best written document on this right now. Otherwise, the second video in this playlist goes from git clone through to setting up an account. Note, there's no GUI so you should be comfortable with CLI if you want to get going at this stage. 
An installation guide would be much appreciated.
Just posted these four videos that take you through Rein and the commands available in the alpha.
The first alpha release has been tagged. To get setup, see https://github.com/ReinProject/python-rein/blob/master/README.md
Posted a new README at Python-rein as I'll probably be tagging the first alpha tomorrow.
https://github.com/ReinProject/python-rein/blob/master/README.md
https://github.com/ReinProject/python-rein/blob/master/README.md
It's been a great couple of weeks. Most of the basic commands have been built out on both client and server side. Just in the last 24 hours, I've got some redeem script checking and building in with some testing so there may not be any need to use external tools beyond the Bitcoin-signature-tool at alpha release. I want to get a version out with a walkthrough video so interested folks can test it out this month.
Updated OP to show the two main python software repos in development.
Software (pre-alpha development)
Python-rein client - Creates an identity, requests microhosting, sync's data to local Causeway server
Causeway Rein server - Grants microhosting space, ECDSA signature auth, stores and returns key/value pairs
To help test or develop, download both of the above and run the server on port 5000. Run 'rein setup' and use the address/key pairs on this sheet for testing. Then run 'rein request localhost:5000' and 'rein sync' to try to store the enrollment message you signed on your Causeway server. (last updated Jan 2nd, 2016)
Software (pre-alpha development)
Python-rein client - Creates an identity, requests microhosting, sync's data to local Causeway server
Causeway Rein server - Grants microhosting space, ECDSA signature auth, stores and returns key/value pairs
To help test or develop, download both of the above and run the server on port 5000. Run 'rein setup' and use the address/key pairs on this sheet for testing. Then run 'rein request localhost:5000' and 'rein sync' to try to store the enrollment message you signed on your Causeway server. (last updated Jan 2nd, 2016)
Sure. I really like DropZone's launch as a command line tool so the past couple weeks I've been focusing on a command line interface that sets the user up with a new account and requests free microhosting from a test server. That much is working now. Next is to store a single record to said storage, then to each of a set of servers. You can follow my progress or join in if you have python skills at https://github.com/ReinProject/python-rein
A quick update, a backend prototype is coming together in the form of a key/value server that uses the 21 wallet for authentication and payment for microhosting. That software can be found at https://github.com/jgarzik/playground21/causeway
Any updates?
Some mockups of an app in locally-saved-webpage form: http://imgur.com/a/eGT5r
Any JS/Front-end wizards want to take this on? PM me.
Any JS/Front-end wizards want to take this on? PM me.
A quick update, a backend prototype is coming together in the form of a key/value server that uses the 21 wallet for authentication and payment for microhosting. That software can be found at https://github.com/jgarzik/playground21/causeway
There is a $100-150 bounty to implement a microhosting server at https://bountify.co/create-a-bitcoin-enabled-key-value-storage-server You've got 3 days to deliver something decent or that cash goes to charity.
Speaking of the server. I got my 21 Bitcoin Computer and have been spending this weekend developing the above microhosting server on their platform. Only some basics work like verifying the signature on a request for a deposit address, requests for pricing and status. Since it's using the two1 library, support for offchain transactions via 402 payment required messages will be working shortly.
One could buy a year's worth of hosting suitable for ones own records for Rein with a few days of mining. After all, the storage requirements for the dozen text files most Rein users would need are minimal.
On the front end, I am looking to introduce more of a workflow around the bitcoin signature tool. While signing with master addresses should be done offline, there's no reason the initial setup (an intake form, choosing microhosting servers, and getting unspent outputs) can't be done online. Then that that information can be package so the signature tool can do the rest offline (e.g. create transactions for payment and signed enrollments).
Speaking of the server. I got my 21 Bitcoin Computer and have been spending this weekend developing the above microhosting server on their platform. Only some basics work like verifying the signature on a request for a deposit address, requests for pricing and status. Since it's using the two1 library, support for offchain transactions via 402 payment required messages will be working shortly.
One could buy a year's worth of hosting suitable for ones own records for Rein with a few days of mining. After all, the storage requirements for the dozen text files most Rein users would need are minimal.
On the front end, I am looking to introduce more of a workflow around the bitcoin signature tool. While signing with master addresses should be done offline, there's no reason the initial setup (an intake form, choosing microhosting servers, and getting unspent outputs) can't be done online. Then that that information can be package so the signature tool can do the rest offline (e.g. create transactions for payment and signed enrollments).
I'm working now to improve the availability and resiliency of state for the protocol. That is, shaping the incentives so people can post jobs or listings for themselves and pay to keep that data available in a professional yet decentralized manner.
Today, I've been working on a sort of microhosting where as a user is first setup, they are provided with a list of servers that are willing to host their records (user, bids, offers, disputes) for a year for a very small price (like $0.25). So the signup process (done offline via a javascript tool) would build a transaction paying N of these providers. The tool would then make it easy to sign and upload the current action (update of their user record, placing of a bid) to each of these servers.
Here's a draft spec on this: https://github.com/ReinProject/causeway/blob/master/spec.md
Today, I've been working on a sort of microhosting where as a user is first setup, they are provided with a list of servers that are willing to host their records (user, bids, offers, disputes) for a year for a very small price (like $0.25). So the signup process (done offline via a javascript tool) would build a transaction paying N of these providers. The tool would then make it easy to sign and upload the current action (update of their user record, placing of a bid) to each of these servers.
Here's a draft spec on this: https://github.com/ReinProject/causeway/blob/master/spec.md
Coinb.in now has pull request that will support our Mediator payment transactions.
For each job, a Mediator holds a third key to the 2-of-3 multisig escrow address. In order to get the Mediator paid, we also create a second address with a little bit different construction. For that address, the Mediator must sign the redeem script to move the funds; a signature from the buyer or seller is also required. This way the buyer and seller can't cut the Mediator out of their payment, which could be substantial in cases where Mediation requires more than just dispute resolution. For example if a Mediator is functioning like an oracle / supplying material information to the transaction / or must do some testing for their part. The pull request that extends Coinb.in with these Mandatory Multisig transactions is here: https://github.com/OutCast3k/coinbin/pull/30
For each job, a Mediator holds a third key to the 2-of-3 multisig escrow address. In order to get the Mediator paid, we also create a second address with a little bit different construction. For that address, the Mediator must sign the redeem script to move the funds; a signature from the buyer or seller is also required. This way the buyer and seller can't cut the Mediator out of their payment, which could be substantial in cases where Mediation requires more than just dispute resolution. For example if a Mediator is functioning like an oracle / supplying material information to the transaction / or must do some testing for their part. The pull request that extends Coinb.in with these Mandatory Multisig transactions is here: https://github.com/OutCast3k/coinbin/pull/30
Jump to: