Utility token for the Phalanx Foundation ecosystem on the TON blockchain.
Phalanx (PLX) is a TEP-74 standard Jetton with mintable, burnable, and transferable owner capabilities, plus an on-chain linear vesting contract for team allocation. Built with Acton and Tolk.
Phalanx Foundation is an open-source initiative building on-chain infrastructure for the open economy. We design an ecosystem of audited, modular, reusable building blocks — starting on TON — so that any project, builder, or community can deploy production-grade smart contracts without writing a single line of code from scratch. Our first product is the Phalanx Tokenization Toolkit: a launchpad of pre-tested Jetton, vesting, and governance contracts that turns weeks of engineering into a verifiable deployment in minutes. PLX is the connective tissue of this ecosystem — granting discounted access to premium services, voting rights over which primitives we build next, and a share of network revenue for stakers.
The first product shipping from Phalanx Foundation is the Tokenization Toolkit — a self-service launchpad where any TON project can deploy a Jetton with on-chain vesting, optional multisig admin, and configurable governance hooks in minutes rather than months. Today, projects launching on TON typically fork unmaintained reference code, modify it without a formal review, deploy by hand, and hope nothing breaks. Phalanx removes this risk by providing one audited, battle-tested foundation that anyone can use, with transparent deployment costs and verifiable on-chain results. PLX integrates naturally: customers paying with PLX receive a 50% discount on deployment fees, a portion of collected fees is permanently burned to reduce circulating PLX supply, and PLX stakers earn a share of network revenue. This is utility driven by real demand from real builders — not speculation.
Beyond the launchpad, our roadmap covers a governance module that lets PLX holders vote on which new contract templates to build, a developer SDK for embedding PLX into third-party TON applications, and — once revenue, traction, and ecosystem maturity justify it — expansion to additional chains where the same primitives are needed.
| Field | Value |
|---|---|
| Name | Phalanx |
| Symbol | PLX |
| Decimals | 9 |
| Total Supply | 1,000,000,000 PLX (1 billion, fixed) |
| Standard | TEP-74 Jetton + TEP-89 metadata |
| Blockchain | TON (Basechain, workchain 0) |
| % | Allocation | Purpose |
|---|---|---|
| 40% | 400M PLX | Liquidity Provision (DEX) |
| 25% | 250M PLX | Treasury |
| 20% | 200M PLX | Community Rewards & Airdrops |
| 10% | 100M PLX | Team (vested 6 months linear, on-chain) |
| 5% | 50M PLX | Marketing & Partnerships |
After the initial distribution and a 24–48 hour observation window, the minter admin will be permanently dropped via an irreversible on-chain transaction, locking total supply at 1B PLX forever — no party (including Phalanx Foundation itself) will be able to mint additional PLX.
See docs/TOKENOMICS.md for full details. Mainnet is live — see docs/MAINNET-DEPLOYMENT-RECORD.md.
Three continuous deflationary forces will compress circulating PLX over time:
- Quarterly buyback-and-burn: a portion of launchpad revenue is used to buy PLX from the open market and permanently burn it.
- Direct fee burn: PLX paid for premium services can be burned at the contract level rather than recycled.
- Staking lock-up: PLX staked for governance and revenue share is removed from circulation while locked.
As the TON ecosystem grows and our launchpad customer base expands, demand for PLX increases while supply contracts. The team allocation (10%) is locked in the on-chain TeamVesting contract that releases tokens linearly over 180 days from launch — meaning the team cannot sell tokens during the first six months of trading, regardless of any party's intent.
The entire codebase is open-source under the MIT license, with 60+ automated tests covering minter operations, per-holder wallet behavior, vesting schedules, governance transitions, and bounce-message handling on edge cases. Continuous integration runs on every commit and pull request, and the full test suite must pass before code can land on master. Each contract is built deterministically and source-verified on Tonviewer immediately after deployment.
A formal third-party audit by a reputable firm is scheduled for Q1 2027 — funded by launchpad revenue rather than venture capital. This timing is intentional: our incentives as the audit's commissioner align with users and protocol stability rather than with investors who might pressure for a faster, lower-quality review. Until the formal audit lands, the security stance rests on three pillars anyone can verify today: comprehensive test coverage, public source code, and on-chain transparency for every state change.
The contract suite has also been internally reviewed against three known TON Jetton failure modes — bounce-message handling, gas-management dust accumulation, and cell-padding/serialization — with all findings documented and remediated in SECURITY.md. The mainnet release will ship with TeamVesting v1.1, which adds a bounce-rollback handler and an admin-only TON dust withdrawal.
The Treasury wallet holds 25% of supply (250,000,000 PLX) and its address is published in our transparency document. The Treasury allocation is exclusively for ecosystem development: seeding initial liquidity on TON DEXes (Ston.fi, DeDust), funding partner integrations, executing the buyback-and-burn program, and supporting open-source contributors. Every Treasury movement — every transfer, every burn, every payment — is verifiable on-chain in real time. Starting the quarter after mainnet launch, Phalanx Foundation will publish quarterly transparency reports detailing inflows, outflows, remaining balance, and rationale for each significant movement. The Treasury is not a black box; it is a public utility.
The 40% Liquidity Provision allocation (400,000,000 PLX) seeds initial pools on TON DEXes (Ston.fi, DeDust) at mainnet launch, paired against TON. The LP tokens minted by these pools will be locked in a publicly verifiable timelock contract for at least 12 months from the date of pool creation. The lock transaction will be published as a public commitment on launch day, and the timelock contract source will be open-sourced alongside the rest of the codebase. After the 12-month lock expires, any movement of LP tokens will require a multi-signature approval from the Foundation operators and will be announced publicly at least 7 days before execution. This protects against the "rug-pull" pattern that has caused real losses elsewhere on TON: the team cannot withdraw the seed liquidity in the first year, and cannot withdraw silently afterwards.
The 10% Team allocation (100,000,000 PLX) is locked in the on-chain TeamVesting contract for 180 days from mainnet launch, releasing linearly. The team cannot sell during the first six months of trading regardless of any party's intent.
Beyond these locks, three deflationary forces (described in Tokenomics) actively reduce circulating supply over time, and the minter admin will be permanently dropped 24–48 hours after distribution completes — locking total supply at 1B PLX forever.
Phalanx Foundation is built and operated by a small team of contributors operating under the pseudonymous-but-accountable model described in Governance. We do not publish individual identities, but every commit to this repository is cryptographically GPG-signed (see SECURITY.md) and every Treasury action is verifiable on-chain.
The project is self-funded. We have not taken venture capital, conducted any token sale or IDO, accepted private discounts, or sold tokens to insiders. There are no investor allocations. The roadmap is funded from contributor personal capital and from the Treasury allocation released only as the project ships. This is a deliberate choice: it means the team is not under pressure from outside backers to optimise for a quick token-price exit, and every PLX in circulation has been either honestly distributed (LP, treasury committed to ecosystem use) or earned (community rewards, customer payments). It also means we move at the pace that funding allows — and we commit to being honest about that pace in public transparency reports.
Phalanx Foundation operates under a pseudonymous-but-accountable model: contributors' personal identities are not published, but every on-chain action, every code commit, and every Treasury movement is permanently recorded and verifiable on TON and GitHub. This approach prioritizes the security and operational independence of contributors while still giving the community complete cryptographic verification of all Foundation activity.
Our explicit goal is to evolve into a fully community-owned foundation — where PLX holders directly govern protocol decisions through on-chain voting. This will start with non-binding signaling in Q3 2026, and progress to binding governance over Treasury allocations, contract templates, and protocol parameters in Q4 2026. The path to decentralization is itself open: every governance milestone will be a public commit, and the contracts that enable voting will be open-sourced and audited alongside the existing primitives.
- Q2 2026 — Mainnet launch of PLX, full open-source release of the contract library, and public documentation.
- Q3 2026 — Tokenization Toolkit MVP launches with three pilot deployments (free for early projects in exchange for testimonials and feedback), followed by initial integrations with TON wallets and DEX aggregators.
- Q4 2026 — Toolkit reaches general availability with native PLX payment integration; the initial governance module ships; and the developer SDK lets third-party applications embed PLX-powered functionality.
- Q1 2027 — Multi-chain feasibility study begins, evaluating Solana and EVM-compatible chains for expansion; the formal third-party security audit completes and is published.
- Q2 2027 and beyond — Cross-chain bridge integration, Foundation-funded grants for community-built primitives, and continuous expansion of the contract template library based on community votes.
Each milestone is a public commitment. If a milestone slips, the slip will be transparent and explained on GitHub.
| Contract / Role | Address |
|---|---|
| Jetton Minter | EQCbaUJqiRIuw5U-A_tUYTK4mdH0L37oFMvxeMEDGE5nVfLS |
| Team Vesting | EQCs-Y2wb83zqjCpRUMiZoKLUqhI3qd6tWWm4ycZBp6lsD5l |
| PaymentSplitter | EQBC3QoFri_IENOzVfMpHzs2Yr5_dJpzNsRNqT-XB173jSlv |
| Deployer / minter admin (temporary) | EQBfYLpqRNp4jVvffYb6uckcGVM2S5F1J8pq-pnFsN0anklj (UQBfYLpq…anhSm in Tonkeeper) |
Verify on Tonviewer mainnet. Full registry: docs/MAINNET-DEPLOYMENT-RECORD.md.
| Contract / Role | Address |
|---|---|
| Jetton Minter | kQAslxaUshiiqy5FrTbYHbBpjBgmcyTHB8vKKCemFKp508xV |
| Team Vesting | kQDNPoiPbKXwjt4i9SqtBmvbUlMgWz1jCR7M5Uwjj5fI8t1l |
| Active deployer / minter admin | kQBg9RFEVaQIh3xVonBxCnIb2Vw19y-rSD4uO1LR0eNH4zT2 (wallet plx-deployer-v2) |
| Retired deployer (security drill 2026-05-20) | kQB1GGwuoPV1vS2DjEg-weTPy5_HQU4ipqQm6KO05EyqEizN |
Verify on Tonviewer testnet. Detail: docs/TESTNET-DEPLOYMENT-RECORD.md.
plx-token/
├── contracts/ # Tolk source contracts
│ ├── JettonMinter.tolk # TEP-74 minter (mintable, owner-transferable, burnable via wallet)
│ ├── JettonWallet.tolk # TEP-74 per-holder wallet
│ ├── TeamVesting.tolk # Linear vesting (6 months) for team allocation; v1.1 bounce-safe
│ ├── messages.tolk # TLB message structs (opcodes)
│ ├── storage.tolk # Contract storage layouts
│ ├── errors.tolk # Error code enum
│ ├── fees-management.tolk # Gas/storage fee math
│ ├── jetton-utils.tolk # Wallet address derivation
│ └── sharding.tolk # Workchain & shard constants
├── tests/ # Native Tolk tests (60+ passing)
├── scripts/ # Deployment & operational scripts
├── wrappers/ # Auto-generated TS-style wrappers
├── metadata/ # On-chain metadata (logo, JSON)
├── docs/ # TOKENOMICS, DEPLOYMENT, etc.
└── Acton.toml # Project manifest
- Linux/macOS (or WSL2 on Windows)
curl,git- ~5 minutes
# Install Acton CLI
curl -LsSf https://github.com/ton-blockchain/acton/releases/latest/download/acton-installer.sh | sh
# Clone repo
git clone https://github.com/phalanx-foundation/plx-token.git
cd plx-tokenacton build # compile all contracts
acton test # run 60+ tests
acton check --fix # lint + auto-formatIf you are running this on a fresh clone, the wallet name
plx-deployerbelow is just a convention — pick whatever you like. On the live testnet currently maintained by Phalanx Foundation, the active operator wallet isplx-deployer-v2(post rotation drill); setPLX_DEPLOYER=plx-deployer-v2in your.envto make the ops scripts use it.
# Generate wallets (deployer + 5 distribution wallets)
for n in plx-deployer plx-treasury plx-lp plx-community plx-marketing plx-vesting-beneficiary; do
acton wallet new --local --name $n --version v5r1 --secure false
done
# Request testnet TON
acton wallet airdrop plx-deployer
acton wallet airdrop plx-deployer # one more time (limit 2/24h)
# Deploy minter + vesting + initial mint to all wallets
PLX_TREASURY=$(acton wallet list --json | jq -r '.wallets[] | select(.name=="plx-treasury") | .address') \
PLX_LP=$(acton wallet list --json | jq -r '.wallets[] | select(.name=="plx-lp") | .address') \
PLX_COMMUNITY=$(acton wallet list --json | jq -r '.wallets[] | select(.name=="plx-community") | .address') \
PLX_MARKETING=$(acton wallet list --json | jq -r '.wallets[] | select(.name=="plx-marketing") | .address') \
PLX_BENEFICIARY=$(acton wallet list --json | jq -r '.wallets[] | select(.name=="plx-vesting-beneficiary") | .address') \
PLX_VESTING_START=$(date +%s) \
acton script scripts/deploy-distribution.tolk --net testnetSee docs/DEPLOYMENT.md for the production checklist.
These contracts power Phalanx Toolkit — a browser-based Web3 crypto tokenization deployer on the TON/GRAM Blockchain. You do not need to fork this repo or run deploy scripts manually if you want a standard audited Jetton:
| Resource | URL |
|---|---|
| Create your own token (step-by-step guide) | https://plx.foundation/guides/create-token |
| Product home | https://plx.foundation |
| Pricing (testnet free tier) | https://plx.foundation/pricing |
| Pre-deploy checklist | https://plx.foundation/prepare |
| Reference Jetton (PLX) | https://plx.foundation/plx-token |
Workflow: sign in → pick tier → customize metadata → pay (or TestnetFree) → sign with Tonkeeper via TON Connect → receive Tonviewer link and audit packet.
For developers: this repository remains the source of truth for JettonMinter, JettonWallet, and TeamVesting. Phalanx Toolkit deploys the same audited Tolk bytecode via Acton. Clone and test here; deploy through the toolkit for production wizard, payments, and dashboard.
The TON ecosystem currently lacks a professional, audited tokenomics-as-a-service offering. Most projects launch tokens by forking unmaintained reference code, modifying it without formal review, and deploying by hand — a pattern that has caused real losses on other chains. Phalanx Foundation enters this gap as a first mover with three durable advantages: a contract library that is deeply tested on testnet (60+ tests passing), a foundation operating model designed for long-term independence rather than quick exits, and a token economy where revenue flows back to holders through buyback-and-burn instead of diluting them. These are not promises; they are mechanisms encoded in smart contracts that anyone can verify.
Phalanx Foundation does not promise any specific price, return, or yield, and does not market PLX as an investment product. Our commitments are to ship verifiable on-chain infrastructure, to maintain an open Treasury, and to permanently lock supply through public deployment events. The principal risks to understand are:
- Adoption risk — the Tokenization Toolkit must attract real customers, and like any service business, demand is not guaranteed.
- Ecosystem dependency — early growth correlates with the TON ecosystem itself; partly mitigated by our multi-chain expansion path on the roadmap.
- Regulatory variation — utility-token classification differs across jurisdictions, and participants must evaluate their local law independently. We do not provide legal or investment advice.
- Toolchain dependency — the contracts in this repository are written in Tolk and built with the Acton toolchain. Our test suite is comprehensive, but a previously unknown defect in Acton or in the underlying TON virtual machine could affect any contract built with that toolchain, including ours. We track upstream releases and will publish advisories if a defect is discovered.
- No insurance, no custody — Phalanx Foundation does not custody anyone's funds. Holders are responsible for their own wallet security, key management, and transaction verification. We will never ask anyone to send tokens or share private keys.
We disclose these not as a formality, but because the alignment between team and community begins with honesty. Anyone evaluating PLX should do so on the basis of verifiable code, disclosed tokenomics, and their own independent assessment of execution risk — not marketing claims.
- Tokenomics — distribution, vesting schedule, treasury policy
- Transparency — wallet registry, movement policy, audit trail
- Deployment — testnet/mainnet step-by-step
- Architecture — contract design and message flows
- Mainnet Checklist — production deploy gates
- Testnet Deployment Record — live testnet evidence
- Security Policy — vulnerability reporting and internal review log
- Terms of Service — pre-launch policy framework for the Toolkit
- Contributing — guide for outside contributors
The fastest way to evaluate Phalanx is to read the code yourself. Every contract lives at github.com/phalanx-foundation/plx-token. Every test reproduces on your machine in under five minutes. Every token movement verifies on Tonviewer. Open a pull request, send us patches, propose ideas. Phalanx is open by design — many shields, one formation, one direction.
- GitHub: github.com/phalanx-foundation/plx-token — code contributions via Pull Request. The Issues tab is intentionally disabled at this stage to prevent impersonation; we will re-enable it alongside a community moderation policy when the toolkit MVP launches.
- Email:
ops@plx.foundation(Cloudflare Email Routing — configure forwarding in dashboard). - Telegram channel: @phalanxfoundation — announcements, builder quest, listing updates.
- Telegram bot: @phalanxfoundationbot —
/start,/site,/swap,/price,/quest. - Discord: planned for Q3 2026 alongside the Tokenization Toolkit MVP.
We do not solicit DMs from unknown senders, and we will never ask you to send tokens or share private keys. Any communication claiming to be from Phalanx Foundation outside the channels above should be treated as a phishing attempt.
MIT — see LICENSE.