Market cap
DIA price
Total supply
Holders
21.0K PHPCpartial
The last read of Ronin failed. The figure above is a floor.
33holders
Measured on Ronin. Shares are of the Ronin supply, not the multi-chain total.
0 PHPCsince Sat, Aug 29 UTC
Change in the supply DIA reads across this coin’s chains, between two daily snapshots. Not mints minus redeems: DIA does not publish issuance flow.
Market data · CoinGecko
Market data · CoinGecko
Circulating supply · DeFiLlama
Aggregator figure, not a contract read. DIA’s own onchain supply is the separate series below.
PHPC is a Philippine peso stablecoin issued by Betur, Inc., trading as Coins.ph, a Bangko Sentral ng Pilipinas licensed Virtual Asset Service Provider and Electronic Money Issuer. It launched on Polygon in 2024 under a BSP sandbox approval, later deployed on Ronin, and left the sandbox in June 2025 with its minting cap lifted.
Among peso-denominated stablecoins, PHPC is the one with a named licensed issuer that has published reserve figures at all. In this part of the map the usual alternative is a token whose issuing entity cannot be identified from public sources.
Sources: Coins.ph PHPC whitepaper, Coins.ph: BSP grants approval to pilot PHPC, BitPinas: PHPC exits the BSP regulatory sandbox
The whitepaper commits peso collateral to "100% backed by a basket of assets consisting of cash, time deposits and short-term money market instruments" and promises "periodic Proof-of-Reserves". One report has been published. As of 31 March 2025 it puts the fair value of reserve assets at PHP 100,124,186.06 against 100,000,000 PHPC in circulation, held in unencumbered savings accounts at UnionBank and Security Bank that the report describes as segregated from other Coins accounts and dedicated to PHPC holders. The attested composition is narrower than the basket the whitepaper describes. On that date it was bank deposits, with no time deposits or money market instruments in the schedule.
Two things are absent, and both are specific. The report is titled a Proof of Reserve attestation and its opinion section is headed Internal Audit Report. It was performed by the Coins.ph Internal Audit Department under the Institute of Internal Auditors' Global Internal Audit Standards and signed by the company's Chief Audit Executive, with the management assertion signed by the CEO. No external accounting firm appears. That is a genuine internal control and a different instrument from a third-party attestation, which is why PHPC sits at Tier B rather than Tier A. Cadence is the second gap: DIA located this report and no later one, the whitepaper links to none, so a process described as periodic stands at one instance sixteen months old.
DIA reads PHPC's supply from contract state on the chains it indexes. Holder concentration is not computed for any coin on this map yet, so it does not appear here. The report's figures describe a sandbox-era state, taken when circulation sat at the 100 million unit cap the BSP approval imposed and that the exit lifted, so the live figure on this page is the current one and the report is a dated snapshot beside it. Neither read verifies a balance in a Philippine savings account. That half of the question stays with the issuer and with whoever signs the next report.
Sources: Coins.ph PHPC whitepaper, Coins.ph PHPC Proof of Reserve report, as of 2025-03-31
Coins.ph positions PHPC for remittances and cross-border transfers, peer to peer payments, merchant settlement and business transactions. The Ronin deployment adds conversion of in-game earnings, and Coins.ph named the Katana decentralised exchange in the Ronin ecosystem as a further listing venue at launch.
Conversion runs in both directions on the Coins.ph platform for users who have completed identity and selfie verification, from 0.01 PHP to 250,000 PHP per transaction.
Sources: Coins.ph: PHPC launches on Ronin, Coins.ph help centre, converting PHP to PHPC (updated 2026-07-11)
Coins.ph holds both a Virtual Asset Service Provider and an Electronic Money Issuer licence from the BSP. PHPC entered the BSP Regulatory Sandbox Framework in April 2024 under an approval that capped aggregate circulation at 100 million units, and exited in June 2025 after meeting the regulator's performance indicators within two months of the pilot's start. Reporting on the exit lists the conditions carried forward: public disclosure of PHPC holders, regular reporting to the BSP, and independent third-party audits covering proof of reserves, smart contract security and system vulnerability.
The issuer's own live surfaces have not caught up. The whitepaper and the help centre article on converting PHP to PHPC both still present PHPC as operating inside the sandbox, and both still carry the obligation to reimburse circulating PHPC when the testing period ends, the help centre page as recently as its 11 July 2026 update. A reader starting from the issuer's documentation would conclude PHPC is still a pilot. DIA states the licence class as the issuer states it and has not independently located the corresponding BSP registry entry.
Sources: Coins.ph: BSP grants approval to pilot PHPC, BitPinas: PHPC exits the BSP regulatory sandbox, Coins.ph PHPC whitepaper, Coins.ph help centre, converting PHP to PHPC (updated 2026-07-11)
The sharpest gap on PHPC is between the conditions reported at sandbox exit and the artefact on the public record. Independent third-party audits of proof of reserves are among the commitments described as carried forward. The one published reserve report was produced by the issuer's own internal audit function. Whether an external engagement exists and has not been published, or has not happened yet, cannot be determined from public sources.
Reserve concentration is nameable rather than hypothetical. On the March 2025 report the whole reserve sat in savings accounts at two Philippine banks, close to 70% at UnionBank and the balance at Security Bank. Deposits are the easiest reserve type to verify and they carry the credit standing of the bank holding them.
Redemption is live rather than promised, which separates PHPC from most of the non-dollar map. The constraint is that the transparency record is a single sixteen month old snapshot, so the backing claim for every month since is issuer-stated.
Sources: BitPinas: PHPC exits the BSP regulatory sandbox, Coins.ph PHPC Proof of Reserve report, as of 2025-03-31
PHPC has no row in the DeFiLlama stablecoins dataset, checked against all 413 pegged assets it returned on 2026-07-29. DIA's onchain read is not a second opinion on PHPC's supply. For most data consumers it is the only one.
The issuer's published figure is a quarter-end snapshot from March 2025. Any current answer on how much PHPC exists has to come from contract state, which is what this page reads.
Sources: Coins.ph PHPC Proof of Reserve report, as of 2025-03-31
PHPC is issued by Betur, Inc., trading as Coins.ph, a Bangko Sentral ng Pilipinas licensed Virtual Asset Service Provider and Electronic Money Issuer.
Not by an external firm on the public record. The one published reserve report, as of 31 March 2025, was performed by the Coins.ph Internal Audit Department under the Institute of Internal Auditors' standards and signed by the company's own Chief Audit Executive. Independent third-party audits are among the conditions reported at sandbox exit, and no such report has been located.
The whitepaper commits to full backing by cash, time deposits and short-term money market instruments. The March 2025 report puts reserve fair value at PHP 100,124,186.06 against 100,000,000 PHPC, entirely in savings accounts at UnionBank and Security Bank. That is one dated snapshot, sixteen months old, and no later report has been published.
No. PHPC exited the BSP Regulatory Sandbox Framework in June 2025 and the 100 million unit cap was lifted. The issuer's own whitepaper and help centre still describe it as a pilot, the help centre as recently as its 11 July 2026 update, so issuer documentation alone would give a reader the wrong answer.
DIA reads PHPC supply directly from contract state on the chains it indexes and shows the per-chain breakdown on this page. PHPC has no row in the DeFiLlama stablecoins dataset.
0x87a25dc1…372CF69AExplorer ↗0x63c6e9f0…3b529353Explorer ↗Supply on this page is read from these contracts. Addresses are verified by DIA against the issuer’s own published documentation.
0x87a25dc1…372cf69aaddBlackList(address), removeBlackList(address) +2paused()mint(uint256)Not read on Ronin. HTTP request failed. Status: 403 URL: https://api.roninchain.com/rpc Request body: {"method":"eth_getCode","params":["0x63c6e9f027947be84d390cfa7b2332d13b529353","latest"]} Details: "<!doctype html>\n<!--[if lt IE 7]> <html class=\"no-js ie6 oldie\" lang=\"en-US\"> <![endif]-->\n<!--[if IE 7]> <html class=\"no-js ie7 oldie\" lang=\"en-US\"> <![endif]-->\n<!--[if IE 8]> <html class=\"no-js ie8 oldie\" lang=\"en-US\"> <![endif]-->\n<!--[if gt IE 8]><!-->\n<html class=\"no-js\" lang=\"en-US\">\n <!--<![endif]-->\n <head>\n <title>Access denied | api.roninchain.com used Cloudflare to restrict access | api.roninchain.com | Cloudflare</title>\n <meta charset=\"UTF-8\" />\n<meta http-equiv=\"Content-Type\" content=\"text/html; charset=UTF-8\" />\n<meta http-equiv=\"X-UA-Compatible\" content=\"IE=Edge\" />\n<meta name=\"robots\" content=\"noindex, nofollow\" />\n<meta name=\"viewport\" content=\"width=device-width,initial-scale=1\" />\n<link rel=\"stylesheet\" id=\"cf_styles-css\" href=\"/cdn-cgi/styles/main.css\" /> <script>\n (function(){if(document.addEventListener&&window.XMLHttpRequest&&JSON&&JSON.stringify){var e=function(a){var c=document.getElementById(\"error-feedback-survey\"),d=document.getElementById(\"error-feedback-success\"),b=new XMLHttpRequest;a={event:\"feedback clicked\",properties:{errorCode: 1005 },helpful:a,version: 1 };b.open(\"POST\",\"https://sparrow.cloudflare.com/api/v1/event\");b.setRequestHeader(\"Content-Type\",\"application/json\");b.setRequestHeader(\"Sparrow-Source-Key\",\"c771f0e4b54944bebf4261d44bd79a1e\");\nb.send(JSON.stringify(a));c.classList.add(\"feedback-hidden\");d.classList.remove(\"feedback-hidden\")};document.addEventListener(\"DOMContentLoaded\",function(){var a=document.getElementById(\"error-feedback\"),c=document.getElementById(\"feedback-button-yes\"),d=document.getElementById(\"feedback-button-no\");\"classList\"in a&&(a.classList.remove(\"feedback-hidden\"),c.addEventListener(\"click\",function(){e(!0)}),d.addEventListener(\"click\",function(){e(!1)}))})}})();\n</script>\n <script\n defer\n src=\"https://performance.radar.cloudflare.com/beacon.js\"\n ></script>\n </head>\n <body>\n <div id=\"cf-wrapper\">\n <div\n class=\"cf-alert cf-alert-error cf-cookie-error hidden\"\n id=\"cookie-alert\"\n data-translate=\"enable_cookies\"\n >\n Please enable cookies.\n </div>\n <div id=\"cf-error-details\" class=\"p-0\">\n <header\n class=\"mx-auto pt-10 lg:pt-6 lg:px-8 w-240 lg:w-full mb-15 antialiased\"\n >\n <h1\n class=\"inline-block md:block mr-2 md:mb-2 font-light text-60 md:text-3xl text-black-dark leading-tight\"\n >\n <span data-translate=\"error\">Error</span>\n <span>1005</span>\n </h1>\n <span\n class=\"inline-block md:block heading-ray-id font-mono text-15 lg:text-sm lg:leading-relaxed\"\n >Ray ID: a33147f5aa89d87e •</span\n >\n <span\n class=\"inline-block md:block heading-ray-id font-mono text-15 lg:text-sm lg:leading-relaxed\"\n >2026-08-30 05:09:02 UTC</span\n >\n <h2\n class=\"text-gray-600 leading-1.3 text-3xl lg:text-2xl font-light\"\n >\n Access denied\n </h2>\n </header>\n \n \n <section class=\"w-240 lg:w-full mx-auto mb-8 lg:px-8\">\n <div id=\"what-happened-section\" class=\"w-1/2 md:w-full\">\n <h2\n class=\"text-3xl leading-tight font-normal mb-4 text-black-dark antialiased\"\n data-translate=\"what_happened\"\n >\n What happened?\n </h2>\n \n <p>The owner of this website (api.roninchain.com) has banned the autonomous system number (ASN) your IP address is in (24940) from accessing this website.</p>\n \n \n <p>\n Please see\n <a\n rel=\"noopener noreferrer\"\n href=\"https://developers.cloudflare.com/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1005/\"\n target=\"_blank\"\n >https://developers.cloudflare.com/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1005/</a\n >\n for more details.\n </p>\n \n </div>\n\n \n </section>\n \n\n <div class=\"feedback-hidden py-8 text-center\" id=\"error-feedback\">\n <div id=\"error-feedback-survey\" class=\"footer-line-wrapper\">\n Was this page helpful?\n <button\n class=\"border border-solid bg-white cf-button cursor-pointer ml-4 px-4 py-2 rounded\"\n id=\"feedback-button-yes\"\n type=\"button\"\n >\n Yes\n </button>\n <button\n class=\"border border-solid bg-white cf-button cursor-pointer ml-4 px-4 py-2 rounded\"\n id=\"feedback-button-no\"\n type=\"button\"\n >\n No\n </button>\n </div>\n <div class=\"feedback-success feedback-hidden\" id=\"error-feedback-success\">\n Thank you for your feedback!\n </div>\n</div> <div class=\"cf-error-footer cf-wrapper w-240 lg:w-full py-10 sm:py-4 sm:px-8 mx-auto text-center sm:text-left border-solid border-0 border-t border-gray-300\">\n <p class=\"text-13\">\n <span class=\"cf-footer-item sm:block sm:mb-1\">Cloudflare Ray ID: <strong class=\"font-semibold\">a33147f5aa89d87e</strong></span>\n <span class=\"cf-footer-separator sm:hidden\">•</span>\n <span id=\"cf-footer-item-ip\" class=\"cf-footer-item hidden sm:block sm:mb-1\">\n Your IP:\n <button type=\"button\" id=\"cf-footer-ip-reveal\" class=\"cf-footer-ip-reveal-btn\">Click to reveal</button>\n <span class=\"hidden\" id=\"cf-footer-ip\">2a01:4f8:1c1e:9e5c::1</span>\n <span class=\"cf-footer-separator sm:hidden\">•</span>\n </span>\n <span class=\"cf-footer-item sm:block sm:mb-1\"><span>Performance & security by</span> <a rel=\"noopener noreferrer\" href=\"https://www.cloudflare.com/5xx-error-landing\" id=\"brand_link\" target=\"_blank\">Cloudflare</a></span>\n \n </p>\n <script>(function(){function d(){var b=a.getElementById(\"cf-footer-item-ip\"),c=a.getElementById(\"cf-footer-ip-reveal\");b&&\"classList\"in b&&(b.classList.remove(\"hidden\"),c.addEventListener(\"click\",function(){c.classList.add(\"hidden\");a.getElementById(\"cf-footer-ip\").classList.remove(\"hidden\")}))}var a=document;document.addEventListener&&a.addEventListener(\"DOMContentLoaded\",d)})();</script>\n </div><!-- /.error-footer -->\n </div>\n <!-- /#cf-error-details -->\n </div>\n <!-- /#cf-wrapper -->\n\n <script>\n window._cf_translation = {};\n \n \n </script> \n \n </body>\n</html>" Version: viem@2.48.4.
Read from the deployed contract. “Not determined” means the contract’s full function set could not be enumerated, not that the capability is absent: a bytecode scan can confirm that a function exists and can never prove that one does not.
Reserve attestation cadence
None identified
We checked the issuer's disclosure pages and found no reserve attestation. Coins we have not checked carry no value here at all.