Short answer
索尔代币 is 索拉纳网络's native asset and is commonly used for network fees and 钱包-level payments. 索拉纳程序库代币 are tokens built on 索拉纳网络's token standard; games may use them for assets, balances, rewards, or special utility depending on design.
For players, the practical question is simple: what am I paying, what am I receiving, and which balance will change? A good game makes that visible before any 钱包 approval.
The design tension
索尔代币 is familiar because it is the base asset of the network, but using it everywhere can make a game feel financially intense. 索拉纳程序库代币 can represent more specific game value, but they add vocabulary and may require token accounts.
The design challenge is clarity. Players should not have to guess whether a cost is a network fee, an entry price, a token transfer, or a reward distribution. The same 钱包 can show several asset types, and the game has to label them responsibly.
Player benefit
When 索尔代币 and 索拉纳程序库代币 are explained well, players make calmer decisions. They can separate unavoidable network costs from optional game costs, and they can understand why a token account may appear in a flow.
This also reduces support friction. Many 钱包 questions come from unclear asset language rather than from the chain itself.
Clear asset language also helps players manage risk. They can keep enough 索尔代币 for fees, recognize when a game is asking for more than a fee, and avoid approving a transfer they did not intend.
奇迹 example
奇迹 should keep 索尔代币 language especially careful around pools, payments, and settlement. If an action involves 索尔代币, the player should understand whether it is a fee, a cost, a prize context, or a reward-related event.
If SPL-style assets or token accounts appear later, they should be introduced as specific game instruments, not vague crypto decoration.
What to watch
Watch for prompts that mix terms: fee, payment, reward, token, claim, and transfer should not be used interchangeably. Each word should point to a real action.
If the interface cannot explain which asset is moving and why, the player should slow down before approving.