Getting Peniwallet multi-chain ready for Testers.

The development of Pi for @Peniwallet has begun today. We should finish in the next 2 months just to be on the safe side. After we drop Ethereum, Base and Solana for testers. What should come next is TON, Polygon, Robinhood and Bitcoin. By this time Pi should be ready.

How can I buy coins with Peniwallet. Here is what we are working on for the new Peniwallet. You will be able to us Apple Pay as well as card payment. We are also considering bank transfer. We have gotten moon pay approval already so this is something coming very soon.

Peniwallet Update We’ve identified the issue affecting some transactions. It is a gas price problem not from us but from the blockchain itself. BNB Smart Chain gas prices are currently fluctuating, but several RPC providers are not reporting the changes correctly. PublicNode, dRPC, Chainstack, and even BSC’s own DataSeed are reporting a gas price of around 0.05 Gwei, while BscScan is showing 0.1 Gwei and climbing. Peniwallet infrastructure relies on RPCs to understand current network conditions and determine an appropriate gas price when broadcasting transactions. If the RPC reports 0.05 Gwei when the network currently requires closer to 0.1 Gwei, Peniwallet can submit a perfectly valid transaction with a gas price that is simply too low for validators to prioritize. The result is that some transactions may remain pending for longer than expected, even though there is nothing wrong with the transaction itself. As a temporary fix, we are doubling the gas price used by Peniwallet to give transactions enough headroom until RPC providers begin reporting the correct network gas price again. This may slightly increase network fees, but it should improve transaction reliability and confirmation times.

In the next version of Peniwallet: We’re bringing holders data and daily trading volume directly into the wallet. You’ll be able to quickly see how many wallets currently hold a token and the total value bought and sold within the day, without having to leave Peniwallet to check an external platform.

Update on @peniwallet We’ve identified the cause of an issue some users may have noticed with balances and token prices. Peniwallet uses a Dependency Injection (DI) framework to manage and share data across different parts of the app. In some cases, that system was retaining old data longer than it should. For example, your wallet may already have received a new balance from the blockchain, but the app can remain stuck displaying the previous balance until a hard refresh clears the old state. The same can happen with prices. If a price request temporarily fails, the app may return $0 and retry immediately. Although the next request succeeds, the earlier $0 state can sometimes remain displayed. Our next app update will upgrade how Peniwallet handles DI and application state so fresh balances and prices consistently replace old data as soon as they become available. The blockchain data is already streaming and seamless. The focus of this update is making sure the app always reflects it correctly and immediately.

One of our infrastructure that we rely on for @Peniwallet price history started redirecting our request because we hit our limit of over 400 requests per second. This cause a few issues. We spent the whole night diagnosing it and switched to a new provider which offers 5,000.

We need to activate the @peniwallet Referral Program. Peniwallet is in a much better shape today than it was when we first launched. In our next update, we will also work towards enabling withdrawals of referral earnings for everyone who has referred users so far.

We are working on our developer fee sharing program for @peniwallet, it is almost ready. See screenshot below. As you can see, I am due for my share of the fees for Wiki Cat traded. If you are a developer with a token on BNB Chain, Follow @PeniwalletDevs for official update.

Update on @peniwallet The issue where some users were seeing transaction notifications on their Peniwallet even though they did not initiate any transactions was caused by previously stuck pending transactions. During the recent data revamp, all transactions were reverified. Some of these old pending transactions were picked up again by the indexer and reprocessed, which triggered the notifications. The reprocessing has now been completed, and the issue has been resolved.