ssadler

module TestSecp256k1 where

import Network.Komodo

import Control.Monad
import Data.Serialize
import Network.Ethereum.Crypto

import Control.Concurrent

ssadler

import Data.Word
import Control.Monad
import Control.Monad.Catch
import Test.DejaFu
import Test.DejaFu.Conc.Internal.Common
import Test.DejaFu.Conc.Internal.STM

import Control.Monad.Conc.Class
import Control.Concurrent.Classy hiding (wait)

ssadler

Keybase proof

I hereby claim:

• I am ssadler on github.
• I am ssadler (https://keybase.io/ssadler) on keybase.
• I have a public key ASA0-TnWdTImafF2eh7bsdX_59JUJoxR0c80on-6wpLqzAo

To claim this, I am signing this object:

ssadler

import Data.List (nub)
import Control.Monad
import System.Environment



main = getArgs >>= compressedFactors . read . head . (++["20"])

-- | Reduce the number of factors needed to create a number

ssadler

#!/usr/bin/bash

# This script makes the neccesary transactions to migrate
# coin between 2 assetchains on the same -ac_cc id

set -x
set -e

source=TXSCL
target=TXSCL000

ssadler

import sys
import subprocess
import json


# create an output with some funds to send across chain
# komodo-cli -ac_name=TXSCL sendtoaddress $inputaddress 2

inputaddress = "RFw7byY4xZpZCrtkMk3nFuuG1NTs9rSGgQ"
amount = 1.9

ssadler

Output amount is now a string

BigchainDB transactions may have multiple inputs and outputs, and each output has an amount, which is the integral number of the asset being transferred. In prior versions of BigchainDB, the amount was encoded as a number, which on the face of it is the obvious way to encode an integer. However, as usual the devil is in the details; JSON, the encoding of choice for BigchainDB transactions, encodes all numbers including integers as floating point. This isn't a problem for the majority of circumstances where numbers are small, however in some environments and for some use cases*, the number may lose precision.

In order to safeguard against this, amounts are now encoded as strings, and it is recommended to use a decimal math library (such as big.js) when dealing with large numbers in Javascript. Additionally, numbers are capped at 9e18 to stay comfortably within the boundary of a 64 bit signed integer.

* Try this in the Chrome developer c

ssadler

Welcome to Ubuntu 16.04.2 LTS (GNU/Linux 4.4.0-1013-aws x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management:     https://landscape.canonical.com
 * Support:        https://ubuntu.com/advantage

  Get cloud support with Ubuntu Advantage Cloud Guest:
    http://www.ubuntu.com/business/services/cloud

0 packages can be updated.

ssadler

import sys

from bigchaindb.core import Bigchain
from bigchaindb.models import Transaction, Block
from bigchaindb.common.crypto import generate_key_pair
import time

test_size = int(sys.argv[1])

ssadler

I hereby authorise the spending of output #1 in the following transaction.
{
  "asset": {
    "id": "e7bf69060ec9c9f814f82455166717044dc8c42decb246144c6825faad59c219"
  },
  "id": "280a0ba9208298c6e3c76e4b6c3ea5d40bf28a03de4e4a7279ad0d1eb26fde32",
  "inputs": [
    {
      "fulfillment": null,
      "fulfills": {