https://medium.com/@Grey_Mate
https://medium.com/@Grey_Mate
Subscribe to Grey_Mate
Subscribe to Grey_Mate
Share Dialog
Share Dialog
Grey_MateThe HoustonSwap Weekly: Technical Deep Dive into Concentrated Liquidity vs Traditional AMM Models (P…
In part 1, we will explore Concentrated Liquidity Market Maker and Traditional AMM models in detail, looking into liquidity provision, token swap and fee generation & ROI. Welcome back to the second installment of our HoustonSwap Weekly series! Since we briefly introduced the core concepts of the Concentrated Liquidity Market Maker model last week, we want to dive deeper into the mechanism and practical applications of the Concentrated Liquidity Market Maker model, and explain how it differs ...
Grey_MateBuild a Sui NFT Mint dApp in Under 10 Minutes with the EthosConnect API, Step by Step (React, TypeSc…
With “$24.9 billion worth of NFTs sold in 2021, compared to just $94.9 million the year before” (Reuters) it’s fair to say that NFTs are here to stay. For developers, this is great news, because it opens up opportunities to build and monetize NFT-related services. Yet across the NFT landscape, devs encounter many pitfalls: insecure smart contract languages, expensive fees to mint or transfer NFTs, slow networks, and steep learning curves, to name a few. In this walkthrough, we’ll bootstrap th...
Grey_MateEarn Passive Income from Your Old Computer!
Learn how to turn your old computer into a server for the Decentralized Cloud and earn passive income.With the pace of advancement of technology, we are constantly upgrading and have old computers left around gathering dust. By factory resetting and installing Ubuntu server, you can then cluster and sell the computing power of your old computers as a Decentralized Cloud Provider on a network like Akash. Decentralized Cloud Provider Cost: Electricity and bandwidth Benefit: Passive income This ...
Grey_MateThe HoustonSwap Weekly: Technical Deep Dive into Concentrated Liquidity vs Traditional AMM Models (P…
In part 1, we will explore Concentrated Liquidity Market Maker and Traditional AMM models in detail, looking into liquidity provision, token swap and fee generation & ROI. Welcome back to the second installment of our HoustonSwap Weekly series! Since we briefly introduced the core concepts of the Concentrated Liquidity Market Maker model last week, we want to dive deeper into the mechanism and practical applications of the Concentrated Liquidity Market Maker model, and explain how it differs ...
Grey_MateBuild a Sui NFT Mint dApp in Under 10 Minutes with the EthosConnect API, Step by Step (React, TypeSc…
With “$24.9 billion worth of NFTs sold in 2021, compared to just $94.9 million the year before” (Reuters) it’s fair to say that NFTs are here to stay. For developers, this is great news, because it opens up opportunities to build and monetize NFT-related services. Yet across the NFT landscape, devs encounter many pitfalls: insecure smart contract languages, expensive fees to mint or transfer NFTs, slow networks, and steep learning curves, to name a few. In this walkthrough, we’ll bootstrap th...
Grey_MateEarn Passive Income from Your Old Computer!
Learn how to turn your old computer into a server for the Decentralized Cloud and earn passive income.With the pace of advancement of technology, we are constantly upgrading and have old computers left around gathering dust. By factory resetting and installing Ubuntu server, you can then cluster and sell the computing power of your old computers as a Decentralized Cloud Provider on a network like Akash. Decentralized Cloud Provider Cost: Electricity and bandwidth Benefit: Passive income This ...
<100 subscribers
<100 subscribers
Sui Full nodes validate blockchain activities, including transactions, checkpoints, and epoch changes. Each Full node stores and services the queries for the blockchain state and history.
This role enables validators to focus on servicing and processing transactions. When a validator commits a new set of transactions (or a block of transactions), the validator pushes that block to all connected Full nodes that then service the queries from clients.
Sui Full nodes:
Track and verify the state of the blockchain, independently and locally.
Serve read requests from clients.
Sui Full nodes sync with validators to receive new transactions on the network.
A transaction requires a few round trips to 2f+1 validators to form a transaction certificate (TxCert).
This synchronization process includes:
Following 2f+1 validators and listening for newly committed transactions.
Making sure that 2f+1 validators recognize the transaction and that it reaches finality.
Executing the transaction locally and updating the local DB.
This synchronization process requires listening to at a minimum 2f+1 validators to ensure that a Full node has properly processed all new transactions. Sui will improve the synchronization process with the introduction of checkpoints and the ability to synchronize with other Full nodes.
A Sui Full node is essentially a read-only view of the network state. Unlike validator nodes, full nodes cannot sign transactions, although they can validate the integrity of the chain by re-executing transactions that were previously committed by a quorum of validators.
Today, a Sui Full node maintains the full history of the chain.
Validator nodes store only the latest transactions on the frontier of the object graph (for example, transactions with >0 unspent output objects).
Follow the instructions here to run your own Sui Full node.
Minimum hardware requirements for running a Sui Full node:
CPUs: 2
RAM: 8GB
Storage: 50GB
We recommend running Sui Full nodes on Linux. Sui supports the Ubuntu and Debian distributions. You can also run a Sui Full node on macOS.
Make sure to update Rust.
Use the following command to install additional Linux dependencies.
$ apt-get update \
&& apt-get install -y --no-install-recommends \
tzdata \
ca-certificates \
build-essential \
pkg-config \
cmake
You can configure a Sui Full node either using Docker or by building from source.
Follow the instructions in the Full node Docker README to run a Sui Full node using Docker, including resetting the environment.
Install the required Prerequisites.
Set up your fork of the Sui repository:
Go to the Sui repository on GitHub and click the Fork button in the top right-hand corner of the screen.
Clone your personal fork of the Sui repository to your local machine (ensure that you insert your GitHub username into the URL):
$ git clone https://github.com/<YOUR-GITHUB-USERNAME>/sui.git
cd into your sui repository:
Set up the Sui repository as a git remote:
$ git remote add upstream https://github.com/MystenLabs/sui
Sync your fork:
Check out the devnet branch:
$ git checkout --track upstream/devnet
Your Full node will now be serving the read endpoints of the Sui JSON-RPC API at: http://127.0.0.1:9000
Sui Explorer supports connections to custom RPC URLS and local networks. You can point the Explorer to your local Full node and see the transactions it syncs from the network. To make this change:
Open a browser and go to: https://explorer.devnet.sui.io/
Click the Devnet button in the top right-hand corner of Sui Explorer and select Local from the drop-down menu.
Close the Choose a Network menu to see the latest transactions.
Sui Explorer now uses your local Full node to explore the state of the chain.
Monitor your Full node using the instructions at Logging, Tracing, Metrics, and Observability.
Note the default metrics port is 9184. To change the port, edit your fullnode.yaml file.
Whenever Sui releases a new version, Devnet restarts as a new network with no data. You must update your Full node with each Sui release to ensure compatibility with the network.
Follow the instructions to reset the environment, namely by running the command:
$ docker-compose down --volumes
If you followed the instructions for Building from Source, update your Full node as follows:
Shut down your currently running Full node.
cd into your local Sui repository:
Remove the old on-disk database and 'genesis.blob' file:
$ rm -r suidb genesis.blob
Fetch the source from the latest release:
Reset your branch:
$ git checkout -B devnet --track upstream/devnet
Download the latest genesis state for Devnet as described above.
Update your fullnode.yaml configuration file if needed.
Restart your Sui Full node:
$ cargo run --release --bin sui-node -- --config-path fullnode.yaml
Your Full node starts on: http://127.0.0.1:9000
Today, a Full node relies only on synchronizing with 2f+1 validators in order to ensure it has seen all committed transactions. In the future, we expect Full nodes to fully participate in a peer-to-peer (p2p) environment where the load of disseminating new transactions can be shared with the whole network and not place the burden solely on the validators. We also expect future features, such as checkpoints, to enable improved performance of synchronizing the state of the chain from genesis.
Please see our privacy policy to learn how we handle information about our nodes.
Sui Full nodes validate blockchain activities, including transactions, checkpoints, and epoch changes. Each Full node stores and services the queries for the blockchain state and history.
This role enables validators to focus on servicing and processing transactions. When a validator commits a new set of transactions (or a block of transactions), the validator pushes that block to all connected Full nodes that then service the queries from clients.
Sui Full nodes:
Track and verify the state of the blockchain, independently and locally.
Serve read requests from clients.
Sui Full nodes sync with validators to receive new transactions on the network.
A transaction requires a few round trips to 2f+1 validators to form a transaction certificate (TxCert).
This synchronization process includes:
Following 2f+1 validators and listening for newly committed transactions.
Making sure that 2f+1 validators recognize the transaction and that it reaches finality.
Executing the transaction locally and updating the local DB.
This synchronization process requires listening to at a minimum 2f+1 validators to ensure that a Full node has properly processed all new transactions. Sui will improve the synchronization process with the introduction of checkpoints and the ability to synchronize with other Full nodes.
A Sui Full node is essentially a read-only view of the network state. Unlike validator nodes, full nodes cannot sign transactions, although they can validate the integrity of the chain by re-executing transactions that were previously committed by a quorum of validators.
Today, a Sui Full node maintains the full history of the chain.
Validator nodes store only the latest transactions on the frontier of the object graph (for example, transactions with >0 unspent output objects).
Follow the instructions here to run your own Sui Full node.
Minimum hardware requirements for running a Sui Full node:
CPUs: 2
RAM: 8GB
Storage: 50GB
We recommend running Sui Full nodes on Linux. Sui supports the Ubuntu and Debian distributions. You can also run a Sui Full node on macOS.
Make sure to update Rust.
Use the following command to install additional Linux dependencies.
$ apt-get update \
&& apt-get install -y --no-install-recommends \
tzdata \
ca-certificates \
build-essential \
pkg-config \
cmake
You can configure a Sui Full node either using Docker or by building from source.
Follow the instructions in the Full node Docker README to run a Sui Full node using Docker, including resetting the environment.
Install the required Prerequisites.
Set up your fork of the Sui repository:
Go to the Sui repository on GitHub and click the Fork button in the top right-hand corner of the screen.
Clone your personal fork of the Sui repository to your local machine (ensure that you insert your GitHub username into the URL):
$ git clone https://github.com/<YOUR-GITHUB-USERNAME>/sui.git
cd into your sui repository:
Set up the Sui repository as a git remote:
$ git remote add upstream https://github.com/MystenLabs/sui
Sync your fork:
Check out the devnet branch:
$ git checkout --track upstream/devnet
Your Full node will now be serving the read endpoints of the Sui JSON-RPC API at: http://127.0.0.1:9000
Sui Explorer supports connections to custom RPC URLS and local networks. You can point the Explorer to your local Full node and see the transactions it syncs from the network. To make this change:
Open a browser and go to: https://explorer.devnet.sui.io/
Click the Devnet button in the top right-hand corner of Sui Explorer and select Local from the drop-down menu.
Close the Choose a Network menu to see the latest transactions.
Sui Explorer now uses your local Full node to explore the state of the chain.
Monitor your Full node using the instructions at Logging, Tracing, Metrics, and Observability.
Note the default metrics port is 9184. To change the port, edit your fullnode.yaml file.
Whenever Sui releases a new version, Devnet restarts as a new network with no data. You must update your Full node with each Sui release to ensure compatibility with the network.
Follow the instructions to reset the environment, namely by running the command:
$ docker-compose down --volumes
If you followed the instructions for Building from Source, update your Full node as follows:
Shut down your currently running Full node.
cd into your local Sui repository:
Remove the old on-disk database and 'genesis.blob' file:
$ rm -r suidb genesis.blob
Fetch the source from the latest release:
Reset your branch:
$ git checkout -B devnet --track upstream/devnet
Download the latest genesis state for Devnet as described above.
Update your fullnode.yaml configuration file if needed.
Restart your Sui Full node:
$ cargo run --release --bin sui-node -- --config-path fullnode.yaml
Your Full node starts on: http://127.0.0.1:9000
Today, a Full node relies only on synchronizing with 2f+1 validators in order to ensure it has seen all committed transactions. In the future, we expect Full nodes to fully participate in a peer-to-peer (p2p) environment where the load of disseminating new transactions can be shared with the whole network and not place the burden solely on the validators. We also expect future features, such as checkpoints, to enable improved performance of synchronizing the state of the chain from genesis.
Please see our privacy policy to learn how we handle information about our nodes.
$ cp crates/sui-config/data/fullnode-template.yaml fullnode.yaml
Download the genesis state for Devnet:
$ curl -fLJO https://github.com/MystenLabs/sui-genesis/raw/main/devnet/genesis.blob
Optional: Skip this step to accept the default paths to resources. Edit the fullnode.yaml file to use custom paths.
Update the db-path field with the path to the Full node database.
db-path: "/db-files/sui-fullnode"
Update the genesis-file-location with the path to genesis.blob.
genesis:
genesis-file-location: "/sui-fullnode/genesis.blob"
Start your Sui Full node:
$ cargo run --release --bin sui-node -- --config-path fullnode.yaml
Optional: Publish / subscribe to notifications using JSON-RPC via websocket.
$ cp crates/sui-config/data/fullnode-template.yaml fullnode.yaml
Download the genesis state for Devnet:
$ curl -fLJO https://github.com/MystenLabs/sui-genesis/raw/main/devnet/genesis.blob
Optional: Skip this step to accept the default paths to resources. Edit the fullnode.yaml file to use custom paths.
Update the db-path field with the path to the Full node database.
db-path: "/db-files/sui-fullnode"
Update the genesis-file-location with the path to genesis.blob.
genesis:
genesis-file-location: "/sui-fullnode/genesis.blob"
Start your Sui Full node:
$ cargo run --release --bin sui-node -- --config-path fullnode.yaml
Optional: Publish / subscribe to notifications using JSON-RPC via websocket.
No activity yet