reinproject / causeway Goto Github PK

To suppore more clients including iOS and Android, more efficient storage and retrieval or documents, a more flexible document schema and document encryption we want to make some changes to Causeway. This issue is proposal and discussion of such changes. It doesn't have to be in-depth but we just want to document the principles we're following.

Authentication for /put should verify that an enrollment is stored that delegates from 'owner' to the signature address.

This is important so that contributors know how their contributions can be used.

This requires manual communication outside Rein.

Does a count of global buckets granted and if it's more than 4 issues an error.

With the release of Bitcoin Core 0.12, it is possible to run a Bitcoin Core node at fairly minimal cost. This job is to add a json-rpc interface to Causeway (https://github.com/ReinProject/Causeway) so it can talk to Bitcoin Core. Then the code should be modified to add in endpoints that enable registered users to do each of the following: 1) request the latest block hash and height 2) request the hash and block height N blocks ago 3) or supply a block hash and retrieve a UTC timestamp and block height.

This issue also exists as a job that you can bid on in Rein.

@weex
As for Heroku, please read here: https://devcenter.heroku.com/articles/sqlite3
Guess sqlite3 should be replaced with something more robust (e.g. postgresql) for production use on Heroku.
I can modify dockerfile accordingly or even create docker-compose.yml script that would run 2 containers - one with dockerized cserver and other with postgresql database itself.

Sibling of ReinProject/python-rein#1 to enable running Causeway as a Tor hidden service. There may be a job on Rein for this where you can get bitcoins for solving this issue with a pull request.