Skip to content

@Emyrk Emyrk released this Nov 5, 2019

A new tag was needed to trigger the automatical build in the ci pipeline

This release marks an upgrade to the api set for interacting with pegnet transactions. The new apis can be found in the wiki here: https://github.com/pegnet/pegnetd/wiki/API. A large change in this update is how transactions are presented to the user. A transaction on pegnet can be either a:

  • burn from FCT -> pFCT
  • coinbase from mining rewards
  • transfer from an asset changing ownership (person A -> person B)
  • conversion from a change in asset, PEG -> pUSD

Every transaction is considered to be included inside of a batch. This is because Pegnet allows users to combine multiple transactions into a single entry. For consistency, if a hash is provided in the form of 64 hex characters, it can contain 0 or more transactions. It could be a factoid txid, a mining opr, or an entryhash. To provide a pegnet txid to a specific transaction, the index of the transaction in the batch must also be provided in the format of [TxIndex]-[Txhash].

E.g: 0-839809fd4f16200c97b1e53c6775c0efd55746db3c285461149adac3572694b3 is the first transaction associated with the given hash. If the batch contains more than 1 tx, you can use the prefix to report the txid of the single tx in the batch: 1-83980..., 2-83980.... There is no rule on the padding of the prefix. If a fixed length is needed for display purposes, leading 0s are accepted: 001-83980...

This change required a large update to the pegnet database, so a full resync is required. The pegnet node will automatically create a new database when using the latest codebase. No action is required to trigger this resync.

API Endpoints added:

  • get-transactions : queries for all transactions related to a hash, address, or height
  • get-transaction-status : Details if a transaction is executed, pending, or rejected.

API Endpoints changed:

  • get-transaction : The params for this have changed
  • get-transaction-entry : This api endpoint was dropped

CLI Commands Updqated/Added:

  • `pegnetd get txs <entryhash | factoid txid | entryhash>
  • pegnetd get tx <pegnet txid>
  • pegnetd burn <FA-source> <FCT amount> : The FCT -> pFCT command has been added to pegnetd
Assets 5

@Emyrk Emyrk released this Nov 5, 2019 · 2 commits to master since this release

This release marks an upgrade to the api set for interacting with pegnet transactions. The new apis can be found in the wiki here: https://github.com/pegnet/pegnetd/wiki/API. A large change in this update is how transactions are presented to the user. A transaction on pegnet can be either a:

  • burn from FCT -> pFCT
  • coinbase from mining rewards
  • transfer from an asset changing ownership (person A -> person B)
  • conversion from a change in asset, PEG -> pUSD

Every transaction is considered to be included inside of a batch. This is because Pegnet allows users to combine multiple transactions into a single entry. For consistency, if a hash is provided in the form of 64 hex characters, it can contain 0 or more transactions. It could be a factoid txid, a mining opr, or an entryhash. To provide a pegnet txid to a specific transaction, the index of the transaction in the batch must also be provided in the format of [TxIndex]-[Txhash].

E.g: 0-839809fd4f16200c97b1e53c6775c0efd55746db3c285461149adac3572694b3 is the first transaction associated with the given hash. If the batch contains more than 1 tx, you can use the prefix to report the txid of the single tx in the batch: 1-83980..., 2-83980.... There is no rule on the padding of the prefix. If a fixed length is needed for display purposes, leading 0s are accepted: 001-83980...

This change required a large update to the pegnet database, so a full resync is required. The pegnet node will automatically create a new database when using the latest codebase. No action is required to trigger this resync.

API Endpoints added:

  • get-transactions : queries for all transactions related to a hash, address, or height
  • get-transaction-status : Details if a transaction is executed, pending, or rejected.

API Endpoints changed:

  • get-transaction : The params for this have changed
  • get-transaction-entry : This api endpoint was dropped

CLI Commands Updqated/Added:

  • `pegnetd get txs <entryhash | factoid txid | entryhash>
  • pegnetd get tx <pegnet txid>
  • pegnetd burn <FA-source> <FCT amount> : The FCT -> pFCT command has been added to pegnetd
Assets 2
Nov 5, 2019
Merge pull request #75 from pegnet/develop
remove chmod, don't have permission

@Emyrk Emyrk released this Oct 11, 2019

This release activates PEG conversions at height 214287, roughly Oct 14, 2019 15:00 UTC. The equation to determine the price of PEG is total market cap of all assets / supply of PEG.

Sum(Each Asset Supply at height n-1 * Each Asset price at height n)
-------------------------------------------------------------
		PEG Supply at height n-1

Please update pegnetd by that date. You will have to resync pegnetd when using this version. We enforces a new sync incase any users update after the activation height. We want to ensure all users are using the correct balances.

ChangeLog:

  • Added PEG conversions
  • The daemon will create a default config file if you do not have one
  • Miner api changes to remove hyphens from field names
Assets 5

@Emyrk Emyrk released this Oct 8, 2019 · 62 commits to master since this release

This is a patch to correct syncing transactions that have duplicate addresses in both the inputs and the outputs. The sql db was using the entryhash + address as a primary key as an indexing tool for retrieving user's addresses. The secondary purpose was to know if an entryhash was already submitted.

The unique filter would not work if a user set themselves in the input and output. This patch handles this case. You will need this patch to sync on mainnet.

There is no change to any transactions on mainnet, all validation rules are the same. This was a client side bug, and does not affect the blockchain.

Assets 5

@Emyrk Emyrk released this Oct 4, 2019 · 72 commits to master since this release

pegnetd is a lightweight daemon + cli tool to interact with the pegnet chain and conduct transactions/conversions of pegnet assets. The daemon will need to be run against a live factomd instance to sync.

For all cli interactions dealing with private keys, factom-walletd acts as the private key store. So all inputs to transactions + conversions will need to be imported into a walletd instance that the cli has access too.

Please refer to https://github.com/pegnet/pegnetd#configuration for configuration instructions. All pegnetd cli tools can be found from pegnetd help

Transactions and conversions will go live around October 7, 2019 at 15 UTC (block height 213237). Currently all assets with a 0 rate will not be allowed to convert. This means PEG cannot be converted until miners decide to place a value for PEG.

Assets 5
You can’t perform that action at this time.