Tryte buffers are designed to be language-neutral, platform-neutral, extensible mechanism for serializing structured data to the tryte schema used by the IOTA tangle. You define your structure once in JSON and this module will take care of encoding all future object data to trytes and back again.

Find the encoding/decoding module here

# npm
npm install --save @iftt/tryte-buffer

# yarn
yarn add @iftt/tryte-buffer

// import package
// ES5
const TryteBuffer = require('@iftt/tryte-buffer').default;
// ES6
import TryteBuffer from '@iftt/tryte-buffer';

const tryteBuffer = new TryteBuffer(addressProtocol);

const testInput   = {
  name: 'Craig O\'Connor',
  aliases: ['CTO', 'Craiggles', 'Goober'],
  id: 76543456,
  phone: '+8005555555',
  phoneType: 'work'
};

let tryteEncoding = tryteBuffer.encode(testInput);
let decodedTrytes = tryteBuffer.decode(tryteEncoding);

// tryteEncoding === '99AAMBFDPCXCVCEAYBLAMBCDBDBDCDFD9C999FMBCCYB999RMBFDPCXCVCVC9DTCGD999LQBCDCDQCTCFD9EI9UWV999XPAVAXAXA9BWAZAZAYAVAYABB9A'
// decodedTrytes === { name: 'Craig O\'Connor', aliases: ['CTO', 'Craiggles', 'Goober'], id: 76543456, phone: '+8005555555', phoneType: 'work' }

if you need to debug use the string tryte-buffer

DEBUG=tryte-buffer node x

You define the protocol using JSON, as this is web friendly and supported by almost every common language in use today. The keys define the name of future input data:

{
  name: ...,
  age: ...,
  height: ...
}

The encoding/decoding options are as follows:

{
  type: 'string' | 'int8' | 'uint8' | 'int16' | 'uint16' | 'int32' | 'uint32' | 'bool' | 'date',
  repeat: boolean, // is the data an array?
  enum: array<string | number>, // an array of all possible values
  precision: 2 // this is only for number types and defines how many decimal places you want to keep
}

Although this is not an exhaustive list of possible use cases, it is relatable data.

let addressProtocol = {
  "name": {
    "type": "string"
  },
  "aliases": {
    "type": "string",
    "repeat": true
  },
  "id": {
    "type": "uint32"
  },
  "phone": {
    "type": "string"
  },
  "phoneType": {
    "type": "string",
    "enum": ["mobile", "work", "home"]
  }
}

type Protocol = {
  [string]: { // key
    [string]: any // key is type, enum, repeat, precision, or any user defined variables
  }
}

• tryteLimit: number; defaults to 2187. If you specify 0 then there is no limit
• overTryteLimit: boolean;
• lastEncodingSize: number;
• protocol: Protocol;
• [string]: { ['encode' | 'decode']: function }; the keys with encoding and decoding prepared from the protocol

• input: an object containing the same keys and values as described by the protocol submitted on instantiation
• output: encoded trytes

• trytes: a string of encoded trytes
• output: a decoded object with the same keys and values as submitted by the protocol buffer

Copyright 2019 Copyright (c) 2004-2010 by Internet Systems Consortium, Inc. ("ISC") Copyright (c) 1995-2003 by Internet Software Consortium

Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.

THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.