This REST service allows us to notarize data using the Bitcoin Blockchain. The REST API is documented here: REST API with spray.
resolvers ++= Seq(Resolver.sonatypeRepo("snapshots"))
libraryDependencies ++= Seq(
"com.ubirch.notary" %% "model" % "0.3.4-SNAPSHOT"
)
resolvers ++= Seq(
Resolver.sonatypeRepo("snapshots"),
"RoundEights" at "http://maven.spikemark.net/roundeights" // Hasher
)
libraryDependencies ++= Seq(
"com.ubirch.notary" %% "core" % "0.3.4-SNAPSHOT"
)
resolvers ++= Seq(Resolver.sonatypeRepo("snapshots"))
libraryDependencies ++= Seq(
"com.ubirch.notary" %% "server" % "0.3.4-SNAPSHOT"
)
resolvers ++= Seq(
Resolver.sonatypeRepo("snapshots"),
Resolver.bintrayRepo("hseeberger", "maven"), // Seeberger Json
Resolver.bintrayRepo("rick-beton", "maven"), // BeeClient
"RoundEights" at "http://maven.spikemark.net/roundeights" // Hasher
)
libraryDependencies ++= Seq(
"com.ubirch.notary" %% "client" % "0.3.4-SNAPSHOT"
)
You may configure which NotaryService the client calls by adding the test server to your config:
notaryService {
client {
url = "http://notary-dev.api.ubirch.com:8080/v1/notaryService/notarize"
}
}
- tbd
- update docker related code
- fixed assembly bug by removing a conflicting logging dependency
- update
scalatest
from 3.0.0 to 3.0.1 - improved documentation: rest-spray.md
- added field "txHashLink" to /notarize response
- upgrade to Akka 2.4.17
- update dependency: "com.ubirch.util:json-auto-convert" from 0.1 to 0.3.2
- update json4s dependencies from 3.4.0 to 3.4.2
- update dependency: "com.ubirch.util:crypto" from 0.2 to 0.3.3
- changed log imports to:
com.typesafe.scalalogging.slf4j.StrictLogging
- update logging dependencies to our current standard set:
lazy val scalaLogging = Seq(
"org.slf4j" % "slf4j-api" % "1.7.21",
"com.typesafe.scala-logging" %% "scala-logging-slf4j" % "2.1.2" exclude("org.slf4j", "slf4j-api"),
"com.typesafe.scala-logging" %% "scala-logging" % "3.5.0" exclude("org.slf4j", "slf4j-api"),
"ch.qos.logback" % "logback-core" % "1.1.7",
"ch.qos.logback" % "logback-classic" % "1.1.7"
)
- use StrictLogging instead of LazyLogging
- update dependency com.typesafe.scala-logging:scala-logging: 3.4.0 -> 3.5.0
- add Dockerfile generation
- update to sbt 0.13.12
- added Tor Support
- refactored module structure to conform with our coding conventions
./goBuild assembly && ./goBuild containerbuild
A list of links that helped us with the OP_RETURN message:
- OP_RETURN and the Future of Bitcoin
- Explanation of what an OP_RETURN transaction looks like
- bitcoin.it Wiki: OP_RETURN
- How to put custom messages into Bitcoin blockchain – OP_RETURN
- bitcoinj Mailinglist: is OP_RETURN available in bitcoinj?
Faucets: