FIP27 / Contracts 2.5.x

• added support for FIP27 (nfts)
• updates for burnexpired
• fixed several structs that were in the wrong order for ABI encoding

Maintenance release

Primarily bug fixes for locked tokens:

• fixes off-by-one error on calculating when unlock periods happen
• changes lock time units to be more granular to facilitate tests
• prevents a condition where getting data from the locktockens table results in tens of thousands of API calls

Other fixes:

• Fixes an error in the fee value safety checks that would cause an error on transactions with a fee but a nil body.
• Fixes several issues with parsing BP.json, and adds support for the chains.json handling.

FIP-6/7/10/12 support and circulating supply calculations

New Features:

• Implements FIP-6, FIP-7, (completes) FIP-10, and FIP-12.
• Adds ability to calculate locked tokens for genesis locks, FIP6 locks, and BP reward locks.
• Adds ability to calculate full circulating supply.

Misc:

• adds examples for indexing blocks
• extends transaction timeout to 3 minutes
• disabled failing tests for transferring addresses

Bug fixes:

• API mutex was getting passed by value, updated fio.API to embed eos.API as a pointer.
• SetFee tests were using wrong key

Hotfix for fee integer issues

Warning: potential breaking changes to fees. Most of these are new, so should have minimal impact, but several signed integers in fees.go were incorrectly set as uint64 instead of int64.

• Add checks for integer conversion before signing a transaction, refuse to sign in the case of a possible overflow.
• Fix many fields in fee.go typed as uint instead of int.
• Fix wrong action on compute_fees call

Hotfix for v1.0.1 (FIP-10) release

Several issues in last release with setting fees, this fixes the following:

• binary marshaling error resulting in error about no authority for a mangled actor name
• Incorrect fees to endpoint mapping
• setting the multiplier was calling the wrong action

v1.0

• Removes functionality that required os-specific dependencies, specifically: HD keys and Keosd support which have been relocated to another repo
• imports eos-go as github.com/fioprotoco/fio-go/eos, this is to allow modifications to ecc and to ensure API stability
• many deprecated functions removed
• includes FIPs 1-4, 9, and partial support for 10

Going forward package, structures, and function naming should be stable, those requiring modifications will use deprecation and the creation of new items to ensure compatibility. In the run up to 1.0.0 there was much instability and that will not be the case going forward.

Initial v1 preview

Massive breaking changes from 0.9

• forks and imports into repo eos-go, renaming 'eos' namespace to 'fos' and 'ecc' to 'fecc'. This is for disambiguation because of fio-specific modifications to these (mostly ecc) libraries, and because 1.9 versions of eos-go changed all requests to use a context.
• removes some incompatible components: hd wallet support, keosd client, and both fioreq and fiotop executables. These were not cross-platform compatible and will be moved into external repositories.
• abandons state-history client. This was far from complete, and ambiguities in documentation along with incompatilbities in the older eos-go library made completing it time-consuming and unlikely to be of good quality. Look at something like chronicle as an alternative.
• covers FIP 1-4, and partial support for FIP 10.