pOAS is a point OAS designed for use within the Oasys ecosystem. It is implemented as an ERC-20 token and is intended to maintain a 1:1 value parity with native OAS (i.e., 1 OAS = 1 pOAS).
We designed pOAS to function as a point system. Holders can use pOAS as a payment method for pre-registered contracts. When pOAS is transferred, it is burned, and the recipient receives the equivalent amount in native OAS. To prevent unintended payments or exchanges, only whitelisted recipient addresses can receive pOAS.
Although pOAS holds the same value as OAS, it is not fully collateralized. The collateral ratio is below 100%, and the value is maintained based on trust in the issuer. The issuer must carefully manage the collateral balance to ensure that there is no shortage of native OAS.
- ERC-20 Token
- Name: oPAS
- Symbol: pOAS
- Decimals: 18
- Transfer:
- Only whitelisted addresses (with RECIPIENT_ROLE) can receive pOAS.
- Upon transfer, pOAS is burned and the recipient receives the equivalent amount of native OAS.
- Mint: Only addresses with the OPERATOR_ROLE can mint pOAS.
- Burn: Self-burnable by the holder
- Roles
- ADMIN_ROLE:
- Assigned to the admin account.
- Can grant or revoke other roles.
- OPERATOR_ROLE:
- Assigned to operator accounts responsible for daily pOAS operations.
- Can perform the following actions:
- Mint pOAS
- Add or withdraw collateralized OAS
- Manage pOAS recipients by granting or revoking RECIPIENT_ROLE
- RECIPIENT_ROLE:
- Assigned to addresses allowed to receive pOAS.
- Only holders of this role can receive pOAS.
- ADMIN_ROLE:
- Supports deposit/withdrawal of collateral OAS by operators
- Includes a read-only function to retrieve the list of recipient addresses in JSON format
- Uses the proxy pattern to support future upgrades
- PaymentSample: A contract that accepts pOAS as a payment method.
- ClaimSample: A contract for distributing pOAS to users as part of promotional campaigns or in-game events.