The Pulsar discord wallet allows the creation of a unique wallet address on the Pulsar Blockchain which is married to the user’s login credentials for discord. This wallet platform both enables access to the Pulsar Ecosystem without the need for a desktop computer and allows earning communal Proof-of-Stake (“PoS”) rewards. Essential wallet behavior on this platform reflects accepting deposits, withdrawing to a different Pulsar address, sending tips or payments to other discord wallet users, and the staking/unstaking of coins for communal participation in PoS.


The discord wallet is a shared staking wallet, whereas the desktop wallet is a solo staking wallet. This design helps new users with smaller staking balances qualify for PoS rewards by aggregating each smaller staking address/balance together under one umbrella. The higher the staking balance held in total under this one discord umbrella, the higher the chance of this shared discord umbrella winning a PoS reward for all the active users staking underneath it. Because PoS rewards distribute across all staking balances in porportion to the staking balance held, users with a smaller staking balance still are able to earn a little something from PoS by using the Pulsar discord wallet. Transactions are accurately recorded and kept up-to-date in the Pulsar Wallet Discord database, which might at-odds with what the explorer reports.


We’ve all heard the phrase, “not your keys, not your crypto.” And this is no different concerning the Pulsar discord wallet. Much like how addresses behave on a traditional cryprocurrency exchange, the Pulsar discord wallet generates an address for its users, but the users themselves do not have access to the dumpprivkey or to the importprivkey commands. However, the Pulsar discord wallet requires all participants to use discord’s 2FA security before being allowed to create an address. It is recommended that individuals using the Pulsar discord wallet also self-custody their funds in the desktop wallet and do transfers between their discord wallet address and their desktop wallet address as they deem appropriate.


Because PoS rewards are a function of a user’s staked balance, the balance a user stakes within the Pulsar discord wallet is shared while the balance a user stakes in the desktop wallet is solo. What this means is that a higher staking balance is needed in the desktop wallet to earn “all-or-nothing” PoS rewards and that more involvement will be needed to run a successful desktop wallet, which includes managing inputs, abandoning orphan transactions, and entering walletpassphrase “” 94608000 true in the console to enable staking operation. Both less staking balance and less user involvement is needed with the Pulsar discord wallet. For example, users of the Pulsar Discord Wallet will need to manually stake their working balance to their staking balance. Each user can decide for themselves the appropriate balance between security and user involvement.


Because the discord wallet is a shared wallet, the Pulsar explorer cannot report accurate balances and transactions for discord addresses. Rather, accurate balance and transaction reporting for discord addresses must come from within the discord application itself. Should a user query their discord address using the explorer, they will see differences that might, at first, cause alarm. The Pulsar Blockchain explorer does not pull information from the discord database used to record discord-specific wallet behavior, such as discord wallet deposits and discord wallet withdrawals. Only the discord wallet application queries the discord wallet transaction database. From the explorer’s point of view toward the discord wallet, the explorer sees the entire umbrella as a whole – but it does not consider the addresses generated under the umbrella. Thus, from the explorer’s perspective, part of user X’s withdrawal transaction might involve funds from user’s Y’s address. But this would be an incomplete picture of the event–the discord transaction database keeps track of the actual association between addresses/balances and users.