- 01 December 2022 (24 messages)
-
messing around with chatgpt and i think it found a more efficient way to encode data in p2sh redeemscripts š³
-
-
this AI is really incredible
-
It's the code part of openai?
-
just released yesterday
-
not just code, you can ask it anything
-
looks like i dont need to sift through unit tests and poorly written docs anymore
-
-
This whole thing was written by AI???
-
yes
-
-
Too many people on it
-
wanna learn how to do multisig transactions using bech32, easy peesy
-
-
im giving it the most basic prompts too
-
thinking about how best to implement dispenser creation/management in rpw and i had the idea of using a 1 of 2 multisig for dispenser addresses
-
that way all dispenser payments would be spendable from the creation address, and the 2nd address could be some fixed increment address generated by passphrase like n+1000 or something
-
or it could be an unspendable address
-
-
Is there a GitHub issue about this? @pataegrillo
-
I don't know. That's something I have in a personal to-do list, because i was about to do it then i thought it's better to test in a single index first
-
-
Ok, I'll try to open an issue whenever i have time
-
- 04 December 2022 (6 messages)
-
I have a wallet question, a user has access to therir wallet via a magic link so does not have 12 words written down. They wanted to move to a new wallet. I wanted to know if the Sweep/Import from a Private Key on CounterWallet worked, seems this would be quickest path? Create new wallet, sweep?
-
-
GitHub - jdogresorg/counterwallet-quick-access-recovery-tool: Counterwallet Quick Access Recovery Tool
Counterwallet Quick Access Recovery Tool. Contribute to jdogresorg/counterwallet-quick-access-recovery-tool development by creating an account on GitHub.
-
U can use this tool to recover the 12-wordsā¦. Also sweep in counterwallet doesnāt work⦠use freewallet.io desktop sweep if u want to sweep all assets balances/ownership in a single tx
-
I thought I had heard sweep did not work and was leaning towards freewallet but it seemed it would be a few steps, will check out tool
-
this will work locally I assume
- 05 December 2022 (3 messages)
-
Yup, it should.. also thereās a link to run direct from GitHub
-
-
Counterwallet sweep does sends one by one⦠freewallet does the CP sweep which moves all in a single tx
- 08 December 2022 (23 messages)
-
-
Hello everyone! Helene referred me here. Her and I met back in 2016 when we were anxiously awaiting the launch of SoG. As a constant user of your platform I wanted to say thank you for the work you do.
Iām actually here on the behalf of Ryo Fougere and Herckeim. You might recognize their names from being some of the original SoG artists. Weāve been building a community for a project called Monster Book for the last year now. And weāve amassed a great group of historical NFT collectors. Helene brought up the great point that we should consider following the roots of the artists and SoG and launch Monster Book on XCP instead of ETH. Iāve spoke with Ryo and Herckeim are open to the idea. Weāve just got a few questions around functionality such as wanting to randomize card distribution and prevent rarity sniping, etc. Is there a good resource here to talk to about this?
I appreciate any time and insight you can spare. If you want to take a closer look at the work we are doing please see our white paper https://kamn8r.medium.com/monster-book-83cc6859afafMonster BookFrom the mind of Rinaldo Wirz comes an immersive world of watercolor monsters
-
I think @pataegrillo may have some ideas how to help with the functionality you want to achieve for card distribution
-
Do bitcoin scripts, like time lock, work on Counterparty?
My guess is NO because tokens are linked to addresses, not UTXOs. ?? -
NFT Royalties āVillan-Speculators or Villan-Marketers? Efficient Marketing Hypothesis (EMH)
In the frenzy of the 2021 bull run countless artists, musicians and creatives were onboarded to various NFT platforms. Some of theā¦
-
@theogoodman makes a good case for vesting. Would be awesome if bitcoin scripts could be used to timelick tokens.
-
Got this question and not sure if there is a limit:
-
"do you know if there is a max number of sends that one can do in a multisend?"
-
1000 I think you will find is the limit
-
Is that a fixed limit or just the biggest send to date?
-
-
we just put out an update last night which fixes some issues with mpma to make it more stable sending up to 1000 assets and reduce the tx fees paid in data encoding by like 50%+.... I still have to make some updates to freewallet when I return from bora bora next which should make adjusting the fee on the first MPMA tx much more straightforward than having to go in and manually adjust the minimum tx fee in settings->preferences->minimum fee
-
-
Ok cool i have seen a 1k send but disnt think there was a hard limit im tempted to try a 1001 send just for keks to see
-
-
Yh thanks for bringing itnto my attention :)
-
hi, i am developing a game called rarepepeparty, my plan is to distribute the cards through booster packs. Technically speaking it's simple, I have a list of cards with different rarity levels (just like you), every time someone buys a booster I fill the booster with commons, uncommons, epics, legends, etc. and then I'll use mpma send to distribute them at low cost
-
by the way, yes, there is a 1000 limit in a mpma send
-
So I 1000 should be cool or the dev work that jdog was going to do still has to happen?
-
-
yes, the limit is already in production
-
since months ago
-
n time lock maybe
- 09 December 2022 (2 messages)
-
is it / would it be possible to multi sig token ownership
-
99% sure it works with 3.. msig.
Im using 3 msig with electrum for tokens transfers. With a custom script for opreturn data. Should be no different for issuances. - 10 December 2022 (1 messages)
-
Joined.
- 13 December 2022 (1 messages)
-
Counterparty-lib 9.60.1 released! | Counterparty
Today counterparty-lib releases version 9.60.1 which includes a number of bug fixes, updates, and new features including: Fixed full-parse / reparse issues - [more info] Bumped Bitcoin Core version to 24.0 - [more info] Added `validate` action to fednode to validate counterparty database integrity - [more info] Added `--no-cache` option to fednode to handle rebuilds
- 14 December 2022 (10 messages)
-
bitcoin 24 was never officially released and was replaced with 24.0.1
https://github.com/bitcoin/bitcoin/releasesReleases Ā· bitcoin/bitcoinBitcoin Core integration/staging tree. Contribute to bitcoin/bitcoin development by creating an account on GitHub.
-
There is a need for more developers involved in the repo. There is a discussion about this: https://github.com/CounterpartyXCP/federatednode/pull/337Bump Bitcoin Core version to 24.0 by jdogresorg Ā· Pull Request #337 Ā· CounterpartyXCP/federatednode
Federated Node Build System. Contribute to CounterpartyXCP/federatednode development by creating an account on GitHub.
-
-
Oh ok, still you (and every developer in this group) should be involved in GitHub.
I also noticed that v24 was not listed as released in the bitcoin core website. And I still believe Counterparty should not be updating Bitcoin Core unless there is a specific reason to -
I think we all know by now about your opinion regarding Bitcoin Core updates. There is no need to repeat this over and over, as you are not adding any new insights. Please abstain from harping on this any more.
-
looks like bitcoin 24.0 was never packaged up into a 'release' on github... but, I can assure you it was released and is on bitcoincore.org at https://bitcoincore.org/bin/bitcoin-core-24.0/ .... Thanks for the heads up on 24.0.1 tho... I'll spend some time testing it on the xchain servers and will bump to 24.0.1 in the next release if all looks good šš
-
Good to know you are reading the repo, because this is my first time mentioning this in this chat
-
Bump bitcoin core to 24.0.1 by jdogresorg Ā· Pull Request #345 Ā· CounterpartyXCP/federatednode
Federated Node Build System. Contribute to CounterpartyXCP/federatednode development by creating an account on GitHub.
-
Most of the people in this chat room are also in the main XCP chat so are already aware of your views regardless š
-
- 15 December 2022 (5 messages)
-
Joined.
-
Hey hey why i miss this place
-
Jdog thx for sweep opreturn patch))
-
It hard understood how binary split for text hex and flags field)) new is simple and reusable)) you see all honeypots was cleaned from old assets))
-
I suggest counterpartytalk forums
- 16 December 2022 (14 messages)
-
Joined.
-
-
Comparing to https://xchain.io/block/765233
-
-
exactly what did you see?
-
These show the last block the hashes match between explorers:
- https://www.xcp.dev/block/765233
- https://xchain.io/block/765233
But from the next block, 765234, these no longer match:
- https://www.xcp.dev/block/765234
- https://xchain.io/block/765234 -
hmmmm, i don't know if I'm doing something wrong, but I see hashes in 765234 are exactly the same
-
-
-
-
definitely weird, AFAIK there were no changes to xchain server. Try to force a page reload
-
-
Strange..... I'm working on xchain backend updates for the next few days... once that is all done, i'll spend some time digging into this.
-
- 17 December 2022 (1 messages)
-
Joined.
- 21 December 2022 (18 messages)
-
Joined.
-
gm, is it cool if I hang here?
-
-
Hello @jdogresorg have you been able to look into this? It is weird because now I also have a second v9.60 node (with waaay faster sync!) and this one now has the other set of hashesā¦
-
I have not had a chance to look into it, I am still working on the server migration (taking longer than expected, and have to perform some xchain SQL optimizations, as some of what I was being allowed to get away with by running local mysql instances, I am no longer allowed to get away with using a mysql cluster).... I am not ignoring this issue, I am not working on ANYTHING else related to xchain until the server migration / optimizations are complete (got lots of ppl DMing me for updates the past week... your not alone in having to wait).... Once I get xchain back up and running on the new infrastructure, I for sure will look into this issue.... block hashes should match in Bitcoin / Counterparty / XChain... if that is not the case, then something is amiss and we should most definitely get it fixed.
-
Also working on some dogeparty updates in prep for the new 9.60.1 release..... getting all the fednode / no bootstrap / full parse updates that fednode/CP got.
-
Out of curiosity, how long did a full sync take you? It definitely is much faster with that index issue fixed š
-
-
-
Yes this is essential. Iām waiting on this before I start writing transactions based on my own node. Iām still in read only mode so is not a problem yet, but once I start writing I want to be sure to do it in the right version
-
Just so I understand the issue... Bitcoin and CP block hashes match... but the block hash displayed on xchain is different?
-
The difference is in the Counterparty ledger/txlist/messages hash.
The last block with all hashes consistent is 765233:
- https://www.xcp.dev/block/765233
- https://xchain.io/block/765233
- https://host4.xchain.io/block/765233
But from the next block, these are no longer consistent:
- https://xchain.io/block/765234
- https://host4.xchain.io/block/765234
Notice how in xchain host4 hashes are different from the main one. And I recently discovered the same difference between my first v9.60 node and the new one. -
re: differences on different xchain servers... that will be resolved when the infrastructure update is complete (will be running ONE mysql cluster database versus a separate local mysql database on each xchain server)
-
re: ledger/txlist/messages hash differences... I believe javier said those are different because we determined that the ordering of a few records in the database was different between the old database and the new full-parse database, resulting in different hashes being produced.... but he verified that all the credits/debits/transactions in all the blocks matched... so all the data in the database should be the same
-
@pataegrillo should be able to explain a bit more in-depth... but, your correct, there are ledger/txlist/message hashes which differ between old database and new full-parse... but AFAIK it is just different hashes, not different data.
-
-
In fact, I experienced myself this order detail. But it got fixed when I fix an order match before that. So, there must be something else. I can compare your database with the current one and tell you the differences so we can catch what's going on
-
Thanks for the context.... FYI we did put out 9.60.1 around 3 weeks ago, and it included the new bootstrap which was generated from a full-parse... but no, no consensus changes in 9.60.1... it just a maintenance release and a bootstrap update.
- 22 December 2022 (2 messages)
-
-
- 23 December 2022 (1 messages)
-
Ah. I do not have my own node. I'm simply attempting to figure out how to verify ownership of a wallet so that a user can play with their cards
- 24 December 2022 (3 messages)
-
Spent some time looking into this, and I think there is nothing specific to Counterparty.
Search ābitcoin sign verify messageā and that should lead you to solutions.
But there was once a Counterparty project related to this, but it seems abandoned: https://github.com/AuthpartyioAuthpartyioAuthpartyio has 7 repositories available. Follow their code on GitHub.
-
Check freeplayer.io ā¦. It does message signing in freewallet to authenticate address ownership n then loads address balances/tokens/content
-
Description of Authparty authentication scheme which extends the counterparty: url scheme to support actions and callbacks
Description of Authparty authentication scheme which extends the counterparty: url scheme to support actions and callbacks - QR_Authorization.spec.md
- 27 December 2022 (1 messages)
-
Joined.