You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Instantly share code, notes, and snippets.
💭
https://FullStack.cash is where I play.
Chris Troutner
christroutner
💭
https://FullStack.cash is where I play.
I'm a senior, full stack, JavaScript developer. I founded FullStack.cash and PSFoundation.cash. Work in Bitcoin Cash (BCH) space.
A JSON file containing public PSF v2 Circuit Relays (IPFS) running Helia
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This page is used to post updates about the CoinJoin Flipstarter campaign. The campaign was fully funded by the BCH community in November of 2022, and work will take place from January through March of 2023.
It's handy to use UFW to limit the amount of bandwidth, resources, and ultimately the number of peers that IPFS can connect to. IPFS can be a resource hog, and there are not internal tools to mitigate it. The official stance from IPFS is that bandwidth and firewall controlls should be implemented by the host OS, not by their software.
All ipfs-coord-esm consumers use port 4001 or 4003 and TCP. No peers use UDP or QUIC (which runs on UDP). So any connections to peers using these protocols are wasted resources.
I'm having a difficult time communicating with the BitBay support for what should be a simple refund. This document was created in order to better share links and make it easier for the BitPay support staff to facilitate a refund.
Short Version
I paid BitPay invoice CSw5bWhtu41e1dcrSyiKt4, which resolved in my Electron Cash wallet as bitcoincash:qzfg5e8zmeauj3wx603hg3eyw4ynasa73uqyucjt3m. I need BitPay support staff to review invoice CSw5bWhtu41e1dcrSyiKt4 and refund the Bitcoin Cash sent to that invoice.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There have been a handful of attempts to create standards around SLP token icons. All approaches prior to the PSF specifications relied on centralized services. The PS002 and PS007 specifications define the use of mutable (changable) data in SLP tokens. Inside this mutable data, a URL to the token icon can be placed. The big advantage of these specifications is that the token icon can be changed at any time by the token creator. It is permissionless, secure, and the process does not rely on any centralized services.
Hands On Examples
This NFT Collector App shows examples of NFTs created using SLP tokens and mutable data (including token icons).
This document sketches-out the construction and operation for a 'token bridge' with the ability to move a stablecoin (or other token) between two blockchains. This would allow the best stablecoins across all chains to be offered on chains with less capability.
The bridge described in this document is 'custodial' in the sense that is in sole possession of the funds for a few minutes, before it transfers the value between chains. However, it is 'trust-minimized' in the sense that every function of the bridge results in on-chain transactions that can be audited and verified by anyone in the world. Beyond the technical considerations, operating this bridge under the control of a business registered in a crypto-friendly jurisdiction would benefit the deployment and long-term operation of the bridge.
Architecture
The diagram below shows the canonical workflow for transferring a stablecoin between the AVAX and BCH chains. Any two blockchains can be used that support