This guide shows you how to make sure MyDoge gives the wallet to every page of your dApp. MyDoge gives the wallet only to the origins on your listing; About the MyDoge In-App Browser explains why.

For anything on this page that needs the DogeOS team, reach them in the DogeOS Discord .

Point Your Listing at Your App#

Give your listing the origin where your app and the SDK run, for example https://app.example.com, rather than a landing page that links or redirects there. Include www. or a port if your app uses one.

Add Your Other Origins#

If your app spans several origins, send the DogeOS team the full list so they can add them to your listing. On MyDoge 3.1.1 and later, the wallet works on every origin on your listing. On MyDoge 3.1.0, it works only on the origin the dApp opened at, so keep wallet flows on one origin where you can.

Choose Your Networks#

Tell the DogeOS team which networks your dApp uses, so your listing names them. Inside MyDoge, your dApp starts on DogeOS Chikyū Testnet when the listing names it or names no networks; otherwise it starts on one of the listed networks.

Register Your Origins in the Console#

Register the same origins on the matching client ID in the developer console . The console and the listing are separate. See Get a Client ID.

Change Domains#

Tell the DogeOS team before you move to a new domain, so the dApp list sends users to the new one.

Get Listed#

Test your dApp in MyDoge first. Once it works on testnet, ask the DogeOS team for a listing. Listings are reviewed by hand. Submit the exact origin where the SDK runs and every other origin your app uses.