From their web page:
> Transparent
> A top auditing firm will attest to the matching supply of BUSD tokens and underlying U.S. dollars on a monthly basis.
Note the future tense, as in, "sometime indefinitely away in the future".
Their attestations (as opposed to audits) just say that at a certain instant in time they had the required amount in a bank account. That means Paxos could have borrowed it for a short while. Quote [1]: "Any activity prior to or after the Report Dates and Times at 5:00 pm ET was not considered when testing the assertions described above."
This is the same trick pointed out by Coffeezilla about a year ago, about Tether. [2]
And the one from November is missing.
[1] - https://paxos.com/wp-content/uploads/2022/10/Executed-BUSD-E...
For all anyone knows the assets held could be collateral for a large overdue loan.
[1] Here is the specific NYDFS guidance on Paxos' issuance of stablecoins. [2] And here is a link to their NYDFS appointed third-party auditory accounting firm.
Complaints against Paxos can be filed with the New York State Department of Financial Services at:
One State Street
New York, NY 10004
---
OR with Paxos directly at
450 Lexington Ave
Suite 3952
New York, NY 10163
---
[1] https://www.dfs.ny.gov/industry_guidance/industry_letters/il...
Only BUSD on Ethereum (ERC-20) is issued by Paxos. The BUSD on the BNB Chain (BEP-20) is not affiliated with Paxos and not regulated by NYDFS. Quoting Paxos:
"BUSD is issued by Paxos on the Ethereum blockchain and regulated by the New York Department of Financial Services. Separately, Binance wraps BUSD and issues separate tokens (known as Binance-Peg BUSD) on several blockchains, including BNB Smart Chain, Polygon, and Avalanche. These tokens are unaffiliated with Paxos and not regulated by the NYDFS."
Offhand, I can't think of a fast and easy way to verify this reliably.
Edit: I spent some time thinking the Ethereum number was the total number of BUSD, but apparently it is Binance's holdings which can be found in a wallet nicknamed "Binance: Binance-Peg Tokens" on Etherscan [3]. Since this number is greater than the total number of pegged tokens, I guess everything adds up. (Of course, since the "cross-chain peg" here is implemented in a centralized way by Binance, it could de-peg at any point they want it to.)
[1] https://www.binance.com/en/blog/ecosystem/understanding-busd... [2] https://www.binance.com/en/collateral-btokens [3] https://etherscan.io/address/0x47ac0fb4f2d84898e4d9e7b4dab3c...