Last active
December 13, 2023 18:45
-
-
Save jdogresorg/42e31755abb03d445d0648c606064e71 to your computer and use it in GitHub Desktop.
Counterparty Thoughts / Features
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
# Counterparty Thoughts / Features | |
- AML / KYC Compliant tokens | |
- Have heard consistent feedback over the years that companies/projects dont issue on CP cuz they can't do so and be in AML/KYC compliance. | |
- We need to provide a way for Companies can do their own AML/KYC (external), and then maintain lists of addresses on CP | |
- From a functionality perspective we just need : | |
- ability to create/edit LIST of addresses (whitelists/blacklists) | |
- update issuances to indicate new token type (AML/KYC compliant) and reference to LIST | |
- Update Send / Order / Dispenser logic to support AML/KYC tokens using LIST | |
- Remove XCP requirement | |
- Consistently hear feedback that it is a shitcoin that is required to use XCP... gonna keep hitting that hurdle until all of CP can be used with just BTC. | |
- We need to provide a way for people to buy XCP using BTC in the background before XCP is required for a function | |
- From a functionality perspective we just need: | |
- add support for `optional_outputs` so CP users can specify additional outputs for a CP tx | |
https://github.com/CounterpartyXCP/counterparty-lib/issues/1214 | |
- Have CP generate tx that purchases XCP from an open dispenser using BTC (tack on extra output to CP normal TX) | |
- Update CP parsing logic to parse dispenses first (so XCP is in address balance before it is needed) | |
- https://github.com/CounterpartyXCP/cips/discussions/92 | |
- File encoding support | |
- Currently no limit on issuance descriptions, so ppl (STAMPS) been stuffing base64 encoded files in there (ick) | |
- Need a simple way for ppl to encode files to BTC and link to a token without bloating database | |
- Need to address this issue/database bloat BEFORE adding support for taproot/p2wsh and encoding larger files. | |
- https://github.com/CounterpartyXCP/cips/discussions/109 | |
- Bridges to other ecosystems | |
- Have heard over they years that ppl worry about CP long-term, and having ability to move a CP token to other ecosystems gives them more confidence that they can do waht they want with their tokens (in case CP "dies") | |
- Ordinal Envelopes - https://forums.counterparty.io/t/ordinal-envelopes/6504 | |
- Multi-chain support (Pluggable Chains) | |
- https://github.com/chiguireitor/cips/blob/cip-16/cip-0016.md | |
- Virtual Machine / Smart contract Language | |
- Have been hearing for a number of years that people want the ability to write their own smart contracts and dont like Solidity. | |
- CPs hardcoded features are great, but ppl want the ability to build additional logic on top of those hard-coded features. | |
- https://forums.counterparty.io/t/proof-of-concept-vm-development/3031 | |
As far as the other features of BTNS... most are either things CP previously had and removed (like callbacks)... or features I want to build.. like the ability for dispensers to trigger dispenses with tokens, not just BTC payments. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment