v1.3-rc2

Releasenotes Threefold chain v1.3-rc2

This release on itself was never released as production-ready. This is the second part of v1.3_rc1.

Summary

• adds frontend explorer support for authcoin transactions.
  • shows if an address is authorized or not.
  • supports (Tx v176) and (Tx v177) transactions.

v1.3-rc1

Releasenotes

This release on itself was never released as production-ready.

Summary

• adds blocking accounts to support transition to another blockchain platform.
  • The auth coin transfer extension provides the ability to ensure only authorized addresses can receive/send coins. Only the condition authorized to do so is able to define which addresses are authorized and which aren't. The condition that defines who is authorized to do so can also only changed by the one(s) owning the current condition authorized to do this and the address authorization.
  • In this tfchain implementation an address is by default authorized.
  • it introduces 2 new Transaction Types in the tfchain network to support this feature:
    • Auth Address Update Transaction (Tx v176);
    • Auth Condition Update Transaction (Tx v177);

Full documentation of this extension can be found here: https://github.com/threefoldtech/rivine/tree/master/extensions/authcointx

v1.2.1

Releasenotes

If you apply this update directly from a release older then v1.2.0,
then please also take into account the changes that were already released with version v1.2.0.

You can find the release notes for v1.2.0 at: /doc/release_notes/v1.2.md.

Summary

• support extension data for the unlockhash filter in transactionpool;
• fix typos in- and improve atomic swap documentation;
• show atomic swap contract addresses in explorer hash.js v2 fulfillment display;
• no longer panic in client CLI when daemon cannot be reached;
• contact daemon from client CLI in a lazy manner, allowing basic functionality
  such as --help and the version command without a daemon being available;

v1.2.0

Releasenotes

This release also includes changes made, but not prior released in a production-ready release,
for the v1.1.2-rc1 candidate release.

Summary

• bug fixes and improvements to web explorer, some of the more important improvements:
  • render arbitrary data decoded only if possible;
  • show timestamps on transaction pages;
  • fix all known runtime errors;
• introduce the TFT <-> TFT20 (an ERC20 ThreefoldFoundation-backed token on Ethereum) bridge (testnet only):
  • it comes with a bridged CLI that forms a bridge between networks, allowing transfers of funds from one network to the other;
  • it introduces 3 new Transaction Types in the tfchain network to support this feature:
    • one to send funds from TFT to TFT20 (Tx v208);
    • one to receive TFT funds from the TFT network (v209);
    • one to register a TFT withdrawal address, required in order to be able to send TFT20 funds (back) to the TFT network) (v210);
  • Tx v208 and v210 can be fully validated by any tfchain daemon;
  • v209 is by default only validated in light-mode. Only a tfchain daemon also connected to the linked Ethereum network can validate the ERC20-backed CoinCreation fully (a recommendation for all block creators);
  • includes a command-line client for the bridge;
• introduce support for 3Bot records (testnet only):
  • you can read more about 3Bot in the context of tfchain at /doc/3bot.md;
  • it comes with 3 new Transaction Types in the tfchain network to support this feature:
    • one to register a 3Bot, creating the record and getting a unique integral ID assigned as a result (Tx v144);
    • one to update the record of an existing 3Bot (Tx v145);
    • one to transfer the ownership of one or multiple names from one existing 3Bot to another (Tx v146);
• improved tfchaind daemon:
  • support unencrypted (plain) wallets;
  • support verbose logging;
  • provide more information for hash lookups in explorers, avoiding the need to look up parent blocks;
  • allow for extensive runtime profiling when building using the profile Makefile targets;
• improve the TFT (testnet) faucet and also provide it with an API;
• some small corrections in documentation;
• update codebase and get it up to date with Rivine:
  • switch to the consensus plugin-based system, eliminating the need for the transactionDB
    (the persistent data of this DB is to be manually deleted by the user);
  • update all vendored dependencies (dep);
  • get codebase up to date with Rivine's new codebase;
  • move threebot code to extension internal package;
  • remove most internal erc20 logic and use the new rivine erc20 extension;
  • adapt and fix codebase where needed;
  • improve linting, formatting and testing;
  • integrate latest rivinecg faucet (closes #369);
  • improved logging during the consensus IBD phase;
  • ensure explorer frontend JS code is up to date with latest bug fixes and features (closes #368);
  • closes #363, closes #362, closes #354, closes #357, closes #351 (disabled for standard net) and also closes #350 (disabled for standard net);
  • remove deprecated data storage functionality from API and CLI;

Upgrade concerns

• Make sure to upgrade your full node, connected to the testnet ThreeFold Chain network, to v1.2.0 immediately, as your node(s) will no longer sync otherwise.
• Starting from block 385,000 v0 transactions are no longer accepted by consensus nodes on both the standard and testnet network;
• Miner fees were already required since a previous patch and are now enforced to be since block 300,000 on both the standard and testnet network;

v1.1.1

Release notes Threefold chain v1.1.1

Important for light clients

The explorer can now return unconfirmed transactions as well when an unlock address is queried. An additional unconfirmed boolean field has been added in the
json of the transactions returned. Since the client will likely not filter on this field yet, the client might think that the transaction is confirmed. This can
lead to problems with incorrect calculation of balances, duplicate outputs if the client already searched through the transactionpool, and possibly more. The logic
which retrieves the relevant transactions should be updated as soon as possible.

Summary

• Improved JumpScale client support:
  • Added support for coin creation and minter definition transactions
  • Improved the handeling of multisig outputs
  • Rework how the balance is shown
  • The client now starts with only a single address
  • Small bugfixes
• Unconfirmed transactions are now returned when looking up an unlock hash in the explorer
• Daemons can now try to broadcast transactions again should they remain in the pool for multiple blocks.
• Bugfixes and improvements