Hello, I'm in the process of putting together a team for an exchange project that I'm working on and I'm looking to hire some good developers to join me (remote work.) Most of the details about this project are already public: but in a nutshell what we are trying to do is to build a general-purpose exchange for contracts.

The current code base for it is here:
https://github.com/ambrosus/crossroads-browser

And a higher level description of the project is here:
https://blog.ambrosus.com/crossroads-towards-a-universal-browser-for-deals-1905b024dee3

Since the goal is quite ambitious, the first step is simply to get a working system for a single kind of contract going. The first contract we're trying to implement on this platform is going to be for a simple derivative / future contract.

I don't have much time to baby sit developers but your role in the project would be to help get the back-end for version 1 of the trade engine stable enough not to crash constantly It's a small team though so there's front-end work, smart contracts, scripting, and so on. We'll be hiring a few developers for this and its a large project.

Let me know if anyone is interested. My work email is matthew@ambrosus.com if anyone wants to make an introduction or showoff your Githubs.

[For more information visit our webpage:]

For more information visit our webpage: www.ambrosus.com


WHAT THIS IS



WHAT WE DO


TOKEN: AMBER (AMB)
ICO: SEPTEMBER 2017 (Date TBC) - Participants will need to go through KYC process.

WHO WE ARE
Meet the Ambrosus Builders

Angel Versetti, CEO (ex-Project Lead at the United Nations, Founder of Versetti & Co and serial crypto-investor)
Dr Stefan Meyer, CTO (ex-Founding Director of EPFL Food and Nutrition Center and serial IoT entrepreneur)
Dr Gavin Wood, Technical Advisor Core Architecture (Ethereum Co-Founder, inventor of Solidity, Co-Founder of Parity)
Dr Jutta Steiner, Technical Advisor Supply Chains (Co-Founder Parity and Provenance, ex-Security Manager at Ethereum)
Professor Jean-Paul Sandoz, Lead Engineer (ex-Professor of Electronics at University of Applied Sciences Western Switzerland and serial inventor)
Marek Kirejczyk, Lead Blockchain Developer (ex-Vice President at Daftcode and serial blockchain entrepreneur)
Matthew Roberts, Lead Blockchain Developer (ex-developer at Storj, Co-Founder of Coinbend and serial blockchain inventor)
Konrad Szalwinski, Lead Front-End Developer (ex-Lead/Senior Developer at Assertis, Codilime, Gamesys and Crowdpark)
Katerina Ianishevska, Community Manager (ex-Journalist/PR at StartUs/Meshine, ex-Investment Law researcher at the University of Thessaloniki).
Dhanesh Kothari, Mentor (ex-Vice President J.P. Morgan, Global IT Products; ex-Credit Suisse Vice-President, Portfolio Management Systems)
Jaron Lukasiewicz, Strategic Advisor (ex-Founder/CEO Coinsetter and Cavirtex; ex-Investment Banker at J.P.Morgan)
David Drake, Strategic Advisor (Chairman LDJ Capital, President of Soho Loft Media Group, Board Member NYC Opera and Washington Ballet)
Jehan Chu, Strategic Advisor (Managing Partner, Kenetic Capital, Founder Ethereum HK, Co-Founder Bitcoin Association HK, Founder Hyperledger HK)
Dr Vlad Trifa, Technical Advisor Hardware (Founder of Web of Things & EVRYTHNG and Head of Digital Lab, Swisscom)
Professor Malcolm J W Povey, Scientific Advisor Food Reassurance (Professor of Food Physics, Inventor of Cygnus UVM, the Acoustiscan scanner and Ultracane)
Dr Fabiola Dionisi, Scientific Advisor Food Quality Control (Global R&D Programme Leader at Nestlé)
Professor Esther Amstad, Scientific Advisor Food Tracers (Head of Soft Materials Laboratory at the Swiss Federal Institute of Technology, EPFL, former Harvard Post-Doc)
Professor Sandro Carrara, Scientific Advisor Biosensors (Senior Scientist at the Integrated Systems Laboratory at the Swiss Federal Institute of Technology, EPFL)
Tom Lyons, Communications Advisor (Owner, Lyons Communications and Chair Communications Working Group, Crypto Valley Association)
David Wachsman, Public Relations Advisor (Director, Wachsman PR)

WHO SUPPORTS US



WHO WRITES ABOUT US



WHERE TO FIND US



OUR SOCIAL MEDIA
Github: https://github.com/ambrosus
Twitter: https://twitter.com/AmbrosusAMB
LinkedIn: https://www.linkedin.com/company-beta/13352564/
Facebook: https://www.facebook.com/ambrosusAMB
Discord (safer alternative to slack): https://discordapp.com/invite/jbmWg8c
Reddit: https://www.reddit.com/r/ambrosus/
Telegram: https://t.me/AmbrosusAMB
Publications (Technical Papers, Use Cases, Vision Paper, White Paper): https://ambrosus.com/#tech-docs


Blog:
blog.ambrosus.com
Roadmap, Deliverables:
https://blog.ambrosus.com/ambrosus-post-ico-roadmap-2017-2020-f7ad7d9ce9cf



Videos:
Baby Food Use Case: https://www.youtube.com/watch?v=OkdCV6zw3lI
Ethereum-Powered Food Checker Demo: https://www.youtube.com/watch?v=bc8SDl3NfBw


Press:
http://munchies.vice.com/en_us/article/j5pwb4/beyond-bitcoin-how-the-blockchain-could-change-the-way-we-eat
https://www.psfk.com/2017/07/the-blockchain-is-being-used-to-track-food-quality.html
https://www.ethnews.com/ambrosus-will-leverage-ethereum-and-iot-to-track-food-supplies
https://www.cryptocoinsnews.com/blockchain-based-ecosystem-tackles-food-supply-chain-deficiencies-sets-token-sale/

