Compatibility thoughts

[MikeD123]

Where relevant (tbh, using this as a notepad almost for myself... 🤦‍♂️)

w3 - Payment Request - Link

// More thought needed on this.

EIP 1102 - Opt-in Provider Access - Link

// Limiting liability is part of compliance within certain regions... Australia, NSW - Gaming licenses in pubs/clubs are required to present readily available warnings/disclosures re: risks of gambling etc... Here's an example from the official site.

Clubs should ensure that this information is readily available to members on their request. Appropriate methods of production include posting on their website, producing in written form, or by email.

Part of remaining compliant is disclosure, and I think this could be quite complimentary for user protection, but also limiting relevant liability on the platform offering the service. If you consider this all baked into protocols and truly decentralized applications who are proxying in centralized guidelines etc... Then something like this carries a ton of weight IMO...

EIP 712 - signTypedData - Link

// Feel like I could be behind the times on this one, but seemed relevant similar to EIP-1102.

[MikeD123]

OpenCorporates - Company registry database

// I was looking at this for the standardization and if it was a free resource then that'd be really cool to hook up. I could ping them and ask.

They've got a free offering I signed up for and I'll update here regarding it, but my concern is that if it's not accessible for everyone then it could be a curve-ball further down the line. Here's an example response looking up Google from their service

If you think about it though... Even if it's $20 a year, that's reasonable in some parts of the world, but if we truly want everyone to be able to build cool shit then that $20 could be the separator between the next big thing never coming to market... It'd be rad if they're keen to collab and help out though. 🤞 (crossed fingers emoji)