- 04 August 2023 (2 messages)
-
Joined. -
Unhosted Marcellus đ«đ» (@oomahq) on XNew psyop just dropped. The existing standarness rules such as the 80 byte limit on OP_RETURN are now called "paternalisms", and a few devs are starting to move to remove them from BC. If you want to voice your concern you can do it in this Pull Request. https://t.co/iEzoOC6Uzi
- 07 August 2023 (12 messages)
-
any dev's serious thoughts on this? I've been following some responses, but would be super interested to know thoughts or reactions -
Also, in relation to this I started a Forum post to start the process of picking the most influential and important upgrades to Counterparty. The purpose would be to make a cool infographic for a new "History" page on the website. It is my intention to note and signify as many Developer Upgrades to Counterparty to show on the developer timeline as possible. I also tried to note any potential upgrades being worked on for the future. Feel free to leave feedback and discuss there if I missed something or explained an upgrade wrong: https://forums.counterparty.io/t/counterparty-developer-timeline-for-counterparty-io/6675Counterparty Developer Timeline for Counterparty.io
Since publishing this post: Updating Information on Counterparty.io - #7 by davesta I have had a great amount of positive feedback to create a âHistoryâ Tab for Counterparty.io where we can display all the Counterparty Upgrades, historic developments and CIPâs in a nice, cool, user friendly way. I also mention a âUser/Artist Historical Tokenâ Timeline in the post mentioned above, but I will do a separate post for that one. Let focus just on developer updates here. It is my intention to gather...
-
Would be nice to be able to do op_return larger than 80 bytesâŠ. Would def be preferred to the multisig encoding methodâŠ. Tho I think taproot encoding and op_return will be close to costing the same amount in the futureâŠ
Imo this would be a step in the right direction⊠making it easier/cheaper to store arbitrary data in op_returnâŠ. Also makes dev a bit easier since less code to encode/obfuscate data -
interesting good to hear your perspective
-
unlimited op_return would be the ideal method -
imo
-
i think there is an output size limit of 100kb or somethign
-
but basically its acknowledging âhey we know people want to store data other than btc transactional data on-chain so hereâs how you should do it so we can ignore it if we wantâ
-
its a weird tug of war, denying reality thing that goes on
-
Too bad it took 9 years for this progress⊠but Iâll take it⊠better late than neverđđ»
-
I think the core devs are finally coming around to the fact that using op_return is far less damaging than multisigâŠ.. they canât stop us from experimenting⊠so at least now theyâre setting up a playground for experimentation rather than continuing to try and put up dev fencesđđ»
-
there are so many ways to cram data on-chain, not having a method that can store more than 80 bytes in a tx to compete for fees doesnât make much sense
- 10 August 2023 (27 messages)
-
Dispenser Improvements (OWNED / BURN address types) · CounterpartyXCP/cips · Discussion #103
Current Dispenser Address Types Currently dispensers are able to be opened on 2 different address types : SOURCE address EMPTY address An EMPTY address is defined in CP as any address which does no...
-
How do you verify a burn address? Seems impossible outside of an oracle. -
open to discussion.. no real standardized way to verify it... could come up with some standardized format like "must contain a certain number of X characters before signature"... ie 1CounterpartyXXXXXXXXXXXXXXXUWLpVr... but no perfect way to verify a burn address... perhaps some here will have ideas đïžïžïžïž
-
IMO... the OWNED addresses is the big addition here... being able to open/refill/close dispensers on other addresses... one complaint I consistently hear is ppl can OPEN a dispenser on an empty address, but can't close the dispenser remotely, and are annoyed at having to send BTC to the dispenser address, then do another tx from the dispenser address, just to close the dispenser.... OWNED addresses would allow one to refill/close a dispenser and fund it from the SOURCE address (assets and BTC tx fees)
-
added some comments
-
IMO... The logic to open dispensers up on EMPTY addresses is flawed... we currently allow opening up of dispensers on any address as long as it does not have any COUNTERPARTY balance history...
The reason this is a concern...
OXBT Dispenser = 50,000,000 tx until dispenser is empty
https://xchain.io/tx/9447ce5f97da93649c5865bb8146aebef5c1aa2968c6ba8005b5642a7d9c615f
ORDIPEPE Dispenser = 3,000,000 tx until dispenser is empty
https://xchain.io/tx/4c3e483b7762f42f8051d782ceec298b8a969f192f1120140037913b2d2b0494
OGPASS Dispenser = 200,000 tx until dispenser is empty
https://xchain.io/tx/11a115ba3b8558afb9d6f19fc51102918fdfd210eb8fd80e4c8fb5adf04165b5
These dispensers were opened up on exchange hot-wallet addresses, and all the resulting "dispenses" are not actually users buying from dispensers, but rather an exchange moving funds around internally. The end result is the exchange is in control of 100% of these funds (all addresses are owned by them), and the CP database is just bloated with a bunch of unnecesary "dispense" records (something I PERSONALLY consider abuse/spam).
These 3 dispenser alone can contribute over 53M records to the CP database... and this is just the beginning unless we do something to address this issue.
I encourage you guys to take this issue seriously and discuss solutions and if this matters to the community, put forth a CIP to address this issue -
we could redefine empty to mean no utxo history
-
Joined. -
Hi everybody,
I'm a big fan of tokenization on Bitcoin. I work on CashTokens on Bitcoin Cash, and I had this idea to revive some of the cool early counterparty tokens of Counterparty (which are also on the BCH but never got a supporting ecosystem) as CashTokens.
Like a 1-to-1 airdrop using a new protocol. If any of the pre-2017 counterparty projects are interested in this, please reach out to me đ -
On BCH we had our own fair share of experimentation with token standards: SLP, wormhole, tokenda but eventually settled on CashTokens: native miner validated tokens
-
So slightly off topic but I want to see if there is any interest from early Counterparty projects, I think many people in BCH have nostalgia for these early token projects.
-
is there a write-up about how cashtokens work?
-
i seem to remember SLP being the chosen token protocol
-
Sure! there is a full technical specification, but here is the introductory blogpost by its creator https://blog.bitjson.com/cashtokens-v2/
-
Iâm just surprised no one has tried this until now
-
thanks, i think âreviveâ is probably not the right terminology, maybe âsummonâ?
-
its funny because there are eth contracts that do this
-
like anytime i move USDC i get weird bizarro tokens
-
Yeah SLP got traction for a good while! But ended up having major scaling problems, and issues with the special indexers needed. Many Interesting usecases were not possible because they couldn't be validated by the VM, so it has totally fallen off
-
what VM?
-
The BCH VM, so BCH script, couldn't verify these tokens. So while BCH had covenants you could not make interesting token covenants
-
Just like how there is a real desire to do AMMs for Ordinals but you could never do that as ordinals are an off-chain L2 concept, just like SLP was
-
and like counterparty is
-
Yeah
-
you can do fun stuff like that you just have to re-write it at the parser level and you canât really use the main chain token
-
So you could make a covenant that verifies a specific utxo, for example for a noncustodial NFT buy offer. But with L2 tokens script will never be able to verify the token itself
-
So AMMs (arguably the biggest innovation from defi) would never be possible
- 13 August 2023 (3 messages)
-
Pls write up a post with your idea so thoughts can be captured and documented for others outside of this chat to see/discuss https://github.com/CounterpartyXCP/cips/discussionsCounterpartyXCP/cips · Discussions
Explore the GitHub Discussions forum for CounterpartyXCP cips. Discuss code, ask questions & collaborate with the developer community.
-
Hi Derp, I must say, this is deeply interesting... look forward to the write-up on Github! - 14 August 2023 (3 messages)
-
thanks, will review and drop my thoughts in reply next day or two :)
- 17 August 2023 (1 messages)
-
Joined. - 20 August 2023 (49 messages)
-
Joined. -
Can you describe a "trust" wallet address?
-
If you have the private key for the address you can import it into Freewallet (or Counterwallet) and move the assets out.
-
Was it a Counterwallet seed phrase or a BIP39?
-
For importing addresses with just a private key use this FAQ: https://gist.github.com/davestaxcp/1e2cc086a13c9a2d045876852b57e5be#viewing-creating-and-importing-addressesFreewallet FAQ 2023 v0.9.23 - Write Up - Draft #5
Freewallet FAQ 2023 v0.9.23 - Write Up - Draft #5. GitHub Gist: instantly share code, notes, and snippets.
-
For your 12 word phrase import you have 2 options. Counterwallet format and BIP39
-
Freewallet FAQ 2023 v0.9.23 - Write Up - Draft #5
Freewallet FAQ 2023 v0.9.23 - Write Up - Draft #5. GitHub Gist: instantly share code, notes, and snippets.
-
Since your 12 word phrase also accesses your BTC wallet, have you tried importing it into any other BTC wallets? Electrum for example?
-
Okay so at least you know the seed phrase is correct
-
Do you know what format your seed phrase is? Freewallet only supports those two I mentioned
-
Are you sure you are looking at the correct address? Checking the address on xchain and seeing the xcp assets associated with the address?
-
I don't know what a trust wallet seed phrase is
-
Like a trust in the legal terms?
-
nope first time ive heard of it
-
... why would you want to get rid of those assets? sheesh ill take the SUCKMYPEPE
-
that one is hard to get
-
XCHAINPEPE too.. wow
-
is there a way you can get your address specific Private Key for this segwit address?
-
then you can use freewallet to import the address and not the seed phrase... as mentioned here
-
might wanna to get into contact with them to get access to your private key... im seeing this page but not gonna dive into it:
-
How To's
Learn how Trust Wallet works. We have self-help guides and articles to get you started with Trust Wallet. Use advanced features like Staking, DEX and accessing DApps.
-
thanks Helene this is also true
-
maybe we should update the website a little ;)
-
Updating Information on Counterparty.io
It is my opinion that the counterparty.io website is outdated and does not accurately represent linking to the best educational information for Counterparty. This post includes the starting process of trying to publicly correct and revise information about each page of the Counterparty website to try to include topics like: CIPâs, wallet documentation, support pages and our spectacular history throughout Counterpartyâs lifetime on counterparty.io. The first impression most users will have in ...
-
Counterparty Developer Timeline for Counterparty.io
Since publishing this post: Updating Information on Counterparty.io - #7 by davesta I have had a great amount of positive feedback to create a âHistoryâ Tab for Counterparty.io where we can display all the Counterparty Upgrades, historic developments and CIPâs in a nice, cool, user friendly way. I also mention a âUser/Artist Historical Tokenâ Timeline in the post mentioned above, but I will do a separate post for that one. Let focus just on developer updates here. It is my intention to gather...
-
i wonder who is working on it.....
-
-
would be nice if I got some public feedback on the posts
-
-
even a "wow this is awesome I support this" would boost my serotonin by at least 20%
-
glad Helene and I could help
- 21 August 2023 (2 messages)
-
-
BTNS Indexer, explorer, APIs, etc.... for those who are interested in playing around with a new token platform... will be working on adding support for dispensers in the coming week đ
- 22 August 2023 (1 messages)
- 23 August 2023 (27 messages)
-
Hi, does anybody know why
I can't multisend from this address
1LVfMMC7Lr3CkdKHp5BWVctU82LZKPqfix
Has been an issue for a while, I can send single assets, but when I try multisend it keeps saying can not broadcast first transaction
Appreciate any help that can be given
Thank you -
try copying/pasting the signed tx from the debug console and broadcast yourself using a tool like this https://live.blockcypher.com/btc/pushtx/
-
it should give you a more helpful error message about why your unable to broadcast the tx
-
Where can I find debug console (signed tx)?
-
click freewallet logo then debug button then click on "console" in window that pops up
-
sign tx.. it will appear in the console.. copy/paste to broadcast in separate tool
-
Thanks m8, I'll give it a try
-
Transaction successfully broadcast
-
But just tried a multisend again no send
-
Ahh there was like 31 signed tx in console, I cleared, tried new multi send, now says server error 500 when I repeat process
-
Server settings normal in frw
-
i posted this in xcp chat, but will post again here, we found an issue with multisend if you added a hardware wallet address: https://gist.github.com/davestaxcp/1e2cc086a13c9a2d045876852b57e5be#my-second-transaction-on-an-mpma-multi-send-is-not-getting-confirmed-and-giving-me-an-error-what-can-i-doFreewallet FAQ 2023 v0.9.23 - Write Up - Draft #5
Freewallet FAQ 2023 v0.9.23 - Write Up - Draft #5. GitHub Gist: instantly share code, notes, and snippets.
-
No never used hardware, the frw hasn't updated on the last 2 updates, could that be the issue?
I don't really want to update until sweep function working -
you can update to v0.9.22
-
that version still has sweep function
-
Plus is not broadcasting first transaction, single sends works fine
-
ah i see
-
Yes but shouldn't the version prior be OK?
-
that is the version prior
-
lastest is v0.9.23
-
It's on v0.9.21
-
thats what you have?
-
Releases · jdogresorg/freewallet-desktop
Desktop wallet for Win/Mac/Linux which supports Bitcoin and Counterparty - jdogresorg/freewallet-desktop
-
also we can move this to freewallet chat to not clog up dev chat
-
Yhh
-
Freewallet.io Chat
This is a channel to discuss FreeWallet and ask questions and let the community answer
- 24 August 2023 (9 messages)
-
All fixed, I updated and can now multisend, thanks
-
has anyone encountered this error trying to set up a federated node? if so have you fixed it? (I am following the documention set up guide)
Cannot install, as it appears a process is already listening on host port 8332 -
are you running a bitcoin node already?
-
yes
-
thats probly the issue if youâre setting up a federated node, it wants to install its own bitcoin node with the docker
-
i am running bitcoin GUI (core, what was QT) not CLI bitcoind
-
if you kill it that error should go away
-
Great Solution to many problems -
okay so install with bitcoin core not opened. Will try later - and annoy you if i need more help đ
- 25 August 2023 (5 messages)
-
Hello good Counterparty people, I have just posted my draft of a Counterparty specific Asset Timeline that is intended to be shown on a possible future "History" page on Counterparty.io - I would love any and all feedback and for some OG's to verify and critique the information: https://forums.counterparty.io/t/counterparty-token-asset-project-timeline-for-counterparty-io/6688Counterparty Token/Asset/Project Timeline for Counterparty.io
This post is dedicated to publicly organizing and critiquing a public list for Counterpartyâs vast historical assets/tokens and projects we have seen since Counterpartyâs inception. The goal for this list is to eventually put them into a cool Historical Timeline to be published on Counterparty.io in a new page titled âHistoryâ. This, and other website changes were previously published in this Counterparty Forum post: Updating Information on Counterparty.io - #8 by davesta The planning of this ...
-
Also on another note would it be a good idea to update where to point new users and new potential developers on the CIP readme and CIP 1? Since the Slack Channel and its link are not accessible? Would it be better to point them to the CIP discussions github and this telegram chat?
-
cips/README.md at master · CounterpartyXCP/cips
Counterparty Improvement Proposals. Contribute to CounterpartyXCP/cips development by creating an account on GitHub.
-
-
- 26 August 2023 (1 messages)
-
Joined. - 27 August 2023 (5 messages)
-
YesâŠ. Feel free to make a pull request, or I can make this suggested update when I have time.
-
havent done a pull request yet, but can do that.... would it be more prudent to include in an informational CIP as stated with this idea here or keep them separate?
-
Adding a 'History' tab on Counterparty.io - Including a Developer and Asset/Project Timeline · CounterpartyXCP/cips · Discussion #106
I think it would be a great idea to add a 'History' tab to the Counterparty.io website that included two timelines. The first timeline included on the page would be an infographic of all of...
-
Iâd update cip1 with current info⊠no need for a new CIP
-
huge! thank you
- 29 August 2023 (1 messages)
-
Who are you talking to and why are you just pasting commands with no context, question, etc.?
Please be clear/concise with your questions and requests here. - 31 August 2023 (10 messages)