OUR BOUNTY PROGRAM
Please check out our google doc. The programme is still work in progress, so some changes may take place in the future. Ambits already awarded to people will be honoured in case of changes.

Newbie - Max 50 chars

AMBROSUS ICO -  SEPTEMBER 2017 - AMBROSUS.COM

Jr. Member - Max 150 chars

Code:

[url=/index.php?topic=2034826.0]▃▃▌▌AMBROSUS▐▐▃▃▃[/url] -TRUSTED QUALITY OF FOOD & MEDICINE | [url=https://ambrosus.com]WEBSITE[/url] | ICO: SEPTEMBER 2017
or
[url=/index.php?topic=2034826.0]░░▒▓ AMBROSUS ▓▒░░[/url] --TRUSTED QUALITY OF FOOD & MEDICINE | [url=https://ambrosus.com]WEBSITE[/url] | ICO: SEPTEMBER 2017
or
[url=/index.php?topic=2034826.0]══╣▓ AMBROSUS ▓╠══[/url] -TRUSTED QUALITY OF FOOD & MEDICINE | [url=https://ambrosus.com]WEBSITE[/url] | ICO: SEPTEMBER 2017
or
[url=/index.php?topic=2034826.0]══╣█ AMBROSUS █╠══[/url] -TRUSTED QUALITY OF FOOD & MEDICINE | [url=https://ambrosus.com]WEBSITE[/url] | ICO: SEPTEMBER 2017

▃▃▌▌AMBROSUS▐▐▃▃▃ -TRUSTED QUALITY OF FOOD & MEDICINE | WEBSITE | ICO: SEPTEMBER 2017
or
░░▒▓ AMBROSUS ▓▒░░ -TRUSTED QUALITY OF FOOD & MEDICINE | WEBSITE | ICO: SEPTEMBER 2017
or
══╣▓ AMBROSUS ▓╠══ -TRUSTED QUALITY OF FOOD & MEDICINE | WEBSITE | ICO: SEPTEMBER 2017
or
══╣█ AMBROSUS █╠══ -TRUSTED QUALITY OF FOOD & MEDICINE | WEBSITE | ICO: SEPTEMBER 2017

Member - Unlimited size

Code:

[center]▃▃▌▌AMBROSUS▐▐▃▃▃ - TRUSTED QUALITY OF FOOD & MEDICINE[/center]
[center][url=https://bitcointalk.org/index.php?topic=2034826.0]Bitcointalk[/url] | [url=https://ambrosus.com]Web[/url] | [url=https://docs.google.com/document/d/1pgv54bcUFs9PasgI3EqpQCopSPrYiVRK6ZEXi9H7y0E/edit?usp=sharing]Bounty[/url] | [url=https://blog.ambrosus.com/]Blog[/url] | [url=https://twitter.com/AmbrosusAMB]Twitter[/url] | [url=https://www.facebook.com/ambrosusAMB]Facebook[/url][/center]
[center]ICO SEPTEMBER 2017[/center]

▃▃▌▌AMBROSUS▐▐▃▃▃ - TRUSTED QUALITY OF FOOD & MEDICINE

Bitcointalk | Web | Bounty | Blog | Twitter | Facebook

ICO SEPTEMBER 2017

Sr. Member - Unlimited size + font size

Code:

[center]
[table]
[tr]
[td][center]
[size=14px][url=https://ambrosus.com][color=blue]AMBROSUS[/color][/url][/size]
[size=1px][font=monospace][color=#0000FF]
..................................`.-://█oo█████████████████o█/:-...................................
............................`.:/██████████████████████████████████████:.............................
.........................-:███████████████//:-..````..-:/█████████████████/-`.......................
....................`-:█████████/:████:-`..`.-://////::-`.``-█████████████████/.....................
.................`-/███████/-.`.`.--.``.:██████████████████/-``.████/.-/█████████/..................
..............`-/██████/-.`..-██:..../████:.``........``-/█████-.`:███:..`./████████/`..............
.............:██████/-`....`/██-`.-███/.`..................`-████:.`/███....`.:████████-............
.........../█████/-`.......██/`..███:`.........`....`.........`/███...███-......./███████-..........
........./█████:.`........██/`.-██/`.........-████████/`.........███:.`███-.......`-███████-........
.......:█████:`.........`██/`.:██:.........`████████████-........./██/.`███...........███████-......
....`:█████:`.........../██`.-██:..........██████████████`........./██:.`███............███████`....
..../████:..............██-.`███...........██████████████`..........███`.████:............██████:...
.`:████/................██`.-██............██████████████............██:`█████`............:██████`.
`/████:`................``../██`............████████████`...........`███./███/..............`██████`
`█████................./██:./██..............`████████-..............███..``.................-█████.
../████-`.............█████.:██`..............████████/.............`██/..██:..............`/█████-.
..`:████/.............-████`.██:.............██████████.............:██-..██:.............-██████...
....-█████/............`███..███.............██████████............`███..███`............██████/`...
.....`:█████/...........:██-.`███`...........██████████/..........`███`.-██/...........███████......
......../█████/.`........███...███..........████████████..........███...███........`-███████-.......
........../██████-`......`███-.`███/`.......████████████.......`/███`.-███`......`:███████-.........
............/██████/-`....`/██/`.-███/......................../███:.`/███`....`-████████-...........
.............`:████████-`...-███-``:████/.`..............`.:████:`..███-...`-████████/..............
................-█████████/-``/███:`../██████:--.....-:██████/..``.`/:``./█████████-`...............
..................`-███████████/█████:```-/██████████████/-`.`-███:.:███████████-`..................
......................./█████████████████:.`````....`````.:█████████████████/.......................
...........................:████████████████████████████████████████████:...........................
..............................`.:/████████████████████████████████/-................................
......................................`.-://███████████//::-.`......................................

[/color][/font][/size]
[/center][/td]
[td]
[center]TRUSTED QUALITY OF FOOD & MEDICINE[/center]
  [url=https://bitcointalk.org/index.php?topic=2034826.0]Bitcointalk[/url] | [url=https://ambrosus.com]Web[/url] | [url=https://docs.google.com/document/d/1pgv54bcUFs9PasgI3EqpQCopSPrYiVRK6ZEXi9H7y0E/edit?usp=sharing]Bounty[/url] | [url=https://blog.ambrosus.com/]Blog[/url] | [url=https://twitter.com/AmbrosusAMB]Twitter[/url] | [url=https://www.facebook.com/ambrosusAMB]Facebook[/url]
[center]ICO SEPTEMBER 2017[/center][/td]
[/tr]
[/table][/center]

AMBROSUS ..................................`.-://█oo█████████████████o█/:-................................... ............................`.:/██████████████████████████████████████:............................. .........................-:███████████████//:-..````..-:/█████████████████/-`....................... ....................`-:█████████/:████:-`..`.-://////::-`.``-█████████████████/..................... .................`-/███████/-.`.`.--.``.:██████████████████/-``.████/.-/█████████/.................. ..............`-/██████/-.`..-██:..../████:.``........``-/█████-.`:███:..`./████████/`.............. .............:██████/-`....`/██-`.-███/.`..................`-████:.`/███....`.:████████-............ .........../█████/-`.......██/`..███:`.........`....`.........`/███...███-......./███████-.......... ........./█████:.`........██/`.-██/`.........-████████/`.........███:.`███-.......`-███████-........ .......:█████:`.........`██/`.:██:.........`████████████-........./██/.`███...........███████-...... ....`:█████:`.........../██`.-██:..........██████████████`........./██:.`███............███████`.... ..../████:..............██-.`███...........██████████████`..........███`.████:............██████:... .`:████/................██`.-██............██████████████............██:`█████`............:██████`. `/████:`................``../██`............████████████`...........`███./███/..............`██████` `█████................./██:./██..............`████████-..............███..``.................-█████. ../████-`.............█████.:██`..............████████/.............`██/..██:..............`/█████-. ..`:████/.............-████`.██:.............██████████.............:██-..██:.............-██████... ....-█████/............`███..███.............██████████............`███..███`............██████/`... .....`:█████/...........:██-.`███`...........██████████/..........`███`.-██/...........███████...... ......../█████/.`........███...███..........████████████..........███...███........`-███████-....... ........../██████-`......`███-.`███/`.......████████████.......`/███`.-███`......`:███████-......... ............/██████/-`....`/██/`.-███/......................../███:.`/███`....`-████████-........... .............`:████████-`...-███-``:████/.`..............`.:████:`..███-...`-████████/.............. ................-█████████/-``/███:`../██████:--.....-:██████/..``.`/:``./█████████-`............... ..................`-███████████/█████:```-/██████████████/-`.`-███:.:███████████-`.................. ......................./█████████████████:.`````....`````.:█████████████████/....................... ...........................:████████████████████████████████████████████:........................... ..............................`.:/████████████████████████████████/-................................ ......................................`.-://███████████//::-.`......................................

TRUSTED QUALITY OF FOOD & MEDICINE  Bitcointalk | Web | Bounty | Blog | Twitter | Facebook ICO SEPTEMBER 2017

Hero/Legendary - Unlimited size + Font size

Code:

[center]
[table]
[tr]
[td][center][size=9px] [/size][size=2px][font=monospace][color=#0000FF]
..................................`.-://█oo█████████████████o█/:-...................................
............................`.:/██████████████████████████████████████:.............................
.........................-:███████████████//:-..````..-:/█████████████████/-`.......................
....................`-:█████████/:████:-`..`.-://////::-`.``-█████████████████/.....................
.................`-/███████/-.`.`.--.``.:██████████████████/-``.████/.-/█████████/..................
..............`-/██████/-.`..-██:..../████:.``........``-/█████-.`:███:..`./████████/`..............
.............:██████/-`....`/██-`.-███/.`..................`-████:.`/███....`.:████████-............
.........../█████/-`.......██/`..███:`.........`....`.........`/███...███-......./███████-..........
........./█████:.`........██/`.-██/`.........-████████/`.........███:.`███-.......`-███████-........
.......:█████:`.........`██/`.:██:.........`████████████-........./██/.`███...........███████-......
....`:█████:`.........../██`.-██:..........██████████████`........./██:.`███............███████`....
..../████:..............██-.`███...........██████████████`..........███`.████:............██████:...
.`:████/................██`.-██............██████████████............██:`█████`............:██████`.
`/████:`................``../██`............████████████`...........`███./███/..............`██████`
`█████................./██:./██..............`████████-..............███..``.................-█████.
../████-`.............█████.:██`..............████████/.............`██/..██:..............`/█████-.
..`:████/.............-████`.██:.............██████████.............:██-..██:.............-██████...
....-█████/............`███..███.............██████████............`███..███`............██████/`...
.....`:█████/...........:██-.`███`...........██████████/..........`███`.-██/...........███████......
......../█████/.`........███...███..........████████████..........███...███........`-███████-.......
........../██████-`......`███-.`███/`.......████████████.......`/███`.-███`......`:███████-.........
............/██████/-`....`/██/`.-███/......................../███:.`/███`....`-████████-...........
.............`:████████-`...-███-``:████/.`..............`.:████:`..███-...`-████████/..............
................-█████████/-``/███:`../██████:--.....-:██████/..``.`/:``./█████████-`...............
..................`-███████████/█████:```-/██████████████/-`.`-███:.:███████████-`..................
......................./█████████████████:.`````....`````.:█████████████████/.......................
...........................:████████████████████████████████████████████:...........................
..............................`.:/████████████████████████████████/-................................
......................................`.-://███████████//::-.`......................................

[/color][/font][/size]
[/center][/td]
[td]
[center][url=https://ambrosus.com][color=blue]AMBROSUS[/color][/url] - TRUSTED QUALITY OF FOOD & MEDICINE[/center][hr]
[url=https://bitcointalk.org/index.php?topic=2034826.0]Bitcointalk[/url] | [url=https://ambrosus.com]Web[/url] | [url=https://docs.google.com/document/d/1pgv54bcUFs9PasgI3EqpQCopSPrYiVRK6ZEXi9H7y0E/edit?usp=sharing]Bounty[/url] | [url=https://blog.ambrosus.com/]Blog[/url] | [url=https://twitter.com/AmbrosusAMB]Twitter[/url] | [url=https://www.facebook.com/ambrosusAMB]Facebook[/url] [hr]
[center]ICO SEPTEMBER 2017[/center]
[/td]

[td][center][size=9px] [/size][size=2px][font=monospace][color=#0000FF]
..................................`.-://█oo█████████████████o█/:-...................................
............................`.:/██████████████████████████████████████:.............................
.........................-:███████████████//:-..````..-:/█████████████████/-`.......................
....................`-:█████████/:████:-`..`.-://////::-`.``-█████████████████/.....................
.................`-/███████/-.`.`.--.``.:██████████████████/-``.████/.-/█████████/..................
..............`-/██████/-.`..-██:..../████:.``........``-/█████-.`:███:..`./████████/`..............
.............:██████/-`....`/██-`.-███/.`..................`-████:.`/███....`.:████████-............
.........../█████/-`.......██/`..███:`.........`....`.........`/███...███-......./███████-..........
........./█████:.`........██/`.-██/`.........-████████/`.........███:.`███-.......`-███████-........
.......:█████:`.........`██/`.:██:.........`████████████-........./██/.`███...........███████-......
....`:█████:`.........../██`.-██:..........██████████████`........./██:.`███............███████`....
..../████:..............██-.`███...........██████████████`..........███`.████:............██████:...
.`:████/................██`.-██............██████████████............██:`█████`............:██████`.
`/████:`................``../██`............████████████`...........`███./███/..............`██████`
`█████................./██:./██..............`████████-..............███..``.................-█████.
../████-`.............█████.:██`..............████████/.............`██/..██:..............`/█████-.
..`:████/.............-████`.██:.............██████████.............:██-..██:.............-██████...
....-█████/............`███..███.............██████████............`███..███`............██████/`...
.....`:█████/...........:██-.`███`...........██████████/..........`███`.-██/...........███████......
......../█████/.`........███...███..........████████████..........███...███........`-███████-.......
........../██████-`......`███-.`███/`.......████████████.......`/███`.-███`......`:███████-.........
............/██████/-`....`/██/`.-███/......................../███:.`/███`....`-████████-...........
.............`:████████-`...-███-``:████/.`..............`.:████:`..███-...`-████████/..............
................-█████████/-``/███:`../██████:--.....-:██████/..``.`/:``./█████████-`...............
..................`-███████████/█████:```-/██████████████/-`.`-███:.:███████████-`..................
......................./█████████████████:.`````....`````.:█████████████████/.......................
...........................:████████████████████████████████████████████:...........................
..............................`.:/████████████████████████████████/-................................
......................................`.-://███████████//::-.`......................................

[/color][/font][/size]
[/center][/td]
[/tr]

[/table][/center]

..................................`.-://█oo█████████████████o█/:-................................... ............................`.:/██████████████████████████████████████:............................. .........................-:███████████████//:-..````..-:/█████████████████/-`....................... ....................`-:█████████/:████:-`..`.-://////::-`.``-█████████████████/..................... .................`-/███████/-.`.`.--.``.:██████████████████/-``.████/.-/█████████/.................. ..............`-/██████/-.`..-██:..../████:.``........``-/█████-.`:███:..`./████████/`.............. .............:██████/-`....`/██-`.-███/.`..................`-████:.`/███....`.:████████-............ .........../█████/-`.......██/`..███:`.........`....`.........`/███...███-......./███████-.......... ........./█████:.`........██/`.-██/`.........-████████/`.........███:.`███-.......`-███████-........ .......:█████:`.........`██/`.:██:.........`████████████-........./██/.`███...........███████-...... ....`:█████:`.........../██`.-██:..........██████████████`........./██:.`███............███████`.... ..../████:..............██-.`███...........██████████████`..........███`.████:............██████:... .`:████/................██`.-██............██████████████............██:`█████`............:██████`. `/████:`................``../██`............████████████`...........`███./███/..............`██████` `█████................./██:./██..............`████████-..............███..``.................-█████. ../████-`.............█████.:██`..............████████/.............`██/..██:..............`/█████-. ..`:████/.............-████`.██:.............██████████.............:██-..██:.............-██████... ....-█████/............`███..███.............██████████............`███..███`............██████/`... .....`:█████/...........:██-.`███`...........██████████/..........`███`.-██/...........███████...... ......../█████/.`........███...███..........████████████..........███...███........`-███████-....... ........../██████-`......`███-.`███/`.......████████████.......`/███`.-███`......`:███████-......... ............/██████/-`....`/██/`.-███/......................../███:.`/███`....`-████████-........... .............`:████████-`...-███-``:████/.`..............`.:████:`..███-...`-████████/.............. ................-█████████/-``/███:`../██████:--.....-:██████/..``.`/:``./█████████-`............... ..................`-███████████/█████:```-/██████████████/-`.`-███:.:███████████-`.................. ......................./█████████████████:.`````....`````.:█████████████████/....................... ...........................:████████████████████████████████████████████:........................... ..............................`.:/████████████████████████████████/-................................ ......................................`.-://███████████//::-.`......................................

AMBROSUS - TRUSTED QUALITY OF FOOD & MEDICINE Bitcointalk | Web | Bounty | Blog | Twitter | Facebook ICO SEPTEMBER 2017

..................................`.-://█oo█████████████████o█/:-................................... ............................`.:/██████████████████████████████████████:............................. .........................-:███████████████//:-..````..-:/█████████████████/-`....................... ....................`-:█████████/:████:-`..`.-://////::-`.``-█████████████████/..................... .................`-/███████/-.`.`.--.``.:██████████████████/-``.████/.-/█████████/.................. ..............`-/██████/-.`..-██:..../████:.``........``-/█████-.`:███:..`./████████/`.............. .............:██████/-`....`/██-`.-███/.`..................`-████:.`/███....`.:████████-............ .........../█████/-`.......██/`..███:`.........`....`.........`/███...███-......./███████-.......... ........./█████:.`........██/`.-██/`.........-████████/`.........███:.`███-.......`-███████-........ .......:█████:`.........`██/`.:██:.........`████████████-........./██/.`███...........███████-...... ....`:█████:`.........../██`.-██:..........██████████████`........./██:.`███............███████`.... ..../████:..............██-.`███...........██████████████`..........███`.████:............██████:... .`:████/................██`.-██............██████████████............██:`█████`............:██████`. `/████:`................``../██`............████████████`...........`███./███/..............`██████` `█████................./██:./██..............`████████-..............███..``.................-█████. ../████-`.............█████.:██`..............████████/.............`██/..██:..............`/█████-. ..`:████/.............-████`.██:.............██████████.............:██-..██:.............-██████... ....-█████/............`███..███.............██████████............`███..███`............██████/`... .....`:█████/...........:██-.`███`...........██████████/..........`███`.-██/...........███████...... ......../█████/.`........███...███..........████████████..........███...███........`-███████-....... ........../██████-`......`███-.`███/`.......████████████.......`/███`.-███`......`:███████-......... ............/██████/-`....`/██/`.-███/......................../███:.`/███`....`-████████-........... .............`:████████-`...-███-``:████/.`..............`.:████:`..███-...`-████████/.............. ................-█████████/-``/███:`../██████:--.....-:██████/..``.`/:``./█████████-`............... ..................`-███████████/█████:```-/██████████████/-`.`-███:.:███████████-`.................. ......................./█████████████████:.`````....`````.:█████████████████/....................... ...........................:████████████████████████████████████████████:........................... ..............................`.:/████████████████████████████████/-................................ ......................................`.-://███████████//::-.`......................................

Link to bounty programme: https://docs.google.com/document/d/1pgv54bcUFs9PasgI3EqpQCopSPrYiVRK6ZEXi9H7y0E/edit

[For more information visit our webpage:]

For more information visit our webpage: www.ambrosus.com













OUR SOCIAL MEDIA
Github: https://github.com/ambrosus
Twitter: https://twitter.com/AmbrosusAMB
LinkedIn: https://www.linkedin.com/company-beta/13352564/
Facebook: https://www.facebook.com/ambrosusAMB
Discord (safer alternative to slack): https://discordapp.com/invite/jbmWg8c
Reddit: https://www.reddit.com/r/ambrosus/
Telegram: https://t.me/AmbrosusAMB
Publications (Technical Papers, Use Cases, Vision Paper, White Paper): https://ambrosus.com/#tech-docs


Blog:
blog.ambrosus.com

Videos:
Baby Food Use Case: https://www.youtube.com/watch?v=OkdCV6zw3lI
Ethereum-Powered Food Checker Demo: https://www.youtube.com/watch?v=bc8SDl3NfBw


Press:
http://munchies.vice.com/en_us/article/j5pwb4/beyond-bitcoin-how-the-blockchain-could-change-the-way-we-eat
https://www.psfk.com/2017/07/the-blockchain-is-being-used-to-track-food-quality.html
https://www.ethnews.com/ambrosus-will-leverage-ethereum-and-iot-to-track-food-supplies
https://www.cryptocoinsnews.com/blockchain-based-ecosystem-tackles-food-supply-chain-deficiencies-sets-token-sale/

OUR BOUNTY PROGRAM HAS NOW CLOSED
The programme is still work in progress, so some changes may take place in the future. Ambits already awarded to people will be honoured in case of changes.




Bounty Has Now Closed

Edit: This was a harmless joke but I've received many pitches that were just like this. If you're a developer be sure to look out for scams  

[Here's how it works:]

Posted this to /r/ethereum but had zero comments. Tell me what you guys think of the concept

Here's an idea for a new smart contract that creates an autonomous bug bounty system. It can be used to create self-patching software that crowd-sources human expertise to hack software and then fixes it without the need for trusted payments.

Here's how it works:

1. Create a contract with a hash of a binary file and a URL to download the file (contract TX.)
2. Commit to a hash of (an exploit binary + a reward address) (exploit hash TX.)
3. Reveal the exploit in private to the vendor and give them time to patch the software. To do this they create a new transaction that updates the binary hash and URL in step 1 (update TX.)
4. Reveal the exploit content by proving the hash in step 2 (reveal exploit TX.)
The network then validates the exploit based on the rules set forth in the contract. The binary file is downloaded and run in a virtual machine and an exploit is expressed in terms of user-input to the program (via network e.g. remote code execution; via disk / file input, or via user-input, etc.) That is: the program is run deterministically by full nodes against an input as part of the consensus rules for that blockchain.

If the exploit can successfully set some protected memory region (or whatever conditions are specified in the contract), then money is taken from the bug bounty pool used to fund the contract and given to the address in step 3 (based on using the blockchain to record who first defined a given exploit in the case of two auditors releasing duplicate vectors.)

Benefits:

• Auditors are now guaranteed payment for exploits. In the past security work has been poorly rewarded or not rewarded at all (contrary to so-called bug bounty policies for a given company.)
• Validation is automatic and payment is always on time. There is no waiting around via email to get a reward.
• The bug bounty program is clearly defined. Auditors aren't going to attack private network resources with this model.

Now there are some unexpected game-theory dynamics that this opens up which could benefit consumers. Namely, you can set penalties within the smart contract to occur against the vendor if they take too long to patch the software and you can also set a time frame that must elapse before a reward can be given out (after which the auditor can release the exploit and claim the reward.)

This will give the vendor time to patch the software and it forces the auditor to wait before releasing a working exploit in the wild. The whole process here clearly defines the responsibilities of both parties so that when an exploit is executed against the old software customers aren't automatically going to be screwed.

Patch contracts

Another idea is the inverse of exploit contracts - patch contracts. If patches are expressed as small programs that can only add or remove a certain number of lines of code from the original software (which is recorded as a deterministic build system with comprehensive test-cases), then it might be possible to actually verify whether the software has been patched. And if that's the case then that can also be added back into the original smart contract.

Hell, you can even crowd-source patches and create incentivized, self-patching programs. Thoughts?

outdated

outdated

outdated

I've been working on a series of new smart contracts for doing p2p cloud storage that make it so that users can pay to download back their stored files without the host being able to receive payment for delivering back the wrong content. The contracts are all fully atomic - you either get back your original data and the host gets paid for it -- or you don't and you get a full refund.

The person that hosts the contents are also periodically audited through a separate smart contract to ensure that they're still hosting files. If they are -- they are guaranteed payment for it without a third-party -- and if they aren't -- the audit payments are refunded to the person paying for the storage with the results publicly verifiable. If a host fails audits (or fails to provide requested content) - they don't get paid for it, the requester gets a refund, and it then has negative consequences for their long-term reputation / proof-of-stake -- however the bulk of this scheme relies on cryptography and not collateral or reputation for it to be enforceable.

Additionally, the scheme is all pay-as-you go so the host only gets paid for as long as they store content and the file owner only makes payment based on the number of downloads. (So hosts get paid for storing files long-term and each time they have to upload them back when requested. Disk space and bandwidth, basically.)

Let me know what you think. It's quite a long read but there's some fairly new ideas there. Like using zero-knowledge proofs for SHA 256 TXID preimages to sign partial transaction chains, using partial transactions to force someone to reveal private keys, homomorphic encryption based on ECDSA + ElGamel, using Bitcoin double-spends as a kind of random number generator (not exactly but for random audits at least.)

The paper is here: http://roberts.pm/atomic_cloud_storage

x

[Description:]

Bitcoin has got me down a lot lately so I decided to code something completely unrelated to money: bartering

www.barterhack.com

Description: It's a service that lets you trade your technical skills for other people's.

• Use case 1: let's say that you're an expert at programming but you really suck at marketing and you're building a cool new project that could really use some exposure: you could use Barter Hack to offer your programming skills in exchange for some marketing and now you don't need to have any money!
• Use case 2: you've been doing a lot of front end work lately and you're bored of it. You really want to move on to doing some programming again but you can't until the UI is done. Meanwhile, there's a designer somewhere having the opposite problem who is over having to code stuff. Solution: use Barter Hack to SWAP work.
• Use case 3: you're an expert at [insert skill here] but not [insert skill here] and you could really use some mentoring. Use Barter Hack to teach each other new skills.
• ?
• Profit.

Anyway, check it out. The site is only basic at this point as I'm still trying to figure out exactly what people need but there's already listings up.

Outdated

[Coinbend: p2p coin swaps with complete strangers.]

Coinbend: p2p coin swaps with complete strangers.

Announcing Coinbend

A few days ago I released my prototype for trading alt-coins without a third-party. My software is the first of its kind to be able to do this - all existing exchanges can't because of transaction malleability but I've found a way to solve this problem for alt-coins without resorting to third-party trust . . . which means: hello functional cross-currency smart contracts. But before I get you too excited: this is only a development prototype missing a lot of features that a consumer release would have.

Even though the software works fine with real money - I suggest you only use this with testcoins for now. And keep in mind that p2p matching isn't functional and there isn't even a refund option so only direct trade works. But having said that: you can, as of this very moment: use this software to trade alt-coins directly with other people. Even if you've never met them before and don't trust them: you can still trade coins. So hopefully when this is finished there will be no more escrow scams or hacked exchanges.

The main benefits of my design:

• Dynamic multi-currency support. It will work with Bitcoin, Litecoin, Dogecoin, Namecoin, Feathercoin, Peercoin, ... any of the hundreds of alt-coins and future alt-coins can be traded in arbitrary combinations.
• High security, trustless. Coinbend uses a new type of cryptography based on time-lock encryption that allows the exchange to provide a secure trade system without third-party involvement.
• Peer-to-peer. Coinbend is the first p2p exchange for alt-coins to solve the trust problem. Existing exchanges suffer from transaction malleability or aren't truly peer-to-peer but Coinbend uses some clever game theory and crypto to provide the first truly trustless exchange.

If anyone wants to check out what I have so far and give me some feedback - I'd really appreciate it as this hasn't received much attention.

Btw, check out the demo nodes: http://alice.coinbend.com and http://bob.coinbend.com. Instructions are in the main thread if you want to try out some simulated p2p trading with testcoins or you can download the main client and try it with a friend using currencies of your choice.

See the main thread here for details: https://bitcointalk.org/index.php?topic=1154211.0

[Coinbend: p2p coin swaps with complete strangers.]

Coinbend: p2p coin swaps with complete strangers.

Announcing Coinbend

Coinbend is the first functional exchange for trading cryptocurrencies that doesn't require a third party. I've been working hard on this software for a while now and this is the first version that runs so I'm releasing this early for feedback.

Keep in mind this is only a prototype so only use this with testcoins - the software is missing a lot of features and doesn't even have a functional order book - but its fully functioning when it comes to trading coins and you can test it if you connect to traders manually.

Let me know what you think of the project in the comments

Download:

• Windows
• Linux
• Source code

Online demo mode:

• Alice
• Bob

(You must enter the node ID of the other demo node for both sides to trade using demo mode.
Minimum order amounts and trade limits apply to prevent abuse.)

Video tutorial: https://www.youtube.com/watch?v=h7maCX8XKbg

How to install and start the software:

• Download and install any cryptocurrencies you want to trade.
• Open the coin clients and then close them - this will create the required data directories.
• Unzip the Coinbend download.
• Run the install file either called windows_install.bat or linux_install.sh. This will copy the database, UI, and config files so the software works.
• Start the file called coinbend.exe or coinbend on Linux -- it will patch your coins config files. Press enter to exit.
• Restart all the coins you want to use. They should now be running on the test network. Allow the blockchains to download and then run the Coinbend client again.
• When all the debug statements have stopped printing, you should see a URL. Visit http://localhost:7777/ in your browser to trade.

Video tutorial: https://www.youtube.com/watch?v=FtPCTpMlcrs

Placing a test order:
You can either place a trade on the network or trade directly with another person. Network trades currently must match 100% because partial matching isn't implemented yet so I recommend you don't do that. Instead, get a friend to run the client and enter their node ID on the trade confirm page. Both trader's must enter each other's node IDs for direct trading to work and both trades must match 100%.


Why this matters

Coinbend is the first exchange to offer dynamic multi-currency support (you read that right.) What this means in English is there are no restrictions on what alt-coins can be traded. Instead, the software will simply work with any cryptocurrency based on Bitcoin (even alt-coins that don't yet exist.)

You can also trade coin pairs in arbitrary combinations. Every aspect of the software has been designed to work with standard transactions so there are no special requirements to use this software with your favourite currency on the main network.

And last but not least: this is the first practical, p2p exchange for trading cryptocurrencies. It requires no middle man to operate, no third-party trust, and strictly gives the users control of their funds at all time. This is possible because Coinbend solves the TX malleability problem with smart contracts without depending on a third-party as a fail-safe making this the first truly trustless exchange.

How it works

Coinbend works by breaking down trades into a series of micro-trades which are carried out using micro-payment channels. The trades are placed with a standard fee (0.5%) which simultaneously serves as micro-collateral. If a micro-payment channel is ever broken, any owed micro-amounts can be recovered from the trade fees which are managed by the exchange.

Since micro-transfer amounts are designed to be as small as possible: any potential losses that might occur will be negligible and the impact of a hacked exchange would have minimal effects. In order to further reduce the risk of p2p trading: Coinbend also includes a secure refund feature. Refunds ensure that an owner's coins will eventually return to them in the event of a broken trade and work by using a new cryptographic construct called the timechain instead of traditional malleable refunds.

tl; dr, you can trade directly with complete strangers using this design without relying on a third-party but the software isn't finished yet.

(Also, please let me know if I should keep working on this as I've already put in a huge amount of time with no reward and a lot more is still needed to get this to beta.)

Developer: matthew@roberts.pm

Website: www.coinbend.com

Twitter: @coinbend

White paper 1: www.coinbend.com/whitepaper.pdf

White paper 2: www.roberts.pm/timechain

I have some transaction critical code that needs to be able to adapt to every possible circumstance and I was wondering what the simplest way to generate your own orphan blocks would be? Is there a way to configure bitcoind to do this or ... what would the custom setup look like (using RPC commands if possible + simple scripts)

I'll be coding this if it needs custom parts but can anyone suggest what the design would look like?

So I'm beginning to realize that all the good domain names are taken by squatters. If any of you have any good domain names that could be used for a wallet, exchange, coin, etc - then please PM me. I'm not willing to pay more than 1k USD for a good domain though because I know that:

• Domains cost ~$12 USD to register
• Selling squatted domains is hard
• Most squatted domains sit there for years not doing anything
• And most people have hundreds of domains they will never use

So if you just want to make a quick N * ~500+ % profit and get rid of one of your domains please PM me.

http://roberts.pm/timechain

What is the timechain? The timechain is a chain of encryption keys that can be used by anyone to encrypt information for a certain period of time - exactly how long depends on how far up the chain the keys are as each key is spaced 5 minutes apart. The timechain is also a DAC or decentralized autonomous corporation - it gives financial rewards to participants for breaking links in the chain which simultaneously releases the secrets needed to decrypt information.

By breaking links in the chain you consume 5 minutes of computing resources to be able to derive the encryption keys - which is what keeps information encrypted for a certain amount of time. When a link is broken - it also releases a puzzle to the rest of the network. The first person to solve the puzzle receives what input to use for their 5 minutes of computing resources - this is what keeps the process fair. If the first person to break a link receives the starting value for the next link then they can just keep breaking links and steal all the currency. The timechain solves that problem with mining - a very similar process to how Bitcoin does it. So our native currency with the timechain is Time (physically - since its a real cryptocurrency and ah metaphorically too.)

Why does this matter? Because as it turns out you can solve a number of important problems with the timechain. For example, if you want to do smart contracts like micropayment channels, cross-chain contracts, or anything with a refund protocol you actually can't in Bitcoin because of tx malleability - and even if you fixed that you're still screwed for alt-coins.

And what about security? We all know exchanges and wallets suck - even with multi-sig. Keeping private keys around all the time just isn't a good idea. A much smarter idea would be to store money over time. If money wasn't all available at one point in time it would be much harder to steal. So the timechain is all about making smart contracts possible today and opening up new possibilities for how we can keep our cryptocurrencies safer. Plus, there may be new uses we haven't thought of yet and that's kind of exciting.

------
We're still making changes to the paper but let us know what you think.

[timechain]

This is a paper we've been working on introducing a new type of cryptographic data structure called the timechain. The timechain is an example of a decentralized autonomous corporation that awards participants for providing reliable time-locked encryption. The paper's main revelation is you can use the timechain to build unhackable currency exchanges, wallets, merchant services, and more - there's a lot of untapped potential there and we think this structure will allow for many new kinds of smart contracts which currently aren't possible. The catch is the timechain does not solve the third-party trust problem - it simply makes third-parties considerably more secure (although you can improve trust by using multiple timechains - read the paper and this will make more sense )

Here is the link to the paper: http://roberts.pm/timechain

And this is our conclusion:

In this article we have described a system for solving the transaction malleability problem in smart contract protocols by introducing the timechain.

The timechain is a new deterministic data structure that uses a chain of time-lock encrypted RSA public keys at 5 minute intervals whose publication is incentivised through the use of hash-locked financial rewards.

Financial rewards are claimed by breaking links in the chain which must be done as early as possible or risk losing the reward. When financial rewards are claimed, the RSA private key is released automatically allowing anyone to decrypt time-locked information using that key.

The resulting process forms a decentralized autonomous corporation (DAC) that rewards participants for providing a reliable time-lock service and can be “hired” by smart contracts to provide a secure refund system without having to rely on malleable refunds transactions or a third-party service.

Finally, the timechain also makes it possible to improve the security of a number of services that handle cryptocurrencies including wallets, escrow agents, and currency exchanges by removing the need for centralization of ECDSA private keys.

Please let us know what you think of the idea and how we can make it better

I'm currently working on some software and this thread will help inform me whether its safe to assume enough altcoin users will have Bitcoin for aspects of the software to not be incredibly inconvenient or whether I need to go back to the drawing board.

Please try to keep your answers honest 

[The main benefits of my system:]

I've been working on a new design for an altcoin exchange that's significantly more practical and secure than anything that presently exists. It's primarily based around peer-to-peer trading using smart contracts, however it also incorporates aspects of regular currency exchange to facilitate fast partial matching (with a slight twist.)

My white paper is available here: https://pdf.yt/d/KzFdlJWF3UTTlf_i

The main benefits of my system:

• Huge multi-currency support. It will work with Bitcoin, Litecoin, Dogecoin, Namecoin, Feathercoin, Peercoin, ... any of the hundreds of altcoins and future altcoins can be traded in arbitrary combinations.
• My design does not rely on non-standard transactions to operate so trades will execute faster. Plus - it will work with real coins and not just test coins like other exchanges.
• It solves the transaction malleability problem that effects all existing smart contracts by constructing a new kind of dispute system. The dispute system allows third-parties to act as a fail-safe without the usual disadvantages of third-party trust.
• It's unbelievably secure. You keep full control over your coins at all times and traditional deposits are not required.

My exchange works by using double-sided micro-payment channels to allow participants to trade directly without having to depend on a third-party to move coins. Micro-payment channels and cross-chain contracts (currently used by Mercury) are both vulnerable to transaction malleability meaning an attacker can break a contract and cause coins to be irrecoverable - a situation leading to an extortion scenario. My exchange solves this problem by using a new kind of dispute system that requires minimal trust to operate. The full abstract is given bellow.

Abstract:

A peer-to-peer cryptocurrency exchange would allow for cryptocurrencies to be traded directly between users without the security risks present in centralised exchange. Smart contracts provide part of the solution but suffer from transaction malleability. In this paper, I propose a simple solution to the malleability problem by introducing a dispute system that is both practical and secure. The dispute system allows a third-party to mediate with minimal involvement and for trades to be verified against an unspent quantity. When a trade has been verified, a server is used to partially unlock the coins and allocate them between contracts which are carried out directly using incremental multi-signature transactions. This process gives the owners full control over their coins and third-party mediation is only required if a contract is interrupted or if the participants are unable to reach consensus.

Release date:
I have a proof of concept that proves the exchange mechanism works which I'll be releasing as open source in the coming weeks. It's by no means ready for use beyond simple testing (sorry if I got your hopes up) but its still an excellent first step in establishing the first secure cryptocurrency exchange.

Special thanks to: Joepie91 / Sven Slootweg for proof reading early drafts of this paper and giving valuable technical feedback; Peter Todd for helping me fix my early contract code (and generally helping me understand what I was doing.) Noel Tierman for his pioneering work in cross-chain contracts, his excellent ideas about trading systems, and the huge amount of time he took responding to my questions; Mike Hearn for his work with micro-payment channels -- the inspiration for this whole design; Jeff Garzik for creating the only library to manipulate raw transactions that isn't painful to use and generally every other person who has helped - thanks.