Skip to content

Player Profiles

In Star Atlas, a Player Profile is meant to be your main identity across the ecosystem.

The easiest way to think about it is this:

instead of your entire Star Atlas life being tied to just one wallet, the idea is that it gets tied to you.

Your profile becomes the center, while multiple wallets can connect to it.

In a normal crypto-native setup, the wallet is usually the identity. That sounds simple, but it creates problems.

If everything is tied to one wallet, then changing wallets, separating assets, or improving security becomes awkward. It can also make the player experience feel fragmented.

Instead of saying:

This wallet is the player.

Star Atlas is trying to move toward something more like:

This profile is the player, and these wallets belong to it.

That is a much more game-like model, because it behaves more like a real account instead of a single wallet address.

The model works roughly like this:

  1. you start with a wallet
  2. you create or connect a Player Profile
  3. that profile becomes your main identity
  4. you can then link additional wallets to that same profile

So instead of treating multiple wallets as totally separate identities, Star Atlas can point them back to one player identity: you.

A Player Profile can make it easier to:

  • keep your identity stable even if you use multiple wallets
  • separate gameplay wallets from treasury or staking wallets
  • manage assets more safely
  • build progression and reputation around a player, not just a wallet address
  • make the ecosystem feel more like a game account and less like raw crypto infrastructure

Later, Star Atlas expanded this idea into zProfile, part of the z.ink ecosystem.

You can think of zProfile as the more advanced, more gamified version of the Player Profile idea.

It is not only a technical account container. It is also meant to become:

  • your on-chain identity
  • your progression layer
  • your reputation or status layer
  • a place where things like XP or engagement can accumulate

AstralPass treats Player Profiles as first-class data because they help connect:

  • wallet ownership
  • Discord identity
  • DAC membership context
  • role-related checks
  • dashboard and governance-related views

That is one of the key ways AstralPass differs from a generic wallet-verification tool. It can use Star Atlas-native identity and membership context instead of stopping at the wallet itself.

This is the most important distinction to remember:

  • a wallet is a tool that holds assets and signs transactions
  • a Player Profile is the identity those wallets connect to

So the wallet is the container. The Player Profile is the player.

At first glance, Player Profiles can seem like boring account infrastructure. But they solve a real Web3-game problem:

players want the flexibility of crypto wallets, while still wanting the simplicity of a normal game account.

Player Profiles are one of the ways Star Atlas tries to combine both.

If your next question is about joining or verifying DAC membership, continue with Joining a DAC On-Chain.