- 01 August 2024 (1 messages)
- 06 August 2024 (8 messages)
-
has anyone done a multisend successfully lately? -
nop, 2nd tx keep failing -
yeah just had that same issue using freewallet although i was able to create the 2nd tx with the API so just need to figure out how to sign it now
-
ugh error sendrawtransaction RPC error: {"code":-26,"message":"mandatory-script-verify-flag-failed (Script evaluated without error but finished with a false/empty top stack element)”}
-
just tried another one, same issue
-
guess ill just do 100 individual sends now 😩
-
ok was able to do 20 send batches at a time and they all worked
-
latest version of freewallet using tokenscan servers
- 07 August 2024 (1 messages)
- 08 August 2024 (16 messages)
-
Where is the appropriate place in GitHub to discuss the planned protocol changing release holistically/in general, not about specific features/issues?
https://github.com/CounterpartyXCP/counterparty-core/milestone/23 doesn’t have comments…
Maybe open a discussion https://github.com/CounterpartyXCP/Forum/discussions ?v10.4.0 (Protocol Change 1) Milestone · CounterpartyXCP/counterparty-coreCounterparty Protocol Reference Implementation. Contribute to CounterpartyXCP/counterparty-core development by creating an account on GitHub.
-
I agree. But I also believe there should be a place to discuss the protocol changing release in general.
-
The goal is the discussion itself being in GitHub, not on a chat
-
I cannot disagree with you, on specific features.
But these is a reason we have a discussion forum (which used to be the CIPs forum). We don’t even have CIPs any more, so I believe the open discussion space (in GitHub) is even more relevant now.
I guess I should just start something in https://github.com/CounterpartyXCP/Forum/discussions
Agree?CounterpartyXCP/Forum · DiscussionsExplore the GitHub Discussions forum for CounterpartyXCP Forum. Discuss code, ask questions & collaborate with the developer community.
-
I’ll open the discussion… but later
-
Adam and/or Evan, Can you speak on taproot in regard to counterparty and the future? Asking for a friend. Thanks. -
Are there any plans for supporting taproot? Your thoughts on taproot in general?
There were historical talks that I could have read or referenced, but those thoughtful comments were deleted from the CIP forum. -
https://github.com/CounterpartyXCP/counterparty-core/issues/1241 looks like the goalpost moved to 10.5. So not any time soon, no worries. That answers the question. Got it. Thanks.Taproot address support? · Issue #1241 · CounterpartyXCP/counterparty-core
Taproot (bech32m, prefix bc1p) and multisig* seqwit (bech32, bc1q) are not supported by Counterparty. Should we add support? A challenge is that addresses use up 1+20 bytes of Counterparty messages...
- 09 August 2024 (23 messages)
-
Imo these are way too many changes in a single release. Will make a discussion about it soon and link it here..:
-
Can’t wait to read it! -
Thinking about it… and maybe is better not to set any expectation. I’ve said enough already and I’m sure the people involved in the repo (and the dev chats) already know.
So don’t wait for it 😉 -
Probably best. Send in some pull requests instead.
-
There’s certainly a case for putting many consensus changes in one release as to avoid having more consensus updates in near future releases. It’s the same issue with stamps. We have some stakeholders that take 10 weeks to implement any changes and many time released consensus changes would be way too time cumbersome. I get that testing these changes manually one at a time is easier but that’s what the tests are for. Get it over with, fix any minor issues that may arise in minor releases and work on the next big things asap. I know I didn’t have time to deal with pushing all the recent CP updates right away and wouldn’t want to be bothered every month or so unless critical. We trust in the creators imo.
And to prior questions posted, yes the stamps indexer, explorer, and wallet/trx creation functionality are all open sourced at this point. Pushing forward to support the CP atomic swap capabilities as soon as they are ready to mutually grow the CP ecosystem along with the marketing power of stamps immutability. Not to mention full support of named CP assets as stamps. Among other things! -
This rust parsing is badass btw. Scrambling to get that on stamps. Makes me wish I just started it all in rust
-
We talked about this in the other chat and have the same answer: I agree with your logic if all changes are non-controversial. But not if there are, because then it becomes a strategy to force them.
-
PROTOCOL MINOR UPDATE: V9.61 · CounterpartyXCP/Forum · Discussion #124
Let this be the space to discuss the next protocol-changing release, a consensus hashes affecting PROTOCOL MAJOR / MINOR UPDATE. Federated node operators, separate from the develop- branch leader, ...
-
It was a joke. I’m ready for CP 2.0
- 10 August 2024 (13 messages)
-
I had similar problems but with a different location for the btc blocks dir. Keep us posted or come back for more. Node system architecture might need a good conversion.
-
Nice. Congrats. Care to share your build specs?
-
the desktop i use to run a local node has turned into a minecraft/fortnite machine for my kids
-
might have to pick one of these up
-
yeah, thats fine, can never have enough 2TB ssd’s lol
-
Thats a full BTC node and a working counterparty node?
- 11 August 2024 (1 messages)
- 12 August 2024 (1 messages)
-
Joined. - 24 August 2024 (1 messages)
-
Joined. - 26 August 2024 (1 messages)
-
Does anyone have connection to creator of the Umbrella project that can connect me with? THank. - 29 August 2024 (1 messages)
-
UnspendableLabs (@UnspendableLabs) on XHello, world! Announcing Horizon Wallet, a modern @CounterpartyXCP wallet! To be released Soon(TM).
- 30 August 2024 (2 messages)
-
I believe this is the Umbrella creator (though, reminder, UMBRELLA is now recognized as the 3rd asset of it's type...): https://twitter.com/LiteBitCoLite₿it ∞/21M ☂️•🏃♂️•💣 (@LiteBitCo) on XHusband, Father, Architect | #Bitcoin Content: @xbtpaul | #dyor x (#dca + #btfd)
-
Joined.
