Building trust and transparency on MultiversX
Graz, Austria
Joined December 2021
- Tweets451
- Following399
- Followers76
- Likes432
Denzel.dastplatform retweeted
Are Builders or Cheerleaders Running the Show of your L1?
Here's a thought experiment on why the social layer of an L1 is ultimately what decides its fate.
So, what is the social layer of a blockchain?
The social layer of an L1 is the human and community aspect that interacts with and influences the technology.
The Social Layer of an L1 is the most important aspect of it's ecosystem because it shapes how the technology is used, developed, and perceived.
The composition of that social layer can be broadly divided into two:
Builders & Cheerleaders: Builders, who are the architects and developers actively contributing to the blockchain's infrastructure and applications, and Cheerleaders, primarily retail investors and enthusiasts who endorse and promote the platform.
Here's why the balance matters:
The balance between builders and cheerleaders ultimately decides the fate of a blockchain.
Is your blockchain builder-heavy?
Then it's very likely that the culture of that L1 would be more grounded and open to criticisms.
Why?
Because Builders are the innovators and implementers within the blockchain community. Their focus is on developing the blockchain's capabilities, solving technical challenges, and advancing the platform's utility.
In that case, their focus is usually on how to solve problems more than the external perception of their L1, although it matters to an extent.
It's very likely that a builder-heavy L1 would make more mistakes and missteps in the short term. However, in the long term, this will turn into a positive rather than a negative aspect, because the progress and learning will be much greater than the loss.
If the core builder layer adopts an "ivory tower culture," it could impede the expansion of the builder community.
This culture often upholds a traditional academic threshold and an "academics know best" attitude, prioritizing credentials over problem-solving skills.
Consequently, this approach becomes restrictive, hindering the inclusion and accommodation of individuals who may lack academic credentials but possess a strong problem-solving mindset.
Consider why most of the biggest consumer-focused companies are built by dropouts who care less about their academic credentials than the problems they are solving.
This is not so different in the L1 space, because an L1 is a consumer-focused platform rather than an academic brainchild.
But sometimes, it happens that the social layer of an L1 could be cheerleader-heavy.
A Cheerleader-heavy ecosystem might exhibit traits akin to a 'cult', with a diminished tolerance for criticism and a focus on narrative over substance.
Such communities may avoid confronting inherent problems, prioritizing their "Core L1 narrative" and token valuation over technical and strategic progress, just chanting the narratives the thin builder layer of that ecosystem try to propagate.
They perceive any criticism as a personal attack, because it attacks the narrative based on which their investment thesis is based on.
Anyway, coming back to the core discussion of cheerleaders vs builders.
Here's why Ethereum is a positive example of a healthy Builder vs Cheerleader balance:
Ethereum is without a doubt the most criticized and hated blockchain in the entire L1 space.
This blockchain has been attacked not just by the Bitcoin community from inception but also by other L1 communities (including myself), because ultimately those L1s were trying to solve the flaws of the base Ethereum architecture.
But there was never once Ethereum was accused of being a cult, because a builder-heavy social layer ensures that while market excitement is high, it doesn't overshadow the essential technical discussions and developments.
There has been more internal criticism of Ethereum's design choices and open acceptance of those problems than what comes from outside.
To make it simple to understand, Ethereum has more people like @sreeramkannan in its social layer than people like @TrustlessState , although media outlets like @bankless play a huge part in propagating the core Ethereum narrative.
So, this equilibrium has been key to Ethereum's endurance and status as a leading blockchain platform. That's why, after two cycles of the Ethereum killer narrative, we don't see any more Ethereum killers that can seriously challenge Ethereum's dominance.
Because at this point, Ethereum cannot be killed. Ethereum has by far the biggest builder-heavy social layer, and ultimately that's what matters the most.
Because whatever happens in the short term, if enough humans apply their minds to solve a problem, they will be able to solve it, and that's why the social layer of an L1 matters more than the tech of an L1.
Denzel.dastplatform retweeted
Introducing the evolution of @Boiler_Room_100!
Our mission: Learn. Grow. Invest. Together. #BR100
A community of dedicated individuals with a shared goal.
Curious why we did it? Check out this thread
🧵↓
P.S. 🔉 ON
Simple: would it not be very nice to know that caviareggs just branded another token? another scam in progress... @PepeVersX I am sure you would like to know that... I know it may not be perfect, but as an option, onchain KYC can prevent scams such as those from caviareggs.
Denzel.dastplatform retweeted
A guide for builders on how to properly create and manage inscriptions on #MultiversX
MultiversX is a decentralized blockchain network that aims to revolutionize the way we interact with payments, DeFi, NFTs, AI and everything in real world applications and virtual worlds.
Inscriptions could play a crucial role in the vision, enabling the creation of a rich and immersive virtual environment. Also, they are a powerful tool in order to keep track of history, ownership and existence of authenticated data.
Everything that is saved and authenticated on blockchain, cannot be rewritten further in the line. So history is going to be safe. Think about safely saving hashes/cryptographic proofs of videos, audios, books, any official documents. All of those are inscriptions, and are in such a form that complete data and verification is off-chain. Practically speaking inscriptions are already on the MultiversX chain, almost from day 1, we have serious companies using txData to save into history tracking (packets, data, certificates).
Specifications
▶️ Inscriptions are unique and indivisible tokens that can store arbitrary data, such as text, images, audio, or even other inscriptions. The storage should be kept on the txData, not saved into the trie, making it cheaper. Authentication of the data will come from indexers or a set of smart contracts.
▶️ Inscriptions have a unique identifier, such as a UUID or a random number. This prevents duplication and ensures the integrity of data. The validity of uniqueness is the job of an off-chain process, or at creation time, the job of a Smart Contract.
▶️ Inscriptions are stored on the blockchain, ensuring immutability and tamper-proof data storage. When a transaction containing an inscription is executed on the chain (it might mean only a transfer from user A to B), the complete transaction is saved in the blockchain database as executed transactions. And using the txHash which can be seen on the blockHeader, any off-chain application can identify the inscription. This ensures that the data stored in inscriptions cannot be altered or deleted.
▶️ Inscriptions can be owned by users, allowing them to control and manage the data within.
▶️Inscriptions can be transferred between users, enabling the sharing and exchange of data. The ownership history of inscriptions can be traced back to their creation, ensuring transparency and provenance. This is essential for tracking the ownership and usage of digital assets.
▶️Inscriptions can be used to create sophisticated applications, such as provenance tracking, ownership verification, and smart contracts. They can be programmed to interact with other smart contracts, enabling a wide range of functionalities. This allows for the creation of sophisticated applications that leverage the power of the blockchain. Or inscriptions can even act as self executing programs as well.
Let’s get more technical and go step by step:
1. Create an inscription:
a. Data Preparation: prepare the data that will be stored in the inscription. This can be of any type of data, such as text, images, audio, or even other inscriptions. The data should be in a format that can be serialized into a JSON object.
🔶Ensure the data is in a format that can be serialized into a JSON object.
🔶Sanitize the data to remove any malicious or invalid characters.
🔶Encode the data into a Base64 string for compatibility with the blockchain protocol.
b. Signature Generation: generate a cryptographic signature for the inscription data. This signature will be used to prove that the inscription was created by the owner. It is generated using the owner's private key.
🔶Obtain the owner's private key.
🔶Create a hash of the inscription data using a cryptographic hash function, such as SHA-256.
🔶Sign the hash using the owner's private key.
🔶Convert the signature into a Base64 string for storage on the blockchain.
🔶Save the hash as an inscription identifier.
c. Inscription Creation: submitting the inscription data, signature, and other metadata to the blockchain network. The blockchain will verify the signature and store the inscription on the ledger.
🔶Prepare a transaction object that includes the inscription data, signature, and other metadata.
🔶Sign the transaction object using the owner's private key.
🔶Broadcast the transaction to the MultiversX blockchain network.
Once the transaction is confirmed on the blockchain, the inscription is considered to be created and stored on the ledger. The creator becomes the owner of the inscription, and the inscription can be retrieved and transferred using the owner's public key.
2. Retrieval/validity of inscriptions:
Once an inscription is created, an off-chain application needs to be created, to monitor the history and track the validity of such information. (Later, we can speak about how this tracking could be created in a smart contract, but that will mean more development, right now it is better to go through the off-chain process as it is needed anyway).
Technically speaking, we need to use the indexer data, add a set of validity functions and create the new database of inscriptions. This database can always be recreated by running an import-db, meaning reprocessing the transactions as they were done by the validators. The order of transactions even right now can be taken from indexer/bigQuery implementations which are open sourced.
As the transaction is indexed, the new program has to check whether it is an inscription (is txData an JSON with the needed 3 fields: identifier, data and signature). Owner check: owner field is equal with sender, Signature check: inscription data signed by owner. Also check in case of new inscription creation (sender == destination), that identifier (which is hash of Data) is unique. Only if all these checks go through, then you can add the inscription to the inscriptions DataBase.
Furthermore, every inscription has to keep all its tracking data. From their original owner, to the latest owner. As in the end, this is the way a user can determine whether an InscriptionNFT is the bluechip/official one or not.
3. Transfers of an inscription:
The workings of the owner field.
🔹To ensure that inscriptions cannot be created or transferred by anyone other than the owner. The owner field is used to validate the signature of the inscription, which ensures that only the owner can create or transfer the inscription.
🔹To allow for the tracking of the ownership history of an inscription. The owner field is stored on the blockchain, which allows anyone to see who the current owner of an inscription is. This can be useful for applications such as provenance tracking and ownership verification.
🔹To facilitate the creation of smart contracts that manage inscriptions. Smart contracts can use the owner field to determine who is allowed to perform certain actions on an inscription, such as transferring ownership or modifying the data.
The ownership of an inscription is immutably stored on the blockchain, and the owner field is used to verify that the person transferring the inscription is actually the owner. It ensures that inscriptions can only be transferred to authorised recipients, and it provides a tamper-proof record of the ownership history of each inscription.
🔹In transaction 1, Alice creates an inscription and sets herself as the owner. The owner field is set to Alice's address, which is a unique identifier that can be used to verify her ownership of the inscription.
🔹In transaction 2, Alice transfers the inscription to Bob. The owner field is updated to Bob's address, which means that Bob is now the owner of the inscription. This change is recorded on the blockchain, and it is impossible to change the owner field without the owner's private key.
Example: examining the ownership history of a CryptoPunk inscription is a crucial step in verifying its authenticity. By tracing the provenance of the inscription back to its creation, you can determine whether it was originally created by the official creator of CryptoPunks. If the inscription can be traced back to the original creator, then there is a strong likelihood that it is authentic. However, if the inscription has been transferred or altered in any way, then its authenticity may be compromised.
Next, let’s discuss trading:
Escrow and Payment: An escrow service can be used to facilitate the transaction. The escrow service will hold the ordinal until the buyer has paid the agreed-upon price. Once the payment is received, the escrow service will transfer the ordinal to the buyer. Threshold signature over an account like this can boost its security.
Digital Marketplace:
One of the harder things on the smart contract is that you cannot actually verify the list of ownership of the inscriptions as it was saved only on txStorage which is not accessible by the SC. One developer could rely on oracles to validate every inscription deposit, but it can cost a lot of gas. Instead of this, the SC could accept simply all the inscriptions thrown at him, and in the frontend the user will see the reliable data.
1⃣ Inscription Listing:
- Inscription Description: The seller provides a detailed description of the inscription, including its identifier, type, data, and any relevant metadata. This helps potential buyers understand the inscription and its value.
- Desired Price: The seller sets a desired price for the inscription, which reflects their assessment of its value and the market conditions. This price is displayed on the marketplace for prospective buyers to see.
Marketplace saves data as Alice listed Inscription 0x123. If the same inscription is deposited by Bob as well, on withdrawal of inscriptions, each user can only withdraw the inscription they themselves deposited. In this case, on the marketplace both Inscriptions 0x123 can exist, one has the previous Owner of Bob and the other to Alice. So on withdrawal, Alice will withdraw only the inscriptions whose previous owner is herself.
2⃣ Bidding Process:
- Buyer's Interest: Interested buyers can view the listing and express their interest by submitting bids. The bid amount represents the maximum price they are willing to pay for the inscription.
- The Buyer will not only Bid for inscription 0x123, but for Inscription 0x123 whose previous owner is Bob
- Bidding Competition: The marketplace automatically compares bids and determines the highest bidder.
3⃣Smart Contract Execution:
- Bid Acceptance: Once the smart contract identifies the highest bidder, it triggers the acceptance of the bid. This initiates the process of transferring ownership of the inscription to the buyer.
- Payment Processing: The smart contract will facilitate the payment process.
- Inscription Transfer: Upon successful payment, the smart contract transfers ownership of the inscription to the buyer. This update is recorded on the blockchain, reflecting the change in ownership.
4⃣ Ownership Transfer and Completion:
- Updated Ownership Record: The blockchain maintains an updated record of the inscription's ownership, reflecting the transfer from the seller to the buyer.
- Transaction Confirmation: The buyer receives confirmation of the transaction, including the inscription identifier, the purchase price, and the updated ownership record.
Conclusion
Inscriptions are poised to reshape the digital landscape, and developers hold the key to unlocking this transformative potential. Inscriptions offer a groundbreaking solution for securely storing and transferring ownership of unique digital assets, opening up a world of possibilities for innovation and creativity.
From revolutionizing the art world to forging new economies within virtual worlds, inscriptions have the power to transform industries and enhance user experiences. Developers, you are at the forefront of this revolution, with the opportunity to build groundbreaking applications that redefine how we interact with the digital world.
The time is now to seize this opportunity. Embrace inscriptions, explore their boundless potential, and unleash your ingenuity to shape the future of the internet. Join the ranks of those who are pioneering this new era of digital innovation, and leave an indelible mark on the landscape of technology.
Denzel.dastplatform retweeted
We love tech and we go always the next level to optimise all the aspects of any component. Today, as requested by community, let's talk about our Virtual Machine (soon to have a better name than WASM).
Someone said that "MvX hasn't made any significantly big changes ... their VM is WASM". This is far from truth.
The #MultiversX VM is far from being simple and it has multiple layers, tens of features, all optimised out till the last bit. Technically speaking, when we talk about the Execution Environment we have at leat 3 different layers, and if we go top to bottom here they are:
1. SmartContract Processor and BlockchainHooks:
First, it prepares the VMInput data from the transaction, takes out the fee from the balance, executes all $ESDT transfers and then it calls the SmartContractExecutionHandler chosen from the smart contract address. Actually we have 2 running VMs on-chain, one with contract written in GO and executed in GO (systemVM) and another one for WASM contracts.
At the end of the execution, the SCProcessor makes a big set of sanity checks, computes the developer rewards, creates the needed cross shard messages, actually writes all the modifications which came as a VMOutput structure into the trie.
Innovations/features here: asynchronous calls V1 and V2, cross shard transaction processing and message preparations, all the $ESDT token system, actually guardian verifications, developer rewards. Handling all the revert in case of errors.
2. The virtual machine:
Is already at its 5th version/iteration. One of the first big implementations and improvements to be done here was writing and reading from the internal VM cache at the time of the execution, not writing intermediary steps to the blockchain state (this is still done in legacy L1s). There is no need to write intermediary changes, only the last one, and only if the execution is a success. STATELESSNESS.
Here we implemented the Ahead of Time compilation module, which reduced the contract preparation time by 80%. Almost a 5x improvement in execution speed. Meaning, any contract is compiled and kept in a serialized format on storage and cache, no need to do that at every execution. A changed serialization format have sped up the preparation phase by 60%.
Next in line was WarmInstances. Instead of deserializing and executing every time a contract, we just keep the WASM executable object as a warm instance and only cleaning up the memory of these objects. Even faster execution, at least a 2x improvement from the AoT version. This is the fastest way to execute in one thread complexe Smart Contracts.
This was for speed, but we never stopped there. Enshrining $ESDT transfers inside the Virtual Machine was a must in order to make it easier to develop complex financial apps. All modes of execution (sync/async) complemented with transfers handled directly by the VM. This eliminated all the re-entrancy issues.
And we could do more, implementing a set of common goods, libraries directly inside the VM as OPCODE: crypto (schnorr, BLSsingle, BLSMulti), bigInt/bigFloat/elliptic curve math, managed maps, managed objects, strings (it is called sentient storage on EVM - not yet implemented), secure randomness, asyncCalls V1 and V2.
Lastly the new backTransfer feature, which makes creating any SC on top of a DEX a simple few liners as all the transfers sent by the child contract to the parent is cached by the VM and given out to the parent. No need for interpretations of SC output, deserialization or complex code to understand the child SCs output.
<payments, results> = ExecuteOnDest(child). This makes DeFi legoblocks easier to create.
3. WASM engine: using Wasmer implementation for a compilation based WASM engine, running the SinglePass code. Improved communication with the blockchain, improved the ahead of time compilation module inside Wasmer, actually created the Warm Instance module and cleanup inside the Wasmer codebase. Extra security checks, disallowed a set of WASM OPCODES, interfacing of WASM objects directly to GO code. Integrated the Gas Module deep inside the Wasmer processing library.
Now, this is what we call Virtual Machine - or one could say Execution Environment. It is complex, built for speed and security of the users and developers. Every bit of optimisation matters. And not all features were described in this post.
This was and is unprecedented in the #blockchain world. No VM has this many features built in.
Next things here:
- asynchronous calls V3 - multilayer multi async calls
- enshrined zero knowledge verifier libraries as OPCODES
- more crypto libraries - seckpr1
- parallelisation of execution
- prefetching data before execution - ahead of time storage preparation
- linear type storage and managed objects.
And let's not forget:
Denzel.dastplatform retweeted
If @beniaminmincu announcing an countdown so big, it must be something extraordinary.
What do you think it is ? 🤔
Denzel.dastplatform retweeted
Explaining #MultiversX Guardians to my grandma
By bringing 2FA on-chain, Guardians are pushing your wallet's security to levels never seen before 🔐
Saying that it is secure is cool, explaining how is better, let’s delve into this feature 🧵
Plan of the thread:
1) What is a multisig?
2) 2FA, how does it work?
3) Guardians, a 2FA and on-chain variant of multisigs
4) Invisible guardian: when you are your own guardian
This type of informative content is becoming increasingly rare on Twitter, so before we dive deep here is how you can support it:
→ ♻️ Give me an RT if you find this content useful
→ ❤️ Follow @gfusee33 if you want more content like this in the future
→ 📘 Bookmark this content to read it later
Now let's get started!
1) What is a multisig
“Multisig” stands for “Multi-signature”. It is a term related to web3 stuff but the concept behind it exists since before the informatics era, so let’s take a real world example!
Suppose you want to buy this beautiful house, currently on sale:
After finding a deal with the owner and getting the needed funds for the transaction, you need to officially register the transaction in order to legally have the ownership on the house you bought. To do this you and the vendor should go to a notary, and you both have to write your signature on a sales agreement
The notary also has to sign this document, so you have three different signatures on it: the notary, the vendor and you. All those three signatures are required to execute the transaction, otherwise it’d be impossible for you to get the house
Signatures, transaction, don’t those terms remind you of something? Right! In the web3 we also need to sign transactions to execute operations. A “multisig” is a wallet that works the same way as the multiple signatures needed to buy a house. Except that with a multisig we don’t execute real estate transactions but blockchain ones!
Therefore a multisig is a wallet requiring the signature of multiple wallets to perform any action: tokens transfer, swapping, smart contract call, etc…
Here are two of the main use cases of a multisig:
a) Using a multisig as an individual
If you need to protect a lot of funds from multiple attack vectors you might have to pair up with people you trust (your friends, your family, etc…) to create a multisig where your signature alone cannot do anything
By doing so, if someone steals your private key, kidnaps you, etc… it won’t be able to steal your funds
b) Using a multisig as a company
A company need to protect its treasury, so what I said above for individuals also work for companies. But a company can also manage a dApp, smart contracts, etc… and thus having some admin keys. Those admin keys are critical, a hack of these likely mean the death of the company
Admin keys don’t need to be hacked to put the company in big troubles. If a malicious employee has an admin key it’d be able to create significant damage
Having a multisig as an admin key is a good shield against what I mentioned above, each company building a serious project should set up a multisig to protect itself
Note: I said that a multisig is a wallet, it is actually a smart contract which can do the same actions as a wallet. So considering multisig = wallet is totally fine
2) 2FA, how does it work?
Let’s temporarily forget the multisig and let’s talk about 2FA and MFA. MFA is the acronym for “Multi-Factor Authentication”, so 2FA is when the “Multi” amounts to 2
It’s impossible not to have heard of MFA in 2024, MFA is the mechanism that requires you to use more than your password to login to a service. When you log in to a website and it prompts you for a code received via SMS, it is MFA, especially 2FA since there are 2 factors: your password and the SMS code
Here are the four main factors used in 2FA in addition to your password:
- A code received by SMS. This method is super convenient and ensures that someone that steals your password also needs to read the received SMS to be able to hack your account. This factor is vulnerable to an attack called “sim-swapping” where the attacker calls your operator and requests a new SIM by impersonating you, making him able to read your SMS. This attack is easy to perform since the operator doesn’t know your voice
- A code received by email. This method is similar to a code received by SMS. This method is not really secure since if the attacker hacks your email it’s game over for you.
- A physical authenticator key which you should plug into your computer to log in to website. This is the most secure method but requires you to protect a physical key.
- The TOTP method. It is the acronym for "Time-based One-Time Password”. This method relies on an authenticator application that generates short-lived codes such as “Google Authenticator”, but any app works. This method is super secure because the attacker has to physically access the device where the app is installed to access your account
3) Guardians, a 2FA and on-chain variant of multisigs
You know what a multisig is, you know what 2FA and MFA are, so you know what a guardian is!
A guardian is a feature which turns your regular wallet into a multisig, but a multisig with some special rules:
- 2 wallets are required to sign a transaction: you and the guardian’s wallet
- The guardian’s wallet is a node. It ensures that the process remains decentralized. Anyone can become a guardian node
- The whole feature is native on the blockchain. This is not something added by a smart contract or anything else. It is a part of the consensus
- You are the only one able to initiate a transaction. So a malicious guardian node can’t do anything to your funds
- You can remove the guardian by waiting 28 days. It means 2 things: first, a malicious node can’t blackmail you. Second, if someone steals your private key, you have 28 days to save your funds, this is largely enough
But how does one instruct the guardian node to sign a transaction? There are a few methods possible but the most used is the 2FA with the authentication app! The process is as follows:
a) You create and sign a transaction
b) You ask your guardian node, “Hey! Can you sign this transaction?”
c) The guardian answers: “Sure, but prove you’re not an impostor, give me the code from your authentication app”
d) You give the code and the guardian signs the transaction
4) Invisible guardian: when you are your own guardian
I mentioned above that anyone can become a guardian node, so theoretically a friend of you can become your guardian! But what if you become your own guardian? Sounds weird? Let me explain!
The xPortal app features called “Invisible Guardian”. This feature will create, behind the scene, a new wallet which will act as a guardian node… your guardian node!
The private key of the invisible guardian’s wallet is stored and encrypted inside your smartphone, you’ll never have access to it. When you create a transaction from xPortal with your regular wallet, the invisible guardian automatically signs it
Is it secure? Absolutely! It means that only your smartphone can create and sign transactions; merely stealing your private key is no longer sufficient to access your assets. The attacker also needs access to your smartphone, which is far more difficult than merely stealing 24 words
I hope this thread brought you useful insights, if so please consider following me (@gfusee33) and throw me a RT and a like! ❤️
Denzel.dastplatform retweeted
MultiversX.
A blockchain which has always been the talk of the town, particularly as it doesn't take the traditional route to achieve its objectives.
medium.com/@xFoudres/multive…
But what objectives?
In this article, you'll find my own interpretation of the vision pursued by MultiversX and its development strategy. From the recent news and innovation brought by xDays down to most underlying things, where they may lead us in the future and where I'd like to see it go.
The article is very long, but don't be afraid, some parts can be skipped, especially if you're already familiar with the recent news.
Where I'd most like to draw your attention is to the part I, which deals with vision, the first and last sub-part of part 2 (2.a, 2.g), which deals with devellopement strategies, and finally the large parts 3 and 4, which deal with my expectations and the possible future devellopement that awaits us.
It should take you something like 15 minutes maximum if you're only interested in its parts. The large part of the article dealing with xDays in part 2, which although interesting, remains more secondary as it leaves the big picture to dwell on all the details of the recent announcements.
I hope that the article will serve as a reference and ressource for other content on what the year 2023 has brought us, and that it will stimulate reflection about the big picture of mass adoption.
Thanks for your read and sharings 🫶 ⚡
Denzel.dastplatform retweeted
mvx.tools is live✅🚀
It's an aggregator of all worthy MVX Tools that need to know when you navigate trough @MultiversX
Next steps:
- fix bugs🙃
- add more tools
- add remarkable "threads/posts"
- add NFT section
@PulsarTransfer send 0.2 EGLD to 100 reactions
Denzel.dastplatform retweeted
The entire #DAST team wishes you a Happy New Year! We all hope you will get massive profits , but most importantly, stay healthy. See you in the next year. 2️⃣0️⃣2️⃣4️⃣
#MultiversX
Denzel.dastplatform retweeted
Important announcement to the entire community:
[Spoiler]: Long thread / e-Compass is not stopping.
After a year 2023 rich in ups and downs, e-Compass has reached a crossroads where changes have become necessary for our personal good and the future of the project ...
Denzel.dastplatform retweeted
Merci. Je n'avais pas du tout suivi. Heureusement que tu l'as posté sur Twitter
Denzel.dastplatform retweeted
The new 'Hall of Fame member' has been chosen, and its @Glouffy67 .
The entire #DAST team congratulates him.
If you also want to become a 'Hall of Fame member' and win 0.5 #EGLD , follow us on Twitter and join our Discord server for more infomartion.
Denzel.dastplatform retweeted
Genesis NFT minters (first minters) receive lifetime rewards, regardless if they are still holding the NFT or not.
That means that the first minter wallet for any DAST NFT will receive passive income indefinitely, regardless if the wallet still holds the NFT or not. 🤯
Denzel.dastplatform retweeted
DAST is crafted to accommodate every idea within our ecosystem. It always begins with an idea 💡,
and the potential is limitless.
Join us and witness the growth from a seed to something extraordinary.🌴
Denzel.dastplatform retweeted
Did you know that #DAST will have 2 different NFT categories on @MultiversX ? 🧐
1. Platform NFT
2. #DAST Pruduct NFT
You want to find out what the difference is ?
Take a look at our Litepaper, on our official website
Denzel.dastplatform retweeted
To simplify DAST's essence:
When #DAST-Platform is successful on a large scale, the passive income also grows significantly.🆙️
Our entire design revolves around this concept, with the investor's well-being as our primary focus. We're all in this for their benefit.
