Back to Blog

Lead in: Solana Simplified

July 1, 2024
2 min read

Solana is celebrated for its high speed, low costs, high transaction throughput, and low latency. These features have made it an increasingly favored platform among both users and developers for all kinds of decentralized applications.

To help both readers and developers navigate this robust ecosystem, BlockSec has specially curated the "Solana Simplified" series. This series covers the fundamental concepts of Solana, practical guides on analyzing Solana transactions, and comprehensive tutorials on writing Solana smart contracts. Let's dive in. 🙌

Breaking Down: A Comprehensive Overview

In the first part of this series, let's delve into the key concepts of the Solana network, including its operating mechanisms, account model, and transactions. This will lay the foundation for writing correct and efficient smart contracts on Solana.

In this article, we will guide you through writing a Solana program (i.e., a Solana smart contract) for posting and displaying articles. We will cover everything from environment setup and contract logic to program testing.

In the last part, we will introduce Solana's special token mechanism and teach users how to analyze a simple Solana transaction using Phalcon Explorer.


About BlockSec

BlockSec is a full-stack Web3 security service provider. The company is committed to enhancing security and usability for the emerging Web3 world in order to facilitate its mass adoption. To this end, BlockSec provides smart contract and EVM chain security auditing services, the Phalcon Security platform for security development and blocking threats proactively, the MetaSleuth platform for fund tracking and investigation, and MetaSuites extension for web3 builders surfing efficiently in the crypto world.

To date, the company has served over 1,000 clients such as Uniswap Foundation, Compound, Forta, and PancakeSwap, and received tens of millions of US dollars in two rounds of financing from preeminent investors, including Matrix Partners, Vitalbridge Capital, and Fenbushi Capital.

Website: https://blocksec.com/

Email: [email protected]

Twitter:https://twitter.com/BlockSecTeam

MetaSleuth: https://metasleuth.io/

MetaSuites: https://blocksec.com/metasuites

Sign up for the latest updates
From Incidents to Regulation: Why Crypto Institutions Need Blockchain Penetration Testing
Security Services

From Incidents to Regulation: Why Crypto Institutions Need Blockchain Penetration Testing

Exchanges, payment firms, custodians, and wallet providers now lose the most money beyond the smart contract—in signing, custody, keys, people, and supply chains. Code-level audit and transaction-level monitoring each leave a gap, and traditional penetration tests may miss crypto's signing and fund semantics. This article opens our blockchain penetration testing series with the two legs of the case for institutions in scope: where the risk actually comes from, and how NYDFS, DORA, VARA, SFC, and MAS treat adversarial testing across five jurisdictions.

What Is Blockchain Penetration Testing? Definitions and Boundaries
Security Services

What Is Blockchain Penetration Testing? Definitions and Boundaries

No widely accepted definition of blockchain penetration testing exists, and many proposed ones tangle it with audit, scanning, and bug bounty. This article sets out a working definition—an adversarial, hands-on assessment of a running system, under agreed scope and rules of engagement, that validates exploitable paths and control chains—and what web3 adds: a money-handling threat model whose defining composition gap is the off-chain-to-on-chain handoff. It then maps the five testable capabilities of that chain and routes nearby objectives to code audit, wallet security audit, web3 security testing, scanning, and bug bounty.

Rules of Engagement and Production Safety for Institutional Blockchain Penetration Testing
Security Services

Rules of Engagement and Production Safety for Institutional Blockchain Penetration Testing

A penetration test that touches signing, withdrawal, and ledger systems is prepared before it runs. This article follows the engagement lifecycle: turning a business decision into objective, scope, named owners, and authorized access; recording authority, permitted techniques, operating limits, prohibited activity, communications, and evidence handling in a Rules of Engagement document; and protecting live service with measurable stop criteria, monitoring, change coordination, and named pause authority. It closes with the remediation and retest that turn findings into validated controls.

Lead in: Solana Simplified