setup zapstore publishing

[basantagoswami]

Publishing via Zapstore:

• Build the new release APK
• Add the SIGN_WITH= variable to .env. If you have the Bull nsec in a browser extension, then it's an easy process. I won't recommend using the private key directly in the .env or even using a bunker://... connection string. As we are considering publishing the .env used in production to make the reproducibility of the wallet easier, using either nsec, or bunker URL increases the risks of exposing private information.

This link explains how the install the zapstore CLI. The zapstore.yaml file has already been configured in this PR

If the built APK is in some file other than the path defined in assets in zapstore.yaml, you'll have to update it

The run zapstore publish

For the currenlt latest release (6.4.0), you'll be asked to sign events like these:

New app:

{
  "content": "The best mobile Bitcoin wallet of all time - focused on privacy, security and usability for day-to-day Bitcoin transactions.",
  "created_at": 1766117114,
  "kind": 32267,
  "tags": [
    [
      "d",
      "com.bullbitcoin.mobile"
    ],
    [
      "name",
      "BULL"
    ],
    [
      "url",
      "https://wallet.bullbitcoin.com"
    ],
    [
      "t",
      "bitcoin"
    ],
    [
      "summary",
      "Bitcoin-only mobile wallet with built-in exchange"
    ],
    [
      "repository",
      "https://github.com/SatoshiPortal/bullbitcoin-mobile"
    ],
    [
      "f",
      "android-arm64-v8a"
    ],
    [
      "f",
      "android-armeabi-v7a"
    ],
    [
      "f",
      "android-x86"
    ],
    [
      "f",
      "android-x86_64"
    ],
    [
      "license",
      "MIT"
    ],
    [
      "icon",
      "https://cdn.zapstore.dev/7f3610090e5552b0bcff091fc9fb7b044bc84d37e87a7ba87036aeaa9b77ddba"
    ],
    [
      "a",
      "30063:46f6acdf9064234122fa080f5d9ef69573d791048e0b256630f8af296331b6e7:com.bullbitcoin.mobile@6.4.0"
    ]
  ]
}

New release

{
  "content": "",
  "created_at": 1766117114,
  "kind": 30063,
  "tags": [
    [
      "d",
      "com.bullbitcoin.mobile@6.4.0"
    ],
    [
      "e",
      "ab7b873e42dff6827eabddbb8b2780dde1f9dace68c56e761ce86e85887cbb27"
    ],
    [
      "a",
      "32267:46f6acdf9064234122fa080f5d9ef69573d791048e0b256630f8af296331b6e7:com.bullbitcoin.mobile"
    ]
  ]
}

etc

[ethicnology]

@basantagoswami it would be super nice if we can have a Continuous Deployment when a PR is merged on main that would automatically deploy the version to the ZapStore using a Github Secret for signing as shown there

Then @BullishNode will only have to generate the NIP07 signing key and add it to the Github Secrets.

No extra work to be perform by @i5hi on each release

[ethicnology]

What is the current status of this PR ?

I guess there is few refactoring needed since our latest work on reproducible builds (no .env anymore)