- 13 May 2024 (307 messages)
-
Sure but if they’re doing that then they likely have at least some knowledge of what they’re doing
-
-
-
-
Won’t help. The people social engineered on that call were Bitcoiners already and had to have had at least a basic understanding of key mgmt. you can’t be in this space for very long and not absorb anything at all. Social engineering works for a reason. People compartmentalize things in their brain and don’t act rationally sometimes
-
I think this is a good case for multisig. Make it hard and time consuming to retrieve your keys. You wise up before getting scammed
-
I literally look at number 5 and I’m convinced it’s 8 multiple times a day
-
-
-
Yeah that one seems crazy to me. I think when something is presented as being “urgent” the rational part of your brain is bypassed
-
Or the tax agency calling you and saying you owe money and it must be paid in Amazon gift cards or crypto. People fall for that shit lol
-
-
Imagine if just sending Bitcoin to your own address could make you lose $1,000’s
-
Jdog made a hash, hex and BTNS transaction decoder for tx signing: https://jdogresorg.github.io/BTNS-Decoder/
the tool is really helpful, but this is a very scary possibility for users.... as browser eth/sol/etc wallets get drained in a similar way all the time for inexperienced users
having something superior to metamask (which doesnt always interpret the data in any "ELI5 readable format" for users) would be a huge help for the wallet side of things -
-
hopefully one day counterparty unpack() will support all message types
-
-
-
-
i know of this one: https://jpja.github.io/Electrum-Counterparty/
-
-
-
-
-
-
-
having a descriptive decoder in wallet would be crazy awesome....
on the edge here for my understanding.... but the most confused i see users (and me) get is decoding MPMA data with the extra addresses attached to the tx... alot of users see that and wonder what the heck is going on
example: https://mempool.space/tx/44299d89ec5d4cdb83757af4c7ab3f6681c3697e58707bb67e05b0b7c49dd52bBitcoin Transaction: 44299d89ec5d4cdb83757af4c7ab3f6681c3697e58707bb67e05b0b7c49dd52bExplore the full Bitcoin ecosystem with The Mempool Open Source Project®. See the real-time status of your transactions, get network info, and more.
-
mpma is hard .. JPJA not addressed it yet and I building on his work
there are 2 counterparty messages to decode and neither supported by unpack() afaik -
-
something about counterparty i have always loved is that users are expected to learn more about the basics of how bitcoin tx's work and how to use different features..... out of all the Antonopolous talks... all the news articles, all the twitter posts.... none of them came close to the education that xcp wallets taught me about reading txs
-
-
The elephant in the room is that the “core devs” are in a hurry. Dispensers are supposedly “stopping them from perfect engineering”.
They forget this is decentralized. Or they don’t want it to be.
And I’m dumb by considering usability. They are the geniuses.
And they think I care about their shitty reactions. Without answering questions. Tell me where I’m wrong. Which I can be, and don’t mind being corrected.
And some personalities in the ecosystem pretend to know. Like me obviously. But at least I think by myself. These other people, are all about narratives and choosing the “most likely side to win”.
I’m pretty sure if the “core devs” were supporting not requiring a prefix and not hard coding txns into the protocol, these personalities would also be.
I learn a lot from the PEOPLE we are dealing with in these discussions. -
-
and the first error message almost every artist sees here is this: "Error composing send transaction via API: Insufficient BTC at address [Your BTC Address]. (Need approximately 0.00XXXX BTC.) To spend unconfirmed coins, use the flag --unconfirmed. (Unconfirmed coins cannot be spent from multi‐sig addresses.)"
-
-
-
-
-
-
-
-
-
-
-
super common question in fw chat
-
-
-
seeing "3CD1Vf".... on an xcp tx when you cant use those types of addresses in your xcp wallet.... and the user is like.... huH?
-
-
This call just came in
-
record it like Junseth
-
no its the beginning characters of the 2nd address in the mpma send in the mempool tx i linked
-
-
-
-
😂 this is exactly what I’m talking about. Only the rocket scientists want no prefix to do rocket science shit
-
multi send error · Issue #1383 · CounterpartyXCP/counterparty-core
having a problem doing a multi send... getting this error It looks like my "second send" gets hung up or something... im barely technical enough to find the github... i was directed to pu...
-
I am not against a prefix
-
use a confirmed tx1 and you won't have issues
-
but it is so hard to track down and we have almost no debug data from the users when this happens.... been on the ready if i see it again.... but havent heard it reported in months now
-
what does this mean
-
make a mpma send low fees n you will get the error I bet
-
it means you do half a mpma send n wait for a confirm
-
-
hmm maybe it had to do with FW versions before sat/vb estimates then
-
-
Me neither… but I do think is cool that it works without it.
And I like that the BTC send itself is the command. No other steps.
And, understanding that dispensers are the most widely used way to buy assets, we should not break them without a proper transition period.
But I’m dumb, don’t listen to me. -
i also think its super cool
-
-
you can't do half a send with freewallet .. you must use the api .. freewallet looks for tx1 in mempool/blockchain n if it can't find it fails
-
-
the face he makes when he steals ur gurl
-
-
Speaking of dispensers. John opened a number of dispensers for a fleet of spaceship in-game assets. They’re still open and relatively cheap. Would be cool if someone eventually make the game
-
2 weekz
-
Just to let you know guys the game is in active development, we've been migrating to 3D and adding a 3D Bar scene (the ambientation of the game) that's gonna be used for menu navigation. Please let us know what do you think of the looks so far. 🐸
-
-
-
Different game. That’s the Pepe one and it’s been in development much earlier than 2022
-
tHeY tOlD mE tWo WeEkZ
-
-
there was a rarepepe card created to fund development of the pepe game ..something about danking was written on it
-
-
They're all sub-assets of : INFISPACE if anyone is curious
-
you'd really use different xpubs
-
yes a different derivation path would be a different xpub
-
and whatever the first wallet dev chooses as the alternate path will become the standard until the end of time
-
I am not so sure you can rightly blame Counterparty because you forgot you opened a dispenser on your own address.
Counterparty is only doing what you asked it to do .. computers are like that they do as they told .. even if its illogical , especially if its illogical but that was what was programmed.
this is why I nice to be able to open dispenser on a empty address, one assigned to dispense not to be used willy nilly -
Depends on the objective. Risk free trading (psbt) or compatibility with ordinals?
-
-
oh sure I just mean have different "accounts" so in the coin selection process you don't accidentally send your xcp assets
-
-
this is for utxo binding in particular
-
-
-
-
yup you got it!
-
-
wasn't trying take credit for your work lol.
-
-
that's a tooling issue and should definitely change
-
as a wallet developer, i am stuck with the original counterwallet derivation because people want to use their current wallet
-
and if i make any changes then its no longer compatible with other wallets
-
-
of course
-
but thats the compatibility issue
-
-
Them love their addys!
-
exactly
-
-
its not ideal obviously, but i dont have the energy to campaign for everyone to use something different, even if its better
-
id rather people just use a hardware wallet
-
then the hardware can tell the wallet what derivation path it wants to use
-
-
not surprised, its been around for a while
-
-
and there is a real switching cost to users
-
especially if they have a lot of utxos
-
-
-
this is a classic case of calling a bug a feature. dispensers aren't addresses, so why on Earth should a user expect that sending bitcoin to their own address would result in the loss of funds
-
this is just a bug. it's easy to fix and apparently accounts for huge losses of funds.
-
-
if I send myself bitcoin i'm sending myself bitcoin.
-
-
i can't believe that we're not okay with blaming users for using a Bitcoin wallet to make a Counterparty tx but we are okay blaming users for using features as designed and losing money *in a completely avoidable way*.
-
-
-
yeah, that is an unreasonable expectation and is totally unnecessary.
-
It's just a bug. There's nothing inherent in the idea of dispensers that requires you to lose money when you send yourself BTC, and I'm genuinely confused that it is just accepted.
-
you don't lose money directly you inadvertently send a token which may or may not be recoverable.
I accept i was lucky it was my address I used not a exchange one ..
its only accepted because that's the reality of the way it functions and changing it is beyond the ability of most -
it will be fixed as a direct result of making dispense a regular Counterparty tx, the resistance to which seems to come down to the idea that it's a user-hostile change
-
-
That's how Counterparty works in general lol
-
also it can be viewed as user hostile because it's a change to the status quo and if a user using electrum or a trezor or a ledger etc etc buys from a dispenser after the change they will lose money as they won't get the token they thought they purchased because they now didn't actually purchase.. this is why some transition time would be great .. .. they will now need a op return which is no biggie if you know but is a problem if you don't
-
this is why activation doesn't take place at the same time as the release. and every mandatory upgrade risks loss of funds and counterparty has had a ton of mandatory upgrades
-
-
-
Would you rather not have conversations?
-
-
Everyone said they are okay with it besides Chief but that was days ago before lots of discussion
- 14 May 2024 (237 messages)
-
yes, it's been pointed out, we do have a common situation where users send a counterparty asset (single) or MPMA (multiple) and the fee calculation turns out to be undercooked, and the tx requires a CPFP.
So we go to electrum to boost the transaction with CPFP.
I think we are a long way from being able to introduce any change to counterparty protocol attaching assets to utxo's only, due to the widespread current practices that will risk loss of assets on utxo's from non counterparty wallet transactions
It's good that the conversation has started, and we have Discussion 134 as a venue for that conversation to continue
https://github.com/CounterpartyXCP/Forum/discussions/134PSBT Support via attaching assets to UTXOs · CounterpartyXCP/Forum · Discussion #134CIP: XXX Title: PSBT Support via attaching assets to UTXOs Author: Derp Herpenstein Discussions-To: ?? Status: Draft Type: ?? Created: 2024-1-26 Definitions PSBT - Partially signed bitcoin transact...
-
You could make a cool piggy bank for kids with this too .. op_hodl stops em breaking it open and they get token each time they save, kids love collecting stuff
however the ground is still shakey so building atop counterparty when the rules keep changing is hard going, once the foundations are solid ideas like this can be explored further.
It works on a technical level at this time but not sure it will be possible once dispensers are 'fixed' -
You can't reason about the rate of change without considering how much work was done in the intervening time. More work has been done on Counterparty Core in the last 4 months than had been done in the preceding 8 years without a single protocol change.
-
True
-
but people here like to be arguing
-
They are not able to agree and that is not good for anyone.
-
They are making me reconsider my opinion about CP community.
-
It's really not reasonable to ask someone to maintain software that results in users losing money in avoidable ways and demand that he not fix them.
-
-
-
WE ARE GETTING OUR FUCKING ASSES KICKED.
CP probably had 200 TXs yesterday (guess).
Ethereum, Solana, others had 100,000’s….
We have a group of devs who want to push us forward to compete and are willing and wanting to do the work and yet some people here think we shouldn’t change at a fast rate.
It’s mind boggling. -
we need even new exchanges to attract more people , make some marketing etc etc ... normies can't use dispenser or exchanges like dex trade, too complicated for them
-
-
that will change.
-
Could have it so dispensers on empty addresses are treated like asset registrations .. in that .. yes there are sanity checks on the creation of txhex that leads to a dispenser opening ... but if you try and open a dispenser on a non empty address it fails is invalid just like if you try to register an already existing asset ?
then the user can only lose money if they do not use api to open dispenser and try n use a existing address -
-
-
doing something as someone else without their explicit permission is a bug, not a feature.
-
-
that only works by adding a 150GB database dependency
-
if I have my btc address posted on my Twitter handle and it has no activity it's still mine, and anyone can open a dispenser for anything on it.
-
The use-cases which will be eliminated are a priori attack vectors. That they _can_ be used non-maliciously doesn't magically mitigate the attacks.
-
-
Signature in OP_RETURN to prove ownership of address wouldn’t work?
-
Nobody has any issues with 99percent of the github updates... Everyone wants xcp tokens to be easy to trade on places ordinals are... We want it easy to run nodes
And for the specific update in question... Personally just had an issue with how it would be deployed for existing wallets.... Which looks like it can still be deployed while keeping existing wallet and dispenser feature infrastructure (which doesn't seem to be ruffling any feathers):
https://github.com/CounterpartyXCP/counterparty-core/issues/1784Alternative Dispenser Upgrade Path · Issue #1784 · CounterpartyXCP/counterparty-coreAdd a compose_dispense() (using OP_RETURN with the CNTRPRTY prefix, desired asset, etc. Have compose_send('BTC') (on both API v1 and v2) guess whether the TX should trigger a dispenser—if i...
-
-
If someone opens a dispenser at my address then if it starts dispensing I've profited from whatever this dispenser was for. The implications of that in the bad case are absolutely horrific
-
If you want to discount the attack vectors that's perfectly fine but wishing them away doesn't work, sorry.
-
-
was replying to this with previous message by the way
-
What if I don't actively monitor my addresses?
-
-
like this perhaps?
-
Sorry it’s a long thread, maybe I missed something
-
-
Can you explain why this feature is so valuable?
-
When I first started using them it was confusing
-
-
Saves money and time. You don’t need to transfer bitcoin first and then open the dispenser
-
-
-
In the proposed solution, you would be able to open as many dispensers as you want on your origin address
-
Ah okay
-
-
how would better hardware wallet support not help solve that issue?
-
Is there a large use case with p2sh for dispensers atm?
-
Would require two txs
-
no as the docs say p2ms only p2sh not supported but jt works
-
-
-
Interesting, so you have done some tests with p2sh and are able to successfully manage cp assets with some workflow of yours?
-
This is a very interesting use case
-
-
-
-
-
-
The thing that makes this discussion incredibly difficult is that opposition to change isn't principled. What we're talking about is an incremental change to a feature that is by far the most radical change to Counterparty in its history. Dispensers changed Counterparty's tx model, changed its trust model and opened up all sorts of novel ways to lose money.
-
I agree with this actually. We’ve already built a product for the nerds in here. We need to make XCP accessible. The reward is PEPECASH parity with that ETH garbage.
-
Dispensers are incredibly useful as they do not expire like DeX orders do they are great for on boarding new users too .. if we can make them better without loss of functionality then cool, but if it's totally impossible then it's impossible. I am not suggesting anyone attacks anyone else with malicious dispensers, just to be able to use them in a way that I can today .. I have set dispensers on hardware wallet .. i mean why wouldn't you ?
-
-
if you want a non-expiring dex order then why not suggest making a new message type or figure out a way to change the existing message? @teysol was doing all sorts of neat, novel experiments with Counterparty after it was launched and would love to do so again I am sure.
-
I wouldn't pay mind to them.... they are the reason why this shit hasn't grown
-
Haters gonna hate regardless
-
I put 100% faith behind the og devs over anyone else
-
a non expiring dex order is a great idea
-
Because behind every decision some people see the threat of tyranny
-
They always gonna push back and they also gonna cry low price and usage
-
Let's vote with our holdings
-
I got bags to back the dev team
-
The 100 xcp holders wanna hold shit up
-
lol doesn't work but I appreciate the sentiment.
-
Pfsh
-
Dev done more in 4 months then 6 years under anyone else
-
Dog kept the lights on, respect but that's it
-
Just keep dev'ing
-
Opening dispensers on cold hardware wallets is a reasonable use case and objection to changing the status quo.
That Doesn’t mean it shouldn’t be changed to fix the larger issues at hand, but it’s a reasonable request to try to keep it -
100 of them, or peeps holding more than 100xcp?
-
Don't forget unused votes are votes for status quo 😂😂😂😂
-
totally! features that aren't obviously exploitable should be kept if possible.
-
-
100xcp coin holders
-
Since dispensers can’t be opened on addresses with a history, unless someone shared and address or a key to recreate the addresses in the derivation path, it’s also not trivially exploited
-
-
-
if you want to get rid of the addrindexrs dependency you need to get rid of this limitation
-
Yes. Been discussed on the forums. 100 percent for it. But again... When PSBT and Atomic swaps I'm guessing it will matter less if the old xcp dex is used less
-
xcp dex is for xcp<>xcp and it works great but could probably be improved. atomic swaps are cross-chain basically
-
using keys is a good one as they not available if someone shares a address's that's never been used
-
Why? would that benefit them?
-
-
No iam saying people without conviction as they hold small amounts of xcp trying to dictate dev...
-
Ahh. I see.
Well, any consolation I in that crew and I'm ready for you cats to bring xcp to mainstream so it can devour the rest of these shitcoins once and for all.
Kill it guys 🪖✊ -
-
be nice if things like this additional functionality were available before other functionality is removed
-
Nice name
-
... the functionality that is being removed will not be replaced by the functionality that is added.
-
-
-
Daniel's my brother
-
lol how come that blow needs to be cushioned but not the blow where you send yourself btc and lose your counterparty assets? the lack of consistency is really bizarre
-
-
there is a proposal for this that was shouted down. it was considered not only unnecessary but unethical.
-
-
-
Ha who’s Daniel?
-
lol it wasn't me! https://github.com/CounterpartyXCP/Forum/discussions/135#discussioncomment-8431385Lock description · CounterpartyXCP/Forum · Discussion #135
This space is to discuss implementation of a lock description operation to ensure inmutability of assets
-
Danielson
-
-
Lock description · CounterpartyXCP/Forum · Discussion #135
This space is to discuss implementation of a lock description operation to ensure inmutability of assets
-
Looks like it was deemed useful and easy to implement
-
Ah okay. If the user sends dust in the same tx as the dispenser open to the otherwise empty addr in question, could that possibly work?
-
I dont fully understand the downstream effects and limitations resulting from removing addrindexers
-
well it removes consensus issues but w/e
-
What I was saying is, assume addrindexers has been removed, can something like my suggestion above work?
-
sorry was being snarky lol. I'd have to think about it.
-
I get that it is causing issues and should be removed
-
it definitely is useful and simple to implement but it made some people furious and it wasn't a battle I was willing to fight personally.
-
Shit id fight that all day.... Users have been asking for that for years
-
-
Forgot I even commented on that discussion. That's all I can do tho. Say my side of things and let it go from there
-
I'd love to add lockable descriptions but you've seen the fight over this current issue, which is much more serious.
-
The sats reside in P2WSH addresses... how is that not UTXOset resident... the Bitcoin protocol doesn't know they can't be spent, therefore they are unspent... no?
-
-
ahhh... my mistake... carry on
-
-
i think k your confusing the empty address and the prefix
-
they're two separate issues, both need to be addressed. both currently slated for the same release I think.
-
Pulling one comment from keyuno disagreeing with it doesn't instantly cause it to be 'impossible to move forward on'... Most of the other comments are heavily for that feature.
Every protocol change is different. You can't take a single comment of one proposal and say 'wee woo' no one can agree on anythingggg
... And as I mentioned earlier... Nobody has an issue with 'meeting both parties in the middle' after the dispenser discussion:
https://github.com/CounterpartyXCP/counterparty-core/issues/1784Alternative Dispenser Upgrade Path · Issue #1784 · CounterpartyXCP/counterparty-coreAdd a compose_dispense() (using OP_RETURN with the CNTRPRTY prefix, desired asset, etc. Have compose_send('BTC') (on both API v1 and v2) guess whether the TX should trigger a dispenser—if i...
-
there was a vitriolic discussion on Telegram. I don't recall saying "weee woo" but maybe I'm misremembering
-
exactly .. I never said to not protect users .. just to not make counterparty more risky to use with only hot keys
-
I also don't recall saying it was impossible to move forward on. I said I pick my battles and that one wasn't worth it to me personally. That doesn't mean someone else can't or shouldn't. The issue is that adding lockable descriptions would be a mandatory upgrade, just like removing the addrindexrs dependency/adding a prefix to dispenses
-
-
-
Get rugged 25 times vs 1. Great!
-
-
-
-
-
-
-
They can be done over a period of time....
-
The minimum you can make an unrugable dispenser is 60 min.
-
using CLTV.
-
Can an origin address close the dispenser of a source address?
-
resetting a asset is nothing to do with not seeing the value in 1/1s .. perhaps you have a divisible token you want not to be or a non divisible you want to make divisible
a reset does not create a historic 1 of 1 .. all transactions are on the chain so there is no pretending it wasn't reset
I fail to see why locking Olga is worse than it being spent ? -
Ask keyuno not me bruh
-
-
Why are you using Electrum!!! No! This is bad! Muy malo 😡
Joke 😂, I really believe this is cool. A design that favors usability. The code build for simplicity at the user side. Shocking, who does that?!?! Dumb engineers… or smart ones??? -
We are the first, and in Bitcoin.
Most others are centralized, VC backed and with fake (cheap to achieve) volume.
The arguments against the plan is about not BREAKING old ways before the alternatives are added.
And about not hard coding txns into the protocol. Don’t trust, verify.
This should not be much of an ask for the reference implementation of a Bitcoin messages (and transactions) interpreting protocol. -
Normies can’t use dispensers??? A buy by simply sending BTC to an address? So these don’t know how to send BTC?
And again, we should not be comparing with centralized services.
Let’s add the better ways. Then, with reduced usage of the stupid simple way, finally deprecate. -
Ninja Wallet, I've done bulk buys before
-
The cost of, don’t trust verify. Not a big deal IMO.
Storage is cheap. And this only affects nodes.
What will be the effect on nodes with the planned VM?
Obviously more disk requirements are not ideal. But there is no alternative if we want nodes to abide by the verification principles.
Full nodes. -
addrindexrs is required only because of the get_oldest_tx() call. removing it would get rid of the check that an address has no btc history.
-
-
Oh really address indexers is only used for dispensers, huh?
Funny, I seem to recall that addrindexrs predates dispensers and is used to look up the UTXOs which actually build the counterparty transaction. 🤷🏻♂️ -
lol, it's the only place where it's a consensus-critical dependency.
-
-
I've said before that it was made a consensus dependency and I left it implicit this time but if you'd like you can consider me "refuted"
-
man, people are stupid as fuck 😆
-
Tiny group of people trying to mentally drain founders & devs who have done more for this protocol in a couple of months than has happened the last 7+ years.
-
yeah that's cool feature but bulk buys need many outputs.. be cool to have just 2 outputs to buy many assets at many price points
-
yup. if you want Counterparty to ever get better, then please say so publicly... otherwise, the only voices that will be heard will be from those that have nothing better to do than spread nonsense and FUD
-
-
Is there a more empty characterization than the word FUD? Reason I try to never use it… even though is what is being done by the side that wants to optimize over any user concerns… or a transition period… or avoiding hard coding transactions.
We can literally hardcode the complete ledger and have CP parsing be as “efficient” as possible. Do we want that? Not me. -
is there a nice lil summary that simpletons like me would understand? I personally support progress as long as its good for my bags LMFAO
-
If Andreas Antonopoulos was in this group and just said "just chill bro and let the devs build" This senseless war of arguments would end. @jp_janssen
-
-
@nomchompskii I guess the point is that the currently debated issues should not be controversial because they won't have much of any consequences except for developers, and even then the effects will be minimal
the biggest user-facing thing being proposed is that there's a long-standing (and unplanned) flaw in the protocol that lets users use non-counterparty wallets to trigger a dispenser, which some people do currently use because of limitations in existing counterparty wallets. however, that same flaw has many serious consequences for the protocol and codebase and makes it easy for users to lose funds (cf big warning messages on xchain and multiple protocol hotfixes)
this should be an obvious thing to address, but some people are using the debate as an opportunity to pick silly fights on the Internet because it makes them feel powerful and their daddies never said they loved them often enough -
-
... use hardware wallets to open dispensers from a hot wallet.
-
-
-
the solution is better hardware wallet support, not keeping the protocol broken so anyone's pet use-case can still be done exactly as-is.
-
-
it doesn't but the question is why is that desirable outside of having to do 1 fewer tx?
-
and is 1 fewer tx enough of a reason for users to lose gobs and gobs of money needlessly?
-
-
-
Exactly
-
@nomchompskii there's not really much reason to dig deeper. it's either what Adam said or "I have my own way of doing things that is completely incidental to the feature that will be changed and my way of doing things will be disrupted so to hell with everyone else."
-
-
for the millionth time it's an attack vector. I understand your existing workflows will be disrupted but if that's enough of a reason to leave an attack unmitigated then there's no real point in trying to improve Counterparty.
-
-
-
will this require a protcool change?
-
-
if you have a proposal for how to keep your own workflows the same while patching the known exploits please post it on GitHub.
-
There's no reason to continue belaboring the points. You have a way of doing things you like that will not be possible if the exploits are patched and you'd like to find a way of keeping your workflows the same. That's perfectly reasonable but posting about it here over and over is not the way to find a solution.
-
If it's a choice between you not having to change your workflows and other people not losing insane amounts of money for a preposterous reason then we're going to choose the latter.
-
-
I understand the hostility to unverified empty addresses if they can be used to attack, that's is not why I want to use them, and i am willing to adjust my work flow, I don't know how else to prove ownership of a key except for to sign it .. there are some very clever cryptographers out there that may know different ways,
-
the best way to begin a concerted discussion is on GitHub.
-
-
tbc was only closed because we thought it was unnecessary.
-
If someone uses an unused address before you do, for example you post on twitter your btc address that has zero history? Doesn't seem much of an attack? Surely you wouldn't post btc addresses on twitter with zero history?
-
a donation address?
-
if someone starts selling something as you then you've just become an agent of that activity.
-
I'm sure any address would have some history before posting on X
-
And the likelihood of someone selling their assets on a address that isn't theirs is slim to none
-
If everything perfectly aligned, possible but highly doubtful
-
it's utterly trivial
-
sweep all socials, find any address without tx history and open up a dispenser as it
-
it's different from and much worse than a dust attack as you're not doing something _to_ somebody, you're doing it _as_ somebody.
-
I haven't heard 1 case of this
-
I am not sure what to say to that. An attack doesn't go away just because it hasn't been exploited. If this one is exploited it's really bad for the victim.
-
I think @XCERXCP did this to a Satoshi address.
-
It's much simpler than traditional identity fraud, e.g.
-
Maybe the attack hasn't happened because it is near impossible and damm right stupid as no gain to seller
-
Kind of a burn address in reality
-
People like to ruin other people's lives. People SWAT other people for the hell of it. Not all gain is financial.
-
Plz show me 1 example of someone's life been ruined by this so called exploit/bug
-
I have not claimed that someone has exploited this, I am saying they can, and that there are things that happen regularly enough that are similar to this for it not to be dismissed.
-
I understand that a culture has developed around Counterparty where risk has been discounted in favor of usability.
-
Your talking a risk of 0.000001%
-
It's an exploit: its severity is high, its probability is low, and it's trivial to do.
-
Severity high is debatable, as you can claim and prove that dispenser wasn't yours by on chain data
-
You'd have to prove you didn't control the origin
-
Plus you can cancel said dispenser
-
what if I don't even know what Counterparty is but one day I see a bunch of BTC at my address?
-
Then someone made u money, whoever sold the asset knew, buyers obviously wanted to buy
-
Is a lot of what ifs that have to align which is why not 1 case can be verbalised
-
Again.
-
Well I think that been able to set up a dispenser in a emblem vault or cold storage, usuabilty/compatible outweighs the near zero risk of this hyperthetical threat
-
it's been 5 days of arguing this stuff. The points have been gone over again and again. The point is you can't expect someone else to maintain software with known exploits and demand they not fix the latter. Who would agree to that?
-
You can create a issue with anything you want to fix
-
there is an issue for this.
-
-
Careful Dogestyle. You object too much and your told your FUDing n your daddy doesn’t love u😂
-
And I didn't read the proposal so I'm not allowed to comment
-
🤐
-
-
Periodic reminder…
-
Be very careful about anyone who contacts you with direct messages ….
always check with known community members to verify the identity of anyone before doing any trades.
Never send large sum first, always use an escrow agent. -
🥳
-
Yes, I did do this. I made Satoshi a few $1k
-
Still sat there?
- 15 May 2024 (74 messages)
-
I think you’re discounting the goodwill of the XCP founders.
They could have easily took the Bitcoin for the development of XCP but they decided not to due to concerns of breaking securities laws.
The same developers now don’t like the idea that someone else’s Bitcoin addresses can be exploited to cause harm. -
No I asked if the "exploit" probably only you have exploited, if the bitcoin in the few $1K is still in address, or did satoshi collect it
-
-
agree the solution has to be iron clad
-
The Bitcoin Office (@bitcoinofficesv) on X
The first capital raise in El Salvador on @Liquid_BTC is now live on @BFXSecurities And so begins a new era of capital markets for El Salvador. It is a small, exciting start to many big things to come for us, so stay tuned. In the meantime, more details on this project 🧵👇
-
-
-
-
I should say bona fides, rather than identity. I’ve come down with a bad flu, so I notice I am muddling some distinctions here and there.
-
-
Nex week we have a awesome event. We have registered more than 120 spain companies that will attend the event....
-
@teysol will tell us about CP and his experience building tech.
-
and I will talk about CP and historical assets.
-
-
without the proof of burn xcp is just another shitcoin
-
19/22 left in dispenser!
34 destroyed! Supply 1400
First Dividend created and will be sent out to all holders this week!
https://xchain.io/tx/7eccd8a8a9feb172fccadb2b7a692a6be947f72830d8c38ed6e0c2e92842970d -
Sad the current version of the protocol doesn’t “prove” (verify) it.
Is it nonsense to ask for this?
https://github.com/CounterpartyXCP/counterparty-core/issues/1791Hard-coded transactions · Issue #1791 · CounterpartyXCP/counterparty-coreI am reading there is a plan to hard-code dispense transactions, to remove dependencies of the software. We already have a hard-coded list of burns. My question (issue) is, why is this a goal for t...
-
-
you don't know what bootstrap means
-
-
I understand that people enjoy posting their stream-of-consciousness on the Internet but in case anyone is troubled by this blatant attempt to sow fear about Counterparty in a general chat where everyone may not be able to validate or invalidate what is being said: Counterparty has had a CSV codifying all of the historical burns since shortly after the burn was completed. It's a nice optimization that speeds up parsing and reduces code complexity in the reference implementation. Anyone can independently verify the CSV with either an older version of the software or a small script that I am sure @B0BSmith or @uanbtc is going to be writing any day now since they're incredibly concerned.
-
Then counterparty hasn’t been crypto since day 1 I guess
-
I think you should be able to validate any csvs used for check pointing etc, which you can right now of course, everything exists on chain
-
Everytime there is a consensus change there is a risk of unintended changes in prior history due to parsing bugs etc, so you should always be able to compare the ledger hashes from prior versions up to the activation block to be sure they match with the new version
-
With a bootstrap this isn’t what happens
-
That’s why Evan keeps saying “that’s not a bootstrap”
-
Counterparty didn't have checkpoints for 8 years and now all of a sudden people are worried about consensus lol.
-
Because with these new updates you reparse from genesis block
-
Its just a misunderstanding, I feel like I need to draw a diagram because I didn’t understand at first either why they aren’t really a big deal
-
Yeah I really don't know where the misunderstanding is so I can't help there, but it'd be great if people didn't post questions as statements insinuating that there is some conspiracy to make Counterparty's blockchain unvalidated.
-
-
-
it's genius: Ouziel and Adam volunteered 4 months of their time to reduce validation from 3 weeks to less than 1 day so that anyone can trivially validate its history and that's the Trojan horse by which they're going to make sure no one ever validates Counterparty's history
-
TIL. Thanks Bob!
-
Diabolical
-
If I were in the devs shoes this would drive me crazy. As far as I can tell they have
- good vision
- good execution
- good intentions
so what is the reasoning for the endless arguments? +1 for moving these kinds of discussions to github. There can be diagrams there. This format includes a wider audience than who can participate productively in these discussions, and so many of the responses are so low effort, repetitive, and fatalistic (and completely incorrect). that it honestly just seems like busy work for core devs. I would rather them devote their time to productive things. If people have real concerns, they should put real effort into counter examples that demonstrate their point, and sometimes people need to accept the outcome if the core devs have strong reasoning for their decisions. Then when a discussion repeats, we can just link to the prior discussion where it was hashed out and concluded. -
+1
Repeated trolling by a (very small) number of people are making some of the TG chats unnecessarily toxic and take away precious dev time -
I agree we can move the discussion to GitHub.
https://github.com/CounterpartyXCP/Forum/discussions/137Hard-coded transactions · CounterpartyXCP/Forum · Discussion #137Following up on CounterpartyXCP/counterparty-core#1791: My original question: I am reading there is a plan to hard-code dispense transactions, to remove dependencies of the software. We already hav...
-
-
-
Wts dm if any interest
-
starting to catch on
-
-
-
-
-
-
But how are we going to prove to ourselves we are decentralized without arguing or how are we going to deploy dispensers from our hardware wallet while still not being able send or do anything else relevant with CP or what about the people who can’t read messages on the block explorer or how are we going to put the child**** token on someone else’s address or what about not being able to rug ourselves with a simple BTC send to our own wallet.
Cmon man, think logically. -
Just FYI, spamming an issue board with a repeat issue that was closed with an answer already would get you banned from almost every open source project. This is not normal or acceptable open source etiquette. The idea that open source means everyone’s opinion is equally valuable regardless of their experience level or contribution is not how this works. Linus Torvalds still reviews every single PR that goes into the kernel, and chooses to add or reject each change. The mainline kernel is far behind all the forks because of this. If his internet is down and it’s too rainy to drive to a coffee shop safely, the release gets postponed (true story).
-
Why do people tolerate that? Because the results are obvious. He is the maintainer of the single most successful piece of FOSS software ever created, and people trust him.
-
-
-
-
Right
-
Jdog coming off as bitter trying to stir the pot against the devs who have done so much for us these last few months.
-
Even though they aren’t charging for their time, their time is valuable for all of us. I know they want to make people feel heard and listen to community feedback, but people should be more careful in how they communicate for the sake of maximizing dev time and avoiding draining all goodwill for the project.
-
-
Devs being drained of their good will by trolls, indeed
-
-
nothing new in that sadly
-
-
-
LordJamieVShiLL.eth (@LordJamieVShiLL) on X
Did you know when @CounterpartyXCP 2.0 goes live the Native gas token will be $XCP ? How’s your $XCP HODL bag looking these days anon?
-
-
I’ve heard Adam discuss on the Coval podcast wanting and his willingness to put in the work to make this happen
-
Ideally we abstract XCP into the background eventually so it's used but not by regular users. Users want to buy and sell in BTC without extra hurdles
-
I think that’s definitely possible at the tooling level: wallet auto-buys xcp on your behalf and charges you for the convenience of a seamless experience
-
Unless he is tarred and feathered first
-
I’ll be in Lisbon for the conference if anyone is attending. https://x.com/mikeinspace/status/1790816816853291207Mike In Space (@mikeinspace) on X
Get tickets here: https://t.co/KQhyq1FpC6
-
Oh cool. I will be there, but missing the party on the beach 😢
-
Same. I'm flying out early that morning.
-
-
-
- 16 May 2024 (34 messages)
-
15 to go! Basically free. Dividend going out this week to all holders. Thank you to all the holders of this piece of history. More to come!
-
Well that was said like a guy who knows what he’s talking about. Listen
-
Now I know why you said that’s not me in ucit. Chat. I was showing the Dank llc guys
Your full on old school og counterparty. Brainiac I figured you were super smart. Well articulated -
I can see how it’s hard to make happen but if expansion is an aspiration then ease of use for idiots like me would be advantageous to say the least !
-
Counterparty White Paper
https://krellenstein.com/adam/get/counterparty-whitepaper_2024-03-29.pdf
For the TLDR crowd (most of you?), here are some goodies I found in the "Future Development" section.
1. Deeper Integration with BTC
".....Counterparty will be able to provide seamless integration with the Bitcoin token: Counterparty assets will be able to be attached directly to UTXOs, allowing for them to be
held and transfered using standard Bitcoin wallet software."
" this upgrade will allow for trustless, atomic swaps between native Counterparty assets and BTC, such as Ordinals has. Indeed, it will be possible to trade Ordinals assets for Counterparty
assets as well."
2. Implementation of a General-Purpose Virtual Machine
"The Counterparty smart contracts language will address these limitations of existing systems, so as to bring general-purpose computation to the Bitcoin blockchain, and without the use of a sidechain. Naturally, XCP will serve as the gas token for computation and storage using this virtual machine, and fees will be dynamic based on network load." -
This isn't a roadmap, it's a whitepaper with ~no technical specifications. If we can't get consensus on fixing bugs in Counterparty because people are used to having them in there then planning on a radical architectural and value-propositional change like making Counterparty a general-purpose computing platform is unrealistic. It's also expensive; not something Adam can self-fund.
-
It sure looked good in the white paper.
Are we giving up already? -
Adam published a white paper on his personal website which mostly described how Counterparty works and spent a few paragraphs describing potential improvements to it. Atomic swaps are happening.
-
I loved the vision. I'd rather see people rallying around it and helping to find ways to achieve the vision instead of arguing over what seem to be minor issues and personality conflicts.
-
-
It comes down to means, opportunity and will. The point is just because Adam used the future rather than the conditional tense doesn't mean he made a promise or devised a plan.
-
Fundraising probably needs to happen.
Is this under consideration? -
Counterparty had no premine; funding protocol development is a well-known challenge.
-
Can I be added in BTNS chat? Thanks
-
This isn’t new ? There is a lot it unpack there though this would be the right place to do it for sure 👍🏻
-
What kind of coin we talking about?
Another consideration is this sort of change would take much more developer resources to maintain after the fact? What happens if the current dev team retires, we would need others to step up….
But I suppose if it was a huge success, there would be developers in line to join. -
-
You'd need a small team of experts indefinitely.
-
I'm working on it
-
-
Official BTNS Chat (EN)
This channel is for discussing the Broadcast Token Name System (BTNS) and the platform's features. Site: btns.wtf Wallet: t.me/freewallet_io Explorer: btns.xchain.io Twitter: x.com/BTNS420 English : https://t.me/BTNS420 Chinese : https://t.me/BTNS420CN
-
Happy to help....
-
Dispenser will be closed tonight and dividends sent tomorrow! Last chance to grab a DESECRATPEPE
-
I was thinking about an option instead of creating a new token we can do it "startup" style, although if we go with the traditional approach in crypto which is build a project > mint a token > raise funds > Has no sense
-
There is a more viable option to have the entire CP community participate. Create a collection of historical assets of all the OGs here who are willing to sell their historical assets.. thus raising funds for development marketing etc....
-
Of course all those OGs who are willing to sell will make some money along the way...
-
Sorry i pinned the wrong message.
-
i was just trying to do a multi send and this error came up. Anyone knows what it means?('b2e95f590fb213c5551ffc137cd530e06e0eef7d234bd5f42c4eec95086c7622', 0)
-
Anyone else getting this error today??
-
https://davestaxcp.gitbook.io/freewallet.io-user-manual/troubleshooting-issues/counterparty-api-communication-error
It has to do with your Server settings and enabling SSL to yes -
review your server settings for CP Host then.... newest update (for Reset to Default) is public.xchain.io and the other option is using api.counterparty.io .... also check your CP Port too
https://davestaxcp.gitbook.io/freewallet.io-user-manual/troubleshooting-issues/stuck-on-checking-data-encoding-fees -
I’m not very technical but was wondering, could this be beneficial to xcp as well?
https://scryptplatform.medium.com/trustless-ordinal-sales-using-op-cat-enabled-covenants-on-bitcoin-0318052f02b2Trustless Ordinal Sales Using OP_CAT-enabled Covenants on BitcoinOP_CAT meets Ordinals
-
looks like it has to do with something on the Counterparty API side of things, it is recommended to use the default server settings in v0.9.31:
https://davestaxcp.gitbook.io/freewallet.io-user-manual/common-questions-using-freewallet-faq/how-do-i-check-my-freewallet-server-settings -
Having an auction of historical assets with a certain portion of the sales revenue being donated to fund development would sounds potentially viable, as long as the donation percentage is not so high that it becomes a disincentive to putting up assets for sale.
If the auction is well promoted, it may also attract renewed interest in CP and the historical counterparty NFTs (the earlier ones are rare antiques from the perspective of the crypto timeline). - 17 May 2024 (9 messages)
-
I’d the auction was so bloody high then maybe it wouldn’t
-
It might do the opposite people would flock to the ones they could afford
-
Did a show primarily on xcp last night - https://rumble.com/v4vn0yl-rugpull-radio-ep-79-bitcoin-tokenization-is-the-future.htmlRugpull Radio Ep 79 - Bitcoin tokenization is the future & ends their rigged Wall St Games - 10:30 PM ET -
Thursdays at 10:30 PM ET Episode Archive: https://rumble.com/playlists/N6IFHf2pPm8 Rugpull Radio is a laid-back environment providing education on the most revolutionary invention humanity has ever cr
-
WTS
Physical PEPECASH coins
xchain.io/asset/HIPPIEPEPE.2024 -
-
Good read by the founder of 37Signals. Helps to articulate what I think a lot of people don’t understand about OS software.
https://world.hey.com/dhh/open-source-is-neither-a-community-nor-a-democracy-606abdabOpen source is neither a community nor a democracyUsing open source software does not entitle you to a vote on the direction of the project. The gift you've received is the software itself and the freedom of use granted by the license. That's it, and this ought to be straight forward, but I repeatedly see that it is not (no matter how often it is repeated). And I think the problem ste...
-
Tokenize the future indeed
A lot of billionaires talk about how real-estate has become tokenized for them once they hit a certain level. So a lot of them are moving value to bitcoin
How could you convince them that counterparty assets could be better ? -
great writer. I like this post https://world.hey.com/dhh/i-won-t-let-you-pay-me-for-my-open-source-d7cf4568I won't let you pay me for my open source
In Debt: The First 5,000 Years, anthropologist David Graeber explores the fascinating history of debt and economies. It starts out by debunking the common myth that prior to coinage, everyone were trapped in this inefficient mode of barter. If you had a chicken to give and wanted sugar from Gandalf, but Gandalf was a vegetarian, you ha...
-
Dividend sent!
https://xchain.io/tx/e98e0ae1a0ad623bdea73b36114a6ac0d8dc6f87b0e3261d872bfdfc78e5db25 - 18 May 2024 (152 messages)
-
Is CounterWallet no longer working?
-
-
What the next best option? Especially for mobile.
-
-