yusefnapora

#!/bin/bash

xcode_version="Xcode-beta"

killall Xcode 2> /dev/null
sleep 1
open "/Applications/$xcode_version.app"

yusefnapora

Verifying that +sefnap is my blockchain ID. https://onename.com/sefnap

yusefnapora

#!/bin/bash

type jq >/dev/null 2>&1 || { echo >&2 "Please install jq: https://stedolan.github.io/jq/"; exit 1; }
type curl >/dev/null 2>&1 || { echo >&2 "Please install curl"; exit 1; }

if [ "$2" = "--local-ipfs" ] && (type ipfs >/dev/null 2>&1); then
  USE_LOCAL_IPFS=1
else
  USE_LOCAL_IPFS=0
fi

yusefnapora

 // The idea here is that case classes that extend `Hashable` will be converted to
 // a Json AST using json4s, then written as canonical CBOR & hashed with SHA-256
 //
 // The actual hashing happens in `MultiHash.forHashable`, which can fail if the
 // Json conversion fails.
 //
 // I don't think this custom marshaller trick will work for signatures, though,
 // because it needs the signing key as an input, which wouldn't be available to
 // the gremlin-scala marshaller.
 //

yusefnapora

Transactor interfaces

The Transactor peer nodes are responsible for writing data to the system and ensuring consistency.

Transactors have two main client-facing interfaces:

• writing data to persistent storage (e.g. IPFS) on behalf of clients
• informing clients of changes to the Journal when updates are made

yusefnapora

object Foo {

// based on this scalaz version: https://gist.github.com/Fristi/e7139a89e2c66d455e97

  implicit def applicativeFuture(implicit executionContext: ExecutionContext)
    = new Applicative[Future] {
    override def pure[A](x: A): Future[A] = Future.successful(x)

    override def ap[A, B](ff: Future[(A) => B])(fa: Future[A]): Future[B] =
      ff.flatMap(fa.map(_))

yusefnapora

  import com.amazonaws.auth.BasicAWSCredentials
  val awscreds = new BasicAWSCredentials("", "")

  import com.amazonaws.services.dynamodbv2.AmazonDynamoDBClient
  val dynamo = new AmazonDynamoDBClient(awscreds).withEndpoint("http://localhost:8000").asInstanceOf[AmazonDynamoDBClient]

  import scala.collection.JavaConversions._
  import com.amazonaws.services.dynamodbv2.model._

  val baseTable = "Mediachain"

yusefnapora

Keybase proof

I hereby claim:

• I am yusefnapora on github.
• I am yusef (https://keybase.io/yusef) on keybase.
• I have a public key ASDpxm7pgDUDKs8tbHQ4jFHkm-fb4YaPhy0bWASLQk2WBwo

To claim this, I am signing this object:

yusefnapora

$ virtualenv venv
$ source venv/bin/activate
(venv) $ pip install -U pip
(venv) $ pip install mediachain-client
(venv) $ mediachain get QmVwwiMVDH7umVSd3vdbwGS3WmFX2axhJCTpbfU4LMPcE8
{
  "metaSource": {
    "@link": "Qmcbo67Ycv6rCREhQYoYeGJzgAJiCZDfyEdtHqdbmTsv6T"
  },
  "meta": {

yusefnapora

mediachain.next api notes

Everything here is in flux and subject to change; this is just a sketch. The idea is to give an overview of the high-level api surface of an "online" node, that is, one that actively contributes to the network and is expected to remain connected to the network.

All the code examples below are in javascript, with flow-style annotations for return types.

Peer ids & local state

A peer has a unique id, which is the hash of their public key. They may also have a collection of certificates, signed by moderators of the namespaces they're authorized to participate in.

The peer-local state includes the peer's id, certificate store, private key, etc. It also includes the index of connected peers, which allows us to route operations to peers with the correct roles.