Skip to content

Releases: pastelnetwork/pastel

Monnet - v1.2.0-beta1

12 Jan 00:19
Compare
Choose a tag to compare
Monnet - v1.2.0-beta1 Pre-release
Pre-release

What's Changed

  • [PSL-367] Implement offer/accept/transfer for action tickets by @akobrin1 in #159
  • [PSL-413] SuperNode should have registered Pastel ID by @akobrin1 in #160
  • [PSL-435] Update comments for ticket structures in cNode by @akobrin1 in #161
  • [PSL-433] Write API on pasteld to handle score update by @akobrin1 in #162
  • [PSL-450] Use MN's collateral outpoint to find MN Pastel ID by @akobrin1 in #163
  • [PSL-454] Update boost version to 1.80 by @akobrin1 in #164
  • [PSL-471] Accept outpoint index numeric parameter in "pose-ban-score" RPC API by @akobrin1 in #165
  • [PSL-474] Enable pose-ban-score API only in masternode mode by @akobrin1 in #166
  • [PSL-478] cNode crashes on invalid RPC command parameter type by @akobrin1 in #167
  • [PSL-488] update docs by @mateeullahmalik in #168

Full Changelog: v1.1.3...v1.2.0-beta1

v1.1.5

08 Dec 17:00
386fef6
Compare
Choose a tag to compare
v1.1.5 Pre-release
Pre-release

What's Changed

  • [PSL-367] Implement offer/accept/transfer for action tickets by @akobrin1 in #159
  • [PSL-413] SuperNode should have registered Pastel ID by @akobrin1 in #160
  • [PSL-435] Update comments for ticket structures in cNode by @akobrin1 in #161
  • [PSL-433] Write API on pasteld to handle score update by @akobrin1 in #162
  • [PSL-450] Use MN's collateral outpoint to find MN Pastel ID by @akobrin1 in #163
  • [PSL-454] Update boost version to 1.80 by @akobrin1 in #164
  • [PSL-471] Accept outpoint index numeric parameter in "pose-ban-score" RPC API by @akobrin1 in #165
  • [PSL-474] Enable pose-ban-score API only in masternode mode by @akobrin1 in #166

Full Changelog: v1.1.3...v1.1.5-beta

Cezanne v1.1.3 Release

21 Sep 19:58
b7c3bb4
Compare
Choose a tag to compare

What's Changed

  • [PSL-407] Sapling transactions are treated as invalid, causing peer banning and stalled sync by @akobrin1 in #158

Full Changelog: v1.1.2...v1.1.3

Cezanne v1.1.2 Release

09 Sep 18:18
afac6a6
Compare
Choose a tag to compare

version string is "v1.1.2-afac6a66f"

Cezanne - v1.1.2 beta

30 Aug 00:41
603fd69
Compare
Choose a tag to compare
Cezanne - v1.1.2 beta Pre-release
Pre-release

What's Changed

  • fix for "register id/mnid" funding address by @akobrin1 in #142
  • [PSL-392] Use pasteld alerting system to facilitate upgrade to new version by @akobrin1 in #143
  • [PSL-394] raise protocol version to 170009 by @akobrin1 in #144

Full Changelog: v1.1.1...v1.1.2-beta9

Cezanne v1.1.1

29 Jul 21:33
Compare
Choose a tag to compare

Full Changelog: v1.1.0...v1.1.1

This is a stable release suitable for use on Mainnet.

This upgrade includes:

  • Improvements to NFT Minting and Collections
  • Support for NFT Transfers, Trades, and Auctions
  • Interchain account identification via PastelIDs
  • Cross-chain network access via Web3 APIs
  • Dramatic upgrades to Sense (our near-duplicate NFT detection protocol)
  • Enhancements to Cascade (our distributed NFT storage protocol)
  • User-friendly utility services via PastelUp
  • Improvements to network optimization and security
  • Added extra validation for SuperNode payment transaction.

NOTE: Upgrade instructions for various client types are listed below.

1. WalletNode: Update pre-Murata WalletNode to Cezanne Walletnode

  1. Download pastelup to existing Wallet host
  2. Next, stop the current node
    • pastelup stop node
  3. Install Pastel Walletnode
    • pastelup install walletnode -r latest -n mainnet -f
  4. Now, you are ready to start the WalletNode
    • pastelup start walletnode

2. SuperNode: Update pre-Murata SuperNode to Cezanne SuperNode

NOTE: SuperNode Update assumes that SuperNode is established via a COLD/HOT mode set-up where:

  • COLD node has:
    • pastel node (pasteld and pastel-cli) set as simple node (not as masternode),
    • wallet with collateral transaction for SN(s) that ran on HOT node(s)
    • masternode.conf for SN(s) that ran on HOT node(s)
  • HOT node has:
    • pastel node (pasteld and pastel-cli) running as masternode
  • LOCAL host - the user's computer used for performing upgrade, this CAN be the COLD node
  1. Download pastelup to both COLD and HOT node (and LOCAL host if it is different from COLD node)
  2. If LOCAL host is NOT COLD node, copy masternode.conf from COLD node to LOCAL host
    • scp cold_host:~/.pastel/masternode.conf .
  3. Open masternode.conf and find MN-NAME, COLLATERAL-TX-ID, COLLATERAL-TX-IND and MN-PRIV-KEY for node that will be upgraded
    {
        "MN-NAME": {
            "mnAddress": "<MN-IP-ADDRESS>:9933",
            "mnPrivKey": "<MN-PRIV-KEY>",
            "txid": "<COLLATERAL-TX-ID>",
            "outIndex": "<COLLATERAL-TX-IND>",
            "extAddress": "<MN-IP-ADDRESS>:4444",
            "extCfg": "",
            "extKey": "<PASTELID>"
        }
    }     
  4. Stop HOT node
    • from HOT node itself
      • pastelup stop node
    • OR from LOCAL host
      • pastelup stop node remote -ssh-ip <...> --ssh-user <...> --ssh-key <...>
  5. Install Pastel Supernode
    • from HOT node itself
      • pastelup install supernode -r latest -n mainnet -f
    • OR from LOCAL host
      • pastelup install supernode -r latest -n mainnet -f -ssh-ip <...> --ssh-user <...> --ssh-key <...>
  6. Initialize supernode, this step is only needed to create new version of masternode.conf on HOT node and to create new version of PastelID (PastelID in Cezanne has new field)
    • from HOT node itself
      • pastelup init supernode --name MN-NAME --new --txid=COLLATERAL-TX-ID --ind=COLLATERAL-TX-IND --pkey=MN-PRIV-KEY --passphrase=<passhrase for new PastelID> --skip-collateral-validation
    • OR from LOCAL host
      • pastelup init supernode remote --name MN-NAME --new --txid=COLLATERAL-TX-ID --ind=COLLATERAL-TX-IND --pkey=MN-PRIV-KEY --passphrase=<passhrase for new PastelID> --skip-collateral-validation -ssh-ip <...> --ssh-user <...> --ssh-key <...>
    • in both cases MN-NAME, COLLATERAL-TX-ID, COLLATERAL-TX-IND and MN-PRIV-KEY are values acquired from masternode.conf in step 2
    • Each of these commands might take a long time and might fail and the end, if it fails, re-run it adding flag --noReindex
  7. If init was successful there will pasteld process running on the HOT node
    • from HOT node
      • $ ps afx | grep pasteld | grep -v grep
          ... /home/user/pastel/pasteld --datadir=/home/user/.pastel --externalip=111.222.333.444 --txindex=1 --masternode --masternodeprivkey=<....>
  8. Update masternode.conf on COLD node with new masternode.conf created on the updated HOT node, it will look similar to this
    {
        "MN-NAME": {
            "mnAddress": "<MN-IP-ADDRESS>:9933",
            "mnPrivKey": "<MN-PRIV-KEY>",
            "txid": "<COLLATERAL-TX-ID>",
            "outIndex": "<COLLATERAL-TX-IND>",
            "extAddress": "<MN-IP-ADDRESS>:4444",
            "extP2P": "<MN-IP-ADDRESS>:4445",
            "extCfg": "",
            "extKey": "<NEW-PASTELID>"
        }
    }     
  9. Re-start pasteld on COLD node (this is required to pickup updates in masternode.conf)
    • from COLD node
      • pastelup stop node OR ./pastel/pastel-cli stop
      • ./pastel/pasteld --externalip=<external IP of the host> --reindex --txindex=1
  10. Re-enable MN
  • from COLD node
    • ./pastel/pastel-cli masternode start-alias MN-NAME
  1. Stop executables on the HOT node
  • from HOT node itself
    • pastelup stop supernode
  • OR from LOCAL host
    • pastelup stop supernode remote -ssh-ip <...> --ssh-user <...> --ssh-key <...>
  1. Set supernode's executables as systemd services
    • from HOT node itself
      • pastelup update install-service --solution supernode
  2. Start supernode
  • from HOT node itself
    • pastelup start supernode
  • OR from LOCAL host
    • pastelup start supernode -ssh-ip <...> --ssh-user <...> --ssh-key <...>

Cezanne - v1.1.0.1

20 May 02:35
Compare
Choose a tag to compare

This is a stable release suitable for use on Testnet.

Changes

  • Improvements to NFT Functionality (Minting, Collections, Transfers, Trades)
  • Support of user information and persistent identities via PastelID
  • Release of Web3 Open-APIs for action tickets
  • Sense improvements to dd-service, fingerprints, and rareness scores
  • Cascade improvements to RaptorQ chunk creation and distribution
  • Kademlia improvements to authentication and peer connections
  • Release of Pastel-Up utility services
  • Security improvements

Cezanne beta 2

23 Mar 22:04
11ea4d9
Compare
Choose a tag to compare
Cezanne beta 2 Pre-release
Pre-release

What's Changed

Full Changelog: v1.1-beta.1...v1.1-beta.2

Pastel Improvement Proposal #1 (PIP-1): Improvement to SuperNode (MN) voting logic

08 Mar 15:32
Compare
Choose a tag to compare

Summary

  • Added extra validation for SuperNode payment transaction.
  • This check is activated in Mainnet at blockHeight 228700.
  • Before the change, the transaction was considered valid if there were less than 6 votes. After the change, the transaction is checked for payment regardless of the payee vote count.
  • Payees are also ordered by vote count in descending order and the payment check is performed first on the payee with max vote count.
  • Regular transactions with no votes are considered valid.

To upgrade:

1. Download new executables into your root or user directory: pasteld and pastel-cli

wget https://github.com/pastelnetwork/pastel/releases/download/v1.0.2/pasteld-linux-amd64

wget https://github.com/pastelnetwork/pastel/releases/download/v1.0.2/pastel-cli-linux-amd64

1b. Rename the new executables to match existing configuration. For example, pastel-cli and pasteld as:

mv pastel-cli-linux-amd64 pastel-cli & mv pasteld-linux-amd64 pasteld

2. Next, stop the current pastel Node (tip: make sure you are in the active Pastel executables directory)

./pastel-cli stop

3. Backup your current executables mv <current-pasteld-exec> <backup-pasteld-exec> & <current-pastelcli-exec> <backup-pastelcli-exec>

For example: mv pasteld pasteld-1.0.0 & mv pastel-cli pastel-cli-1.0.0

4. Before you start the new node, you must reconfigure your data directory files.

First, return to your home and move the existing data directory to a backup:

mv ~/.pastel ~/.<back-up-name-of-data-directory>

Then, create a new data directory:

mkdir ~/.pastel

Lastly, copy the existing files from the back-up directory to the new directory:

cp ~/.<back-up-name-of-data-directory>/wallet.dat ~/.pastel
cp ~/.<back-up-name-of-data-directory>/pastel.conf ~/.pastel

(OPTIONAL: COPY THE MASTERNODE.CONF IF RECONFIGURING THE COLD NODE ON A HOT/COLD SUPERNODE SETUP) cp ~/.<back-up-name-of-data-directory>/masternode.conf ~/.pastel

5. Now, return to the directory containing the various executables and select the correct permission scripts

Set the correct permissions on shell scripts:

chmod 755 *.sh

You may also need to set correct permissions on executables:

chmod 755 pasteld
chmod 755 pastel-cli

6. Now, you are ready to restart the node:

If you are running a standard Node, run: ./start-node.sh

If you are running a SuperNode

  • On Hot Node, run: ./start-mn.sh
  • On Cold Node, run ./start-node.sh

Cezanne beta 1

02 Mar 00:38
359eb96
Compare
Choose a tag to compare
Cezanne beta 1 Pre-release
Pre-release

What's Changed

Full Changelog: v1.1-alpha.2...v1.1-beta.1