degdb/degdb

degdb: distributed economic graph database

degdb

Distributed Economic Graph Database

Design Doc/Ramble

Initial implementation done at PennApps 2015 Fall. There is a slow rewrite/redesign happening.

Running

# Install degdb and bitcoin dependencies
$ go get -v -u github.com/degdb/degdb github.com/btcsuite/btcwallet github.com/btcsuite/btcd

# Create the bitcoin wallet
$ btcwallet --create

# Launch new server and connect to provided peers.
$ go run main.go -peers="example.com:8181,foo.io:8182"

$GOPATH/bin must be on the path so degdb can launch instances of btcwallet and btcd.

Development

For development purposes you can launch multiple nodes within a single binary. This can only be used in development and disables connecting to external peers.

go run main.go -port=8181 -nodes=10

License

DegDB is licensed under the MIT license.

Contributors

• Tristan Rice
• Chaoyi Zha

degdb's Issues

Integrate with Tinkerpop

It would be nice to have tinkerpop integration since it's a fairly popular graph traversal system.

https://tinkerpop.incubator.apache.org/

https://tinkerpop.incubator.apache.org/docs/3.0.2-incubating/#vendor-requirements

Relates to #4.

How does degdb compare to gun?

amark/gun#127 (comment)

Project still active?

Hello,

Is this project still active?

Improved/optimized triplestore

Desired features of a new/improved triplestore

• Fast compression on disk (lz4?)
• Fast queries
• De-duplicate fields in memory (use tokens instead of ids/predicates?)
• Use existing solution (Cayley?)

As for Cayley, see concerns https://news.ycombinator.com/item?id=10589886

Support SPARQL

Requested/interest:
https://news.ycombinator.com/item?id=10587599

Support MQL

Implement billing support between servers

This is a crucial requirement for v1.0.

There are two main types of requests. Requests between servers, and requests from clients. Likely client requests will be made over HTTP/HTTPS due to the ease of writing client APIs.

Each node will need to be able to send & receive bitcoin as well as verify that the transactions haven't been double spent. Since the requests need to happen in real time, it's not acceptable to wait for confirmations which may take up to 10mins depending on transaction fee. This may require each node to keep an entire copy of the block chain (~40gb) which seems like a lot of overhead.

Each node needs to keep a copy of user metadata cached in order to quickly determine who to pay royalties to. This should happen in an async process that runs after more confirmations come in. Otherwise, clients could potentially pump money out of the server with fraudulent transactions.

Also need to set a schema for user profiles such as "degdb:/type/author" that allows for storing bitcoin addresses. Should consider only allowing that author to sign triples for itself.

Support Gremlin

Possibly integrate with Cayley, or Tinkerpop.

Determine IP address by contacting other nodes

Endpoint /api/v1/myip returns the requesters IP address.

Package network/ip allows for fetching the IP address from multiple external servers.