Skip to main content

LSAN Token

note

LSAN is currently used primarily for access management. You can mitigate the use of LSAN tokens by engaging the network directly through the Streamr SDK.

The LSAN token, an ERC20 token exclusively developed for use with the Log Store AlphaNet, plays a pivotal role in ensuring secure and efficient data transactions on the network. Its primary function is facilitating seamless integration with live Streamr data streams and Arweave storage while providing permissioned access to Node Operators, and helping us cultivate data that improves decisions for our final production tokenomics. This token is indeed the heart of the Log Store AlphaNet, powering users' ability to store and retrieve data on the network.

Acquiring LSAN Tokens

Participants can acquire LSAN tokens by depositing MATIC into the Log Store AlphaNet ERC20 Smart Contract. The number of LSAN tokens minted is calculated automatically based on the network's storage costs - whereby 1 LSAN = 1 wei_per_byte * multplier. The multiplier gives the development team the ability to incorporate a fee buffer that may be required to compensate additional network services beyond storage, such as use of oracles. This dynamic pricing model ensures that the participants compensate the network accurately for storage of data to the underlying decentralized storage network.

Learn how to mint LSAN with our CLI →

Transacting with LSAN Tokens

While the LSAN tokens can be transferred to other addresses, a robust whitelist/blacklist system is in place to manage permissions. During the lifecycle of AlphaNet, we’ve enabled a manner to add or remove addresses from the whitelist, which contains addresses permitted to send tokens to the blacklisted addresses. Similarly, the blacklist is a registry of addresses that can only receive tokens from the whitelisted addresses. This precautionary measure ensures that the LSAN tokens are used in accordance with the intended rules and constraints of the Log Store AlphaNet.

The only address that is intended to be blacklisted is the Log Store Network’s LogStoreNodeManager.sol Smart Contract, which manages incentives within the Broker layer of the network. This means that in order to participate as a Broker Node on the Log Store Network during the Alpha, the Node address must be granted permission.

Usher Labs, the team behind the Log Store, will begin granting access permission to Node Operators once the Network gathers enough utility and feedback to be considered stable and escalated to the BetaNet phase.