Skip to content

Cezanne v1.1.1
Compare
Choose a tag to compare
@a-ok123 a-ok123 released this 29 Jul 21:33
· 208 commits to master since this release
v1.1.1
315a959

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 <...>
Assets 5
Loading