omnipin 1.4.2 → 1.5.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +7 -7
- package/dist/cli.js +20249 -18581
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -30,13 +30,13 @@ Read the [docs](https://omnipin.eth.link).
|
|
|
30
30
|
|
|
31
31
|
### "Most flexibility, lowest trust assumptions"
|
|
32
32
|
|
|
33
|
-
Walletbeat uses Omnipin to deploy to IPFS. It was selected after [contrasting it against many other web3 deployment options](https://github.com/walletbeat/walletbeat/blob/beta/governance/decisions/2025-walletbeat-hosting.md), and Omnipin stood out as the one with the most flexibility, user control, lowest trust assumptions, lowest-dependency, and not locked into any specific provider.
|
|
34
|
-
|
|
35
|
-
Omnipin makes it easy to automate deployment to multiple IPFS providers for redundancy, gate deployment success by actual replication and availability on popular IPFS gateways for reliability, and to update the onchain ENS records to point to the deployed IPFS CID to boot (without granting CI any authority beyond ENS record updates). Runs great with Helios too.
|
|
36
|
-
|
|
37
|
-
In other words, Omnipin is the missing deployment tool that makes it feasible to adopt the cypherpunk standards and technologies that web3 frontends should strive to adopt. No more excuses now.
|
|
38
|
-
|
|
39
|
-
[polymutex.eth](https://farcaster.xyz/polymutex.eth), core dev of WalletBeat
|
|
33
|
+
> Walletbeat uses Omnipin to deploy to IPFS. It was selected after [contrasting it against many other web3 deployment options](https://github.com/walletbeat/walletbeat/blob/beta/governance/decisions/2025-walletbeat-hosting.md), and Omnipin stood out as the one with the most flexibility, user control, lowest trust assumptions, lowest-dependency, and not locked into any specific provider.
|
|
34
|
+
>
|
|
35
|
+
> Omnipin makes it easy to automate deployment to multiple IPFS providers for redundancy, gate deployment success by actual replication and availability on popular IPFS gateways for reliability, and to update the onchain ENS records to point to the deployed IPFS CID to boot (without granting CI any authority beyond ENS record updates). Runs great with Helios too.
|
|
36
|
+
>
|
|
37
|
+
> In other words, Omnipin is the missing deployment tool that makes it feasible to adopt the cypherpunk standards and technologies that web3 frontends should strive to adopt. No more excuses now.
|
|
38
|
+
>
|
|
39
|
+
> — [polymutex.eth](https://farcaster.xyz/polymutex.eth), core dev of WalletBeat
|
|
40
40
|
|
|
41
41
|
[github-actions]: https://github.com/omnipin/omnipin/actions
|
|
42
42
|
[gh-actions-img]: https://img.shields.io/github/actions/workflow/status/omnipin/omnipin/ci.yml?branch=main&style=for-the-badge&logo=github&label=&color=%232B4AD4
|