DEV Community: Tanya Prajapati

20 days into Solana and transactions finally make sense.

Tanya Prajapati — Mon, 15 Jun 2026 20:08:21 +0000

This is the summary of everything I have learned about transaction in Solana-

Transaction are not just messages or amount send. Transaction contains metadata,instructions, accounts and programs.

When a transaction is processed, a signature key is generated which is used to check details of the transaction in the solana explorer.

There are more than one account used in the transaction where the program account (owner account) is one of those accounts.

Signature key works like the confirmation that a transaction is processed but it does not control the success or failure of the transaction. However using the generated signature key, the transaction details can easliy be viewed on Solana Explorer.

The flow of a transaction in Solana is similar to the transaction in Stripe or Paypal (websites used for payments).

In Solana, the transaction does not waits in the mempool like in EVM blockchain
The transaction is broadcasted to the entire node using an RPC url when it is created. This transaction is then validated by the validators present in the network. Validators get paid when they validate a trnasaction, this is the reason why transaction fee is taken whenever their is any transaction.

Day-13 of learning Solana

Tanya Prajapati — Sun, 07 Jun 2026 15:27:43 +0000

So far, I have understood about -

The use of account and types of accounts used in Solana .
Difference in devnet, mainnet and testnet
How one can see details of any account present in Solana
What SOL and Lamports are.
About to read on-chain data in Solana
How account in Solana works similar to database in web2

Questions I have now -

What does on-chain data even mean and where does it live?
How much data at one transaction can be stored?
What is the logic behind transactions.
Why Proof of history is used as the consensus mechanism and why?
Is rent in Solana lesser as compare to gas fees in Ethereum and Polygon? If yes, then how and why?
How does the physical layer in Solana look like ?
Is the concept of bulk transaction used? If yes then how does it is handled?
Is the test done in devnet responds different than in testnet?
Can a wallet from other blockchain be used for transaction in Solana?
What is the best use case to use Solana?

Taking a day to explore these concepts so that I can answer these question in day 14 .

Identity in Web3

Tanya Prajapati — Sat, 30 May 2026 22:11:55 +0000

Unlike in case of Web2 ,Web3 enables self-soverign identity (SSI) model which allows users to control their digital identity. Users in web3 can decide what information to share and with whom using Cryptography and digital wallets.

Trustless Identity Claims:
In Web3 users use Verifiable Credentials(VCs) which allows them to prove claims with minimal disclosure of the data. These credentials are cryptographically signed by the governments, banks.They are like certificates in Web3.
It is used when the provenance is necessary.
Ex- User can use their VC to proof they are above 18 without revealing exact birthdate.
Zero-Knowledge Proofs (ZKPs) :
In web3 Zero-knowledge proofs are used to prove a claim without revealing the private data. Mathematical proofs are used to proof users identity without exposing the real data.
It is used when privacy and security of the data is non-negotiable.
Decentralized Identifiers(DIDs):
DIDs are globally unique identifiers. They can be used when the developers needs a unique identity which can be used in other platforms for recognition. DIDs are tamperproof.

In web3 , a user's identity does not rely on centralized platforms .