Purpose &
Vision
Bitsafe (BSF) is a Solana-based digital
currency ecosystem designed for real-world merchant payments and staking
rewards. The system connects three main participants — users, merchants,
and liquidity providers — through a transparent and auditable on-chain
structure. Its goal is to merge speed and scalability from Solana with long-term
sustainability through a dual-token model:
·
BSF (BitSafe Token)
– the primary utility token used for payments and staking.
·
sBSF (Staked BitSafe Token)
– a yield-bearing token representing staked BSF.
By building directly
on Solana, Bitsafe inherits sub-second confirmation times, near-zero
transaction costs, and a mature developer ecosystem.
Design Philosophy
The system was designed around five principles:
1.
Transparency
– every token movement is verifiable on-chain.
2.
Efficiency
– merchant payments must settle in under 1 second.
3.
Fair Yield
– staking rewards come directly from actual network use (not
inflation).
4.
Compliance-ready
– supports regulated gateways and on/off-ramps.
5.
Scalability
– modular code enables expansion to additional stablecoins or
sidechains.
The Dual-Phase
Model
Bitsafe’s lifecycle unfolds in two
coordinated phases:
·
Phase 1 – Infrastructure
& Growth
: staking, token distribution,
liquidity pools, and dApp infrastructure.
·
Phase 2 – Merchant Adoption
& Utility
: transition to a high-velocity
payment ecosystem where BSF is used for real purchases, loyalty programs, and
transaction rebates.
Key Metrics
·
Total supply: 1,000,000,000 BSF
·
Decimals: 9
·
Network: Solana (SPL standard)
·
Average transaction fee: <
$0.0001
·
Consensus: Proof-of-History
(PoH) + Delegated Proof-of-Stake (DPoS)
·
Staking ratio target: 50% of
circulating supply
The Bitsafe on-chain program is
built with the Solana Anchor framework, which provides a structured and
auditable way to define programs (smart-contracts) using the Rust language.
Every key function — such as staking, minting, or payments — is executed
through a deterministic Program Derived Address (PDA), guaranteeing
predictable authority and eliminating the need for private custodial keys.
The architecture follows a state-based
model in which a single global State
account defines parameters and
authorities, while derived token accounts handle liquidity and staking
balances. Each interaction is validated by Anchor’s security model, ensuring
the correct signer, program ID, and instruction order.
|
Account
|
Purpose
|
Notes
|
|
State (PDA)
|
Stores configuration
(admin, treasury, BSF mint, sBSF mint, vaults, policy cap, decimals, staking
shares).
|
Created once at program
initialization.
|
|
BSF Mint
|
The primary SPL token
mint for Bitsafe.
|
Controlled by the State
PDA.
|
|
sBSF Mint
|
Secondary mint
representing staked BSF shares.
|
Mint authority = State
PDA.
|
|
Staking Vault
|
Token Account owned by
the State PDA that holds users’ deposited BSF.
|
Non-custodial,
transparent on-chain.
|
|
Treasury
|
Wallet controlled by DAO
governance.
|
Receives network fees and
manages liquidity.
|
|
User Accounts (ATAs)
|
Standard associated token
accounts for BSF and sBSF.
|
Users always retain
custody of their staked assets.
|
·
Admin / State PDA:
the program’s root authority; can mint initial supply, initialize
state, and create metadata.
·
Treasury:
authorized to burn BSF tokens for supply control or deflationary
adjustments.
·
DAO Governance:
after activation, admin privileges transition to on-chain
vote-based control.
·
Policy Cap:
a maximum supply parameter preventing inflation above predefined
limits.
·
Signer Seeds: each mint/burn/transfer_checked call derives a PDA using [b"state", bsf_mint]
for
deterministic control.
All arithmetic
is checked (checked_add, checked_sub
) to avoid overflow, and all staking share computations are
proportional to the vault’s current balance to ensure fairness among stakers.
┌───────────────────────┐
│ User Wallets │
│ BSF / sBSF ATAs
│
└──────────┬────────────┘
│
▼
┌───────────────────────┐
│ Staking Vault │
│ (Owned by State PDA) │
└──────────┬────────────┘
│
▼
┌───────────────────────┐
│ State │
│ admin, treasury, │
│ policy_cap, shares │
└──────────┬────────────┘
│
▼
┌───────────────────────┐
│ Treasury / DAO │
│ Fee control & unlocks │
└───────────────────────┘
This design
provides auditable, non-custodial staking where no centralized wallet
ever holds user funds, and every balance can be independently verified
on-chain.
Each function in the Bitsafe on-chain program serves a specific
operational purpose. Together they form a complete life-cycle for BSF tokens —
from issuance, staking, and redemption, to controlled minting and metadata
creation. The code follows the Solana Anchor convention, where every function
has a well-defined context (list of accounts) and operates within strict
authority boundaries.
Purpose: To set up the program’s state for the first time. It defines all
key parameters and creates the necessary accounts — state, s_bsf_mint
, and the staking vault.
Process Summary:
Admin calls initialize()
and provides:
o
the treasury address,
o
BSF mint reference,
o
optional pre-mint amount (to
fund the treasury).
A new State PDA is created with seeds [b"state", bsf_mint]
.
The program records the admin, treasury, mints, and decimals.
If premint_amount > 0
, the function mints BSF directly to the treasury ATA using the
PDA as authority.
Why it matters:
Initialization defines every core address deterministically and
ensures there can only be one valid configuration per BSF mint — eliminating
the risk of duplicate state objects or rogue treasuries.
Purpose:
Allow users to deposit BSF tokens into the staking vault and
receive proportional sBSF tokens in return.
Process Summary:
User
transfers BSF → staking_vault
(checked transfer).
The
program calculates the number of shares to mint:
shares = (amount * current_shares) / total_assets
(If vault is empty, shares =
amount).
It
mints sBSF to the user’s associated token account.
Updates
the global staking_shares
counter.
Why it matters:
This mechanism ensures fairness and transparency — each user’s
share of the vault is proportional to their contribution, and all yield
distributions remain on-chain.
Purpose:
Redeem sBSF tokens for the corresponding amount of BSF from the
vault.
Process Summary:
1.
Burns sBSF from the user’s
account.
2.
Calculates redemption amount
based on total vault assets and outstanding shares.
3.
Transfers the computed BSF
amount from the vault to the user’s BSF account.
4.
Updates global staking_shares
.
Why it matters:
Guarantees that every staker can always reclaim their proportional
stake without dependence on external actors. All conversions are transparent
and auditable.
Purpose:
Allows the admin (or later DAO) to mint new BSF tokens, respecting
the policy cap set during initialization.
Process Summary:
1.
Verifies that admin == state.admin
.
2.
Ensures that total supply +
requested amount ≤ policy_cap
.
3.
Uses the PDA signer to mint the
tokens to a destination account.
Why it matters:
This enforces monetary discipline and prevents unauthorized
inflation of BSF supply.
Purpose:
Allows the treasury to burn BSF, reducing total supply — e.g., for
deflationary adjustments or to remove collected fees.
Process Summary:
1.
Verifies that caller == state.treasury
.
2.
Burns BSF from the treasury’s
account.
Why it matters:
Gives DAO-governed control of circulating supply, supporting
stability and long-term scarcity.
Purpose:
Placeholder for future yield distribution logic. In future
versions, this may collect transaction fees, staking rewards, or DAO-approved
distributions.
Process Summary:
Currently a no-op (does nothing) but exists to anchor the program
interface for upgrades.
Purpose:
Creates the on-chain metadata for the sBSF mint using Metaplex
Token Metadata v4, giving staked tokens a human-readable name, symbol, and
URI.
Process Summary:
1.
Uses Metaplex builder to call CreateMetadataAccountV3Builder
.
2.
Assigns the admin as update
authority.
3.
Sets metadata fields (name,
symbol, URI).
4.
Invokes the instruction using
the PDA signer.
Why it matters:
Ensures that sBSF tokens appear correctly in wallets and explorers,
and that metadata is controlled securely by the program’s authority.
┌──────────────┐
│
initialize() │
└──────┬───────┘
│ creates
▼
┌──────────────┐
│
stake() │───► Mints sBSF to
user
└──────┬───────┘
│ burns
▼
┌──────────────┐
│
unstake() │───► Returns BSF to
user
└──────┬───────┘
│ admin only
▼
┌──────────────┐
│
mint_bsf() │───► DAO-controlled
issuance
└──────┬───────┘
│
▼
┌──────────────┐
│
burn_bsf() │───► Supply reduction
└──────────────┘
The Bitsafe staking model is designed to be transparent,
yield-bearing, and fully aligned with actual network usage. Rather than
printing new tokens as inflation, BSF creates a circular reward economy where real
transaction volume drives staking rewards and treasury
sustainability.
Bitsafe uses two
related SPL tokens:
|
Token
|
Description
|
Role
|
|
BSF
|
Main payment &
staking token.
|
Used for
transactions, payments, and staking deposits.
|
|
sBSF
|
Staked representation
of BSF (1:1 backed).
|
Represents user’s
share of the staking vault. Redeemable for BSF anytime.
|
Conversion Logic:
·
When a user stakes BSF, they
receive sBSF according to their proportional vault share.
·
When they unstake, their sBSF
is burned and BSF is returned from the vault.
·
sBSF supply always equals total
outstanding staking shares.
This model is non-custodial,
and yields scale with network activity — not arbitrary emissions.
At the core of staking
lies the staking_shares value stored in the State
account. It represents the total
shares minted across all users. When a new user stakes, the program computes
their fair share as:
[ shares = ]
This ensures that:
·
Early stakers are not diluted.
·
Rewards distribute
proportionally.
·
Vault arithmetic remains stable
under all conditions.
All math uses checked
128-bit arithmetic to avoid overflow, and values are stored as 64-bit unsigned
integers (u64) for Solana compliance.
Unlike traditional staking
systems that inflate token supply, Bitsafe’s rewards originate from network
activity:
1% Transaction Fee
on every payment is distributed as:
·
0.5% → Treasury:
adds to liquidity, buybacks, and DAO-controlled reserves.
·
0.5% → Stakers: proportionally distributed to active stakers via harvest()
logic.
As merchant adoption grows,
the reward pool grows organically — ensuring long-term sustainability and
utility-linked yield.
Scenario:
Alice stakes 1,000 BSF when the vault holds 9,000 BSF and 9,000
shares total.
[ shares = (1000 * 9000) /
9000 = 1000]
After a week, transaction
fees generate 100 BSF in the vault. Total assets = 10,100 BSF, total shares =
10,000.
If Alice unstakes her 1,000
shares:
[ redeem = (1000 * 10100) /
10000 = 1010]
She receives 1,010 BSF —
effectively earning 1% yield from real payment activity.
┌──────────────┐
│ User A │
│
(1,000 BSF) │
└──────┬───────┘
│ stake()
▼
┌───────────────────┐
│ Staking Vault │
│
+1,000 BSF │
└──────┬────────────┘
│ mint sBSF
▼
┌──────────────┐
│ User A │
│
(1,000 sBSF) │
└──────┬───────┘
│ unstake()
▼
┌───────────────────┐
│ Vault sends BSF │
│ (with yield) │
└───────────────────┘
The Bitsafe (BSF) token economy is designed to evolve over time —
starting with a staking-driven liquidity phase and progressing toward broad
merchant usage. The supply and governance mechanisms ensure both early-stage
stability and long-term decentralization through DAO oversight.
|
Parameter
|
Value
|
Notes
|
|
Total Supply
|
1,000,000,000 BSF
|
Fixed maximum cap
|
|
Decimals
|
9
|
SPL standard
|
|
Initial Mint
(Phase 1)
|
500,000,000 BSF
|
Pre-mined to
Treasury
|
|
Locked DAO
Pool (Phase 2)
|
500,000,000 BSF
|
Released over 5
years
|
|
Transaction
Fee
|
1 %
|
50 % → Treasury,
50 % → Stakers
|
|
Blockchain
|
Solana
|
SPL Token
Standard
|
All minting and
burning operations are executed through PDAs with explicit caps defined in the
on-chain State
account. No off-chain authority can exceed the policy cap.
Objectives:
·
Establish staking pools,
exchanges, and core liquidity.
·
Maintain moderate free float
for price stability.
·
Incentivize ecosystem partners
and developers.
|
Allocation
|
% of Total
|
Tokens (M)
|
Purpose
|
|
Foundation
& Treasury
|
20
%
|
200
|
Liquidity,
reserves, buybacks
|
|
Development
& Infrastructure
|
10
%
|
100
|
Platform,
wallets, APIs
|
|
Marketing
& Community
|
8
%
|
80
|
Listings,
outreach
|
|
Research
& Innovation
|
5
%
|
50
|
Cross-chain
R&D
|
|
Core
Team & Advisors
|
10
%
|
100
|
36-month
vesting
|
|
Liquidity
Provision
|
6
%
|
60
|
CEX/DEX
pools
|
|
Ecosystem
Grants
|
4
%
|
40
|
3rd-party
integrations
|
|
Philanthropy
& Impact
|
2
%
|
20
|
Education,
inclusion
|
|
Public
+ Private Sales
|
27
%
|
270
|
Launch
and liquidity support
|
|
Reserve
/ Harvest Pool
|
8
%
|
80
|
Staking
rewards
|
Expected circulating supply:
150–250 M
BSF (15–25 %).
Objectives:
·
Expand circulation to 60–80 %
of total.
·
Use BSF for real merchant
payments and cashback.
·
Transition governance to DAO.
|
Allocation
|
% of Total
|
Tokens (M)
|
Purpose
|
|
Circulating Supply (Payments & Loyalty)
|
45 %
|
450
|
Transaction flow & merchant incentives
|
|
Treasury & Stability Fund
|
20 %
|
200
|
Market buffer, price stability
|
|
Merchant Rewards & Cashback Pool
|
10 %
|
100
|
Loyalty and cashback programs
|
|
Ecosystem Development
|
10 %
|
100
|
SDKs & compliance tools
|
|
Team & Advisors
|
10 %
|
100
|
Vesting linked to adoption
|
|
Charity & Community Growth
|
5 %
|
50
|
Financial education & inclusion
|
Target float:
600–800 M BSF in
circulation by 2030.
The
remaining 500 M BSF are locked under DAO control. Each year, new tokens can be
unlocked only when specific ecosystem metrics are achieved.
|
Year
|
Max
Unlock
|
Trigger
Condition
|
Destination
|
|
2026
|
100
M
|
≥
€10 M monthly volume or 100 k users
|
Treasury
/ Liquidity Support
|
|
2027
|
100
M
|
≥
€25 M volume or 250 k users
|
Cashback
& Rewards Pools
|
|
2028
|
100
M
|
≥
€50 M volume or 500 k users
|
Merchant
Reserve Expansion
|
|
2029
|
100
M
|
≥
€75 M volume or 750 k users
|
DAO
Stability Fund
|
|
2030
|
100
M
|
≥
€100 M volume or 1 M users
|
Full
Float Release
|
Each
unlock must be approved through a DAO vote and verified by an independent
oracle reporting on-chain transaction metrics.
2026 ─┬─ 100 M → Treasury Liquidity
2027 ─┬─ 100 M → Cashback & Rewards
2028 ─┬─ 100 M → Merchant Reserve
2029 ─┬─ 100 M → Stability Fund
2030 ─┬─ 100 M → Circulating Float
Total
DAO-locked supply released:
500 M BSF over five
years.
The long-term goal of Bitsafe (BSF) is to become a universal
merchant payment token — one that bridges crypto efficiency with real-world
usability while maintaining on-chain transparency. By Phase 2, BSF will
function not just as a staked asset but as an active payment medium that
rewards both merchants and consumers.
Each payment processed
through the Bitsafe network follows a standardized 1% fee distribution model.
Step-by-step flow:
Customer Purchase
o
A customer pays a merchant 100
BSF using a supported wallet or payment terminal.
Network Fee (1%)
o
The protocol automatically
deducts 1 BSF as a network fee.
Treasury & Stakers Split (0.5% + 0.5%)
o
0.5 BSF is routed to the
Treasury for liquidity, buybacks, and operations.
o
0.5 BSF is sent to the reward
vault to be distributed among active stakers.
Merchant Settlement (99%)
o
The merchant receives 99 BSF
instantly into their wallet.
End-of-Period Harvest
o
The harvest()
function aggregates all staker
rewards and distributes them proportionally.
┌──────────┐ 100 BSF Payment ┌────────────┐
│
Customer│ ─────────────────────────▶│
Merchant │
└──────────┘ └─────┬──────┘
│
▼
1% Fee
Split
│
┌──────────────┬─────────────────────┘
▼ ▼
┌──────────────┐ ┌──────────────┐
│
Treasury │ │
Stakers │
│
(0.5%) │
│ (0.5%) │
└──────────────┘ └──────────────┘
This automatic split
ensures sustainability (treasury funding) and fair yield (staker
rewards) without inflating supply.
Bitsafe’s merchant
network includes built-in incentives to promote adoption:
|
Mechanism
|
Description
|
|
Cashback Pool
|
Merchants receive
periodic cashback in BSF for transaction volume, drawn from DAO-approved
reserves.
|
|
Loyalty Rewards
|
Customers can earn
BSF-based points for repeated purchases.
|
|
Reduced Fees for
Staking Merchants
|
Merchants who stake
BSF directly may receive 0.75% fees instead of 1.00%.
|
|
Instant
Settlement
|
Solana’s sub-second
confirmation enables near-instant transfer and accounting.
|
The Bitsafe
ecosystem is built for easy integration:
·
Merchant APIs
for e-commerce and PoS systems.
·
SDKs
in TypeScript and Rust.
·
Payment Terminals
supporting QR and NFC payments.
·
Stablecoin Swap Layer
(future): automatic conversion between BSF and stable assets
(USDC/SPL).
Scenario:
·
A merchant processes 10,000 BSF
in sales per day.
·
1% network fees generate 100
BSF.
·
50 BSF goes to the Treasury.
·
50 BSF goes to the staker
reward pool.
If 50,000 merchants
process similar volume, the Treasury and staking pool collectively earn
millions of BSF annually — purely from organic activity, not inflation.
This creates a closed-loop
economy: usage drives value, value drives staking, and staking drives
network growth.
Bitsafe’s governance model ensures that no single entity can control
supply or treasury functions after the network matures. The design follows a progressive
decentralization path — starting with a controlled admin phase to secure
the launch, then transitioning into a full DAO (Decentralized Autonomous
Organization).
Phase 1 –
Controlled Launch (2025–2026) During the initial
phase, the admin address defined in the State
account manages upgrades, minting
(within the cap), and treasury setup. This ensures security and operational
control during early deployment.
Phase 2 – DAO
Activation (2026–2027)
Once the DAO contract is
launched, governance rights are gradually transferred:
·
Minting and burning permissions
move from admin → DAO PDA.
·
Treasury management becomes
proposal-based, requiring majority votes.
·
DAO oracles validate ecosystem
metrics (volume, users, liquidity) that unlock DAO-controlled token tranches.
Phase 3 – Full
Decentralization (2028 onward)
The admin account
becomes inactive. All major protocol parameters (fees, unlocks, reward ratios)
are governed by DAO proposals and on-chain voting.
Proposal Creation:
Any staker
holding ≥0.5 % of sBSF can submit a governance proposal.
Voting Period:
o
Duration: 7 days
o
Each sBSF token = 1 vote
o
Quorum: 20 % participation
minimum
Execution:
o
If a proposal passes, DAO
multisig or on-chain instruction executes the approved action automatically.
Transparency:
o
All votes and proposals are
recorded on-chain.
o
Treasury activity is public and
auditable.
Bitsafe is
built to meet future regulatory standards without compromising
decentralization.
|
Focus Area
|
Implementation
|
|
AML/KYC
Gateway
|
Off-chain
partner exchanges handle user onboarding; the on-chain layer remains
permissionless.
|
|
Auditability
|
Every
transaction, mint, and burn is visible on Solana explorer; supply and DAO
wallets are verifiable.
|
|
Non-custodial
Design
|
Users
always control their own BSF/sBSF; the protocol never holds private keys.
|
|
Upgradeable
Security
|
Anchor
framework allows controlled program upgrades through DAO vote until
governance lock.
|
This hybrid
structure lets regulated partners connect without compromising the open nature
of the blockchain.
The Treasury
acts as the network’s stabilization mechanism and operational reserve. Its
funds originate from the 1 % transaction fee and DAO unlocks. Usage categories
include:
·
Market liquidity provisioning
·
Buyback and burn operations
·
Developer grants
·
Merchant cashback funding
All treasury
transactions will eventually route through a multisig smart contract
governed by the DAO.
Admin Phase (2025–2026)
│
▼
DAO Activation
(2026–2027)
│
▼
Full DAO Control
(2028→)
This ensures a
clean and transparent transfer of power from founders to community governance —
a hallmark of sustainable Web3 ecosystems.
Bitsafe’s roadmap is structured to deliver sustainable ecosystem
growth through a series of technical, economic, and governance milestones.
Each phase is designed to strengthen both the technological base and the
token’s real-world utility.
Objective:
Build the core Solana program
and establish the staking ecosystem.
Key Milestones:
·
Deploy BSF and sBSF mints on
Solana mainnet.
·
Launch staking smart contract (bitsafe
program).
·
Initialize Treasury and DAO
state accounts.
·
Conduct first 500M BSF pre-mint
under policy cap.
·
Launch web staking interface
(Anchor + React dApp).
·
Begin first staking period with
test liquidity.
Outcomes:
Functional on-chain staking,
secure mint/burn mechanisms, and validator engagement.
Objective:
Increase liquidity,
visibility, and user participation.
Key Milestones:
·
First exchange listings (DEX +
CEX).
·
Expand staking rewards to 50k+
users.
·
Release SDK for Solana, React,
and TypeScript integrations.
·
Begin DAO proposal testing and
testnet voting.
·
Onboard first group of merchant
payment pilots.
·
Release Bitsafe Wallet with
staking and payment features.
Outcomes:
Greater accessibility for
users and early-stage merchants, groundwork for DAO activation.
Objective:
Transition from controlled
administration to decentralized governance.
Key Milestones:
·
Deploy DAO governance contract.
·
Transfer minting authority from
admin → DAO PDA.
·
First DAO vote on treasury fund
allocation.
·
Initiate first DAO-based unlock
(100M BSF if conditions met).
·
Integrate oracle metrics for
transaction volume and active users.
Outcomes:
Self-governing, community-led
network with transparent unlock criteria.
Objective:
Achieve large-scale merchant
adoption and real-world utility.
Key Milestones:
·
Deploy merchant SDK for PoS and
e-commerce systems.
·
Integrate with stablecoin swap
layer for volatility control.
·
Launch loyalty & cashback
modules funded by DAO unlocks.
·
Reach 100,000+ active merchants
and 1M+ users.
·
Implement dynamic fee model
(0.75–1.0 %) for stakers/merchants.
Outcomes:
Real BSF transaction volume;
fees drive yield instead of inflation.
Objective:
Establish Bitsafe as a
globally recognized payment and staking network.
Key Milestones:
·
Full DAO autonomy (no admin
privileges remaining).
·
Expand cross-chain integrations
via wrapped BSF (e.g., Ethereum, Tron).
·
Secure Tier-1 exchange
listings.
·
Formalize compliance
partnerships with regulated custodians.
·
Introduce merchant lending and
credit services.
Outcomes:
Bitsafe evolves into a
self-sustaining, DAO-governed ecosystem supporting global commerce and
decentralized finance.
2025 ─
Foundation ───────────────► Core Staking
Launch
2026 ─
Ecosystem ────────────────► Exchange
Listings / Wallets
2027 ─
Governance ───────────────► DAO
Activation
2028 ─
Adoption ─────────────────► Merchant
Payments / Cashback
2029–30 ─ Expansion ─────────────► Global Scaling / Compliance
This appendix provides key reference data and constants that define
the Bitsafe protocol implementation. All values are for the mainnet
deployment on Solana.
|
Parameter
|
Description
|
Value / Notes
|
|
Blockchain
|
Network where
BSF and sBSF reside
|
Solana Mainnet
|
|
Token
Standards
|
SPL (Solana
Program Library)
|
9 decimals
precision
|
|
Consensus
|
Proof of
History (PoH) + Delegated Proof of Stake (DPoS)
|
Average block
time ~400 ms
|
|
Average Fee
|
Per transaction
|
< $0.0001
equivalent
|
|
Validator
Count
|
Decentralization
metric
|
2,000+
|
|
Smart
Contract Framework
|
Rust + Anchor
|
Modular and
auditable
|
|
Metadata
Standard
|
Metaplex v4
(CreateMetadataAccountV3)
|
Used for
on-chain token identity
|
|
Supported
SDKs
|
TypeScript /
Web3.js / UMI / Anchor
|
dApp and API
development
|
|
Constant
|
Description
|
Example Value
|
|
Program ID
|
Bitsafe Solana
program identifier
|
9sNuk7RoqUcyzSPwjUZZTHc6pxxpn12rBuxXQoEWCtmy
|
|
Seed Prefixes
|
PDA derivation bases
|
"state", "s_bsf_mint"
|
|
Vault Token
|
Staking vault
holding user BSF
|
Owned by State PDA
|
|
Policy Cap
|
Maximum mintable
supply
|
1,000,000,000 BSF
|
|
Transaction Fee
|
Network fee per
payment
|
1% (0.5% Treasury,
0.5% Stakers)
|
|
Reward Function
|
harvest() (planned)
|
Redistributes usage
fees
|
|
Arithmetic Type
|
Safe Math
(checked_add / checked_sub)
|
Prevents overflow
|
|
Mint Authority
|
PDA derived from [b"state",
bsf_mint]
|
Immutable and
deterministic
|
|
Layer
|
Tool / Library
|
Role
|
|
Smart Contract
|
Rust + Anchor
|
On-chain logic
|
|
Token Metadata
|
Metaplex
|
Token identity and
display
|
|
Frontend
|
React + TypeScript
|
Staking dApp &
dashboard
|
|
API Layer
|
Solana Web3.js / UMI
|
Wallet and account
integration
|
|
Analytics
|
RPC Indexer +
Explorers
|
Real-time supply
tracking
|
|
Testing
|
Anchor CLI + Solana
Test Validator
|
Unit and integration
tests
|
Typical Solana
development commands for the Bitsafe program:
anchor build
anchor deploy --provider.cluster mainnet-beta
anchor run initialize --policy-cap 1000000000 --premint-amount 500000000
anchor run stake --amount 1000
Bitsafe (BSF) combines the
scalability of Solana with a real-world payments model that rewards usage
rather than speculation. Through its dual-token architecture (BSF + sBSF),
DAO-controlled unlocks, and transparent staking mechanism, it establishes a sustainable,
merchant-focused ecosystem.
This whitepaper documents the
technical and economic foundations of the network. Its design balances security,
decentralization, and utility — providing a bridge between
blockchain finance and everyday commerce.