- 12 January 2024 (685 messages)
-
Every counterparty asset would benefit from this
-
As I'm usually quiet just trying to catch up, I'm bringing robot as useful contribution
-
I wont vote in his 'personal' poll with control of a "Project Dev" claim as it lends validity to his grandstanding. Leading people to still believe he is at the helm for the sake of their holdings.
-
Joined.
-
I do not feel in my heart of hearts that counterparty cannot come to a consensus, but rather that it cannot come to a consensus on what he deems valid to consent to
-
gm
-
-
We can broadcast and shame though.
-
Welcome
-
Big fan. Quite the honor.
-
Guys, what do you think about this.
Separate the parsing of blocks database from the core(We apply the principle of single responsibility )
we build a rest api on top of the database that we expose to the user(aplicamos el principio de responsabilidad unica)
we let the blockparse have the heavy tasks of writing to the CP database and reading from the bitcoin node.
we would use diesel.rs and rust mostly to build the blockparser.
and use actix.rs and diesel.rs to build the publicly exposed api. -
opinions?
-
This way it is easier to maintain, the blockparse is the source of truth that consumes the most resources and the rest API is the one that is exposed to the public. Just two services running on top of CP would allow us to add a lot of performance
-
sent you a DM ser
-
Okey dear ser
-
i like the apply of Single Responsability principle we did this way in the stamps indexer where each service just do one thing less the explorer and api that are in the same service
-
Joined.
-
it’s a party now!
-
More opinions like this are welcome.
-
What frameworks did you use for this?
-
-
Apir
-
I'm working now on some performance benchmarks (along with another couple of devs), but it's obvious there's a *lot* of low-hanging fruit in the codebase. And we could easily just have ton of threads serving API requests if we needed to scale horizontally. Splitting a single service up into multiple services usually slows everything *down*, because suddenly you're serializing and deserializing data and moving it around a ton unnecessarily. Scalability != performance, and we want to be able to scale counterparty-server without also slowing it down in the process.
-
Not really, since we would have a service reading bitcoin blocks and writing to the CP database, the other service (rest api) would only read from the database, not write... we could horizontally scale the rest api multiplexing and we could respond to 100's of thousands of requests per second
-
This can help to understand my point.
-
-
currently you are running everything in a single service, you are running the bitcoin node. parsing blocks, and responding to client requests.
-
This proposes a cleaner and more scalable architecture.
-
CP protocols would be implemented in the blockparser. etc..
-
I mean @teysol has designed & implemented a massively complicated system using SOA. I think he gets it...
-
yeah the issue there is in that diagram 97% of counterparty-server is in "Block Parser", and the right side of the diagram is the remaining 3% in a little library called api.py that is (1) definitely not a bottleneck, and (2) can be scaled perfectly well with very minor changes
-
Neutral, but a thought… Are we going out of our way to fix xchain in the process? Should we abandon the xchain/freewallet support idea all together for the benefit of the community??
-
-
Come back if you want to bounce more ideas in this area. I dont want to sidetrack you with my ideas. Good work.
-
A named stamper! Rtfo.
-
you're right about the percents. However, the data shows that the bottleneck is the way blocks are being parsed.
-
Fixing counterblock and counterwallet by proxy?
-
Now I have a doubt.
-
Counterparty2mysql is the black line in the middle for xchain
-
I found this gem in the codebase today 😂
-
What would happen if someone with a malicious transaction injected dirty SQL, is the tx data being sanitized before executinf a sql query?
-
Previous conversation where I wouldn’t allow the gas lighting and a friend comes up with a fix. https://t.me/Counterparty_Dev/9711mason in Official Counterparty Dev Chat
Logstash is your friend here imo
-
A Blue One in Official Counterparty Dev Chat
Good for low volume. I just took a look at script. Maybe a cron job or webhook push after a new block to a script that dumps the sqlite? Looping through is nice but here we are. Dump sqllite to MySQL then cleanup in MySQL after.
-
-
-
-
-
🤦♂️ all this nonsense over a database optimization, I mean I can run an LLM that contains a pretty full body of world knowledge on my iphone with good speed.
-
how big is this database?
-
8gb?
-
LMAO
-
no way
-
-
I really though it must be like over 100gb or something
-
On 10 mins block
-
hahaha
-
sorry, only half caught up on the actual issue.
-
this 👆 💯
-
-
Teach me
-
-
2016?
-
David Pissarra (@davidpissarra) on X
Run the Mistral-7B-Instruct-v0.2 model on iPhone! Supports now StreamingLLM for endless generation. Try the MLC Chat App via TestFlight https://t.co/NnyyhTcAPk For native LLM deployment, attention sinks are particularly helpful for longer generation with less memory requirement.
-
-
we should be looking for that performance....
-
really my bad, it’s like comparing apples and dinosauer bones or something, 2 different types of things.
-
They have an agenda.
-
To add to this
It’s worth noting that the with the Bitcoin max block size we’re talking about an average of a few thousand transactions in 10 minutes, assuming they are all xcp transactions.
We don’t need a Ferrari, we just need a fiesta -
And it’s not spam
-
yeah not comparable. the db is really small, the codebase is really simple and you're only writing a block every 10 mins!
-
Welcome
-
all the sql queries might be harder to recreate in postgres/mysql but heh there’s ways around that
-
And someone who can drive
-
https://github.com/CounterpartyXCP/counterparty-lib/blob/master/counterpartylib/lib/blocks.py
here all CP runscounterparty-lib/counterpartylib/lib/blocks.py at master · CounterpartyXCP/counterparty-libCounterparty Protocol Reference Implementation. Contribute to CounterpartyXCP/counterparty-lib development by creating an account on GitHub.
-
I just wrapped the entire database in an ORM model
-
one really nice and surprising thing having come back after all this time is that people aren't hollering for super fancy features. Counterparty's simplicity is what gave it an edge over competing projects in the early days, and philosophically it seems to have aligned with what the market wanted. Simplicity continues to be our friend. The codebase needs TLC and incremental improvements but overall functionally it seems to satisfy the community's needs.
-
Fluent Bit v3.0 Documentation | 3.0 | Fluent Bit: Official Manual
High Performance Telemetry Agent for Logs, Metrics and Traces
-
models2.py
1 file sent via WeTransfer, the simplest way to send your files around the world
-
yes. there's definitely functionality I'd like to see added! but there are a bunch of uncontroversial infrastructure problems to solve first...
-
See all the tables in sqlite in tje database
-
strong disagree. there *are* a lot of quick wins. and aggressively changing the dev culture of a cryptocurrency doesn't work. Heck, even the Hudson River Trading guys had to fall in line with bitcoin dev process.
-
-
-
doing a massive rearchitecture starting from first principles before any real profiling has been done doesn't make a ton of sense...
-
i haven't run git blame but my guess is that much of the codebase hasn't been touched in > 5 years
-
the test suite will help expose that as well
-
probably right
-
Keep it in mind though with every character change.
-
A Blue One in Official Counterparty Chat
He was tinkering with what was already there.
-
-
respectfully, I have already asked you for clarification in a DM.
-
-
- 13 January 2024 (674 messages)
-
I'm just realistic, CP for years did not receive strong development. no incentives, or devs building assets or improving the tech. Maybe in bitcoin it works because it has stronger economic incentives
-
y’all talking about counterparty yet it literally sparked a billion dollar NFT craze, we sold a rare pepe at sotheby’s for $3.65mil, measuring a protocol on the amount of development isnt giving you the whole picture
-
if counterparty suffers from insufficient developer resources then doing a massive rearchitecture which would require commensurate developer resources is... not a winning strategy.
-
A donation of 100k to the CP development would have been enough.
-
lol
-
that's just not true. source: founder and funder of counterparty
-
it's not a question just of how much money, but what it's directed to
-
Respectfully, this is open source software development. We can speak in the open and have already. Scroll up for my answer and stop sliding the topic and filling up the chat with politics. Got something to say, say it. I don’t have to respond and you dont speak for me.
This is your last engagement from me in this regard. -
If you ask me to improve CP's performance, I'll tell you my ideas. I am not saying that it is the fastest way to improve the technology and I am also not saying that 1 or 2 devs are required for this. Getting to work on my proposal is something that requires fulltime development
-
you should build an alternate implementation then
-
8gb, wow, that’s not bad at all.
-
I can do it, I can build a counterparty implementation in Rust or C++, the rules and protocol would be the same. nothing changes only the performance... Now the difficult thing would be to find people who are willing to support my proposal.
-
I am sure that python lovers will not want to support it.
-
you dont need support you can just build it
-
if its in consensus and better then people will use it
-
I have financed the construction of a wallet and I have spent around 78k just on development that will support CP... atomic swaps, dispenser and other cool stuff...
-
I won't do it if I don't receive enough support from the devs...
-
not sure what you’re asking, why wouldnt anyone support you doing something like that or do you mean financial support
-
if I receive support from some devs I can go ahead with the proposal to the community and seek funds to get that done.
-
gotcha, well normally you dont need a cosign, you just do it in the open
-
IMO the kind of issues adam's been making on GH are the exact right first steps. I especially like his most recent one: https://github.com/CounterpartyXCP/counterparty-lib/issues/1305Rough Plan to Fix Repo · Issue #1305 · CounterpartyXCP/counterparty-lib
Working on all of this with @ouziel-slama (!) Migrate to Python 3.11 Use the latest version for all dependencies Replace setup.py with pyproject.toml Add and document Hatch support Fix test suite B...
-
just normal QoL stuff. Get the repo back in shape and go from there.
-
obv there is some unique stuff about blockchains but a lot of what needs to be done is just regular TLC and best practices...
-
Bitcoin has a max tx/s of 7. If we cant scale to 10 decodes/db entries per second. Even with a stack of blocks in. Few minutes we are still looking at what, 100 per second? There is a maximum upper limit here and it’s pretty low.
-
ex: we need to upgrade from pytest 2.x to 7.x 😂
-
I wouldn’t be surprised if there a function thrashing the hard disk for every tx in a block when the whole block could be put into memory…
-
Work in the server side rendered xcpdev, integrated with the fednode, already started!
Working proof of concept: https://mdx315cagk.execute-api.us-east-1.amazonaws.com/
Repo: https://github.com/CNTRPRTY/xcpdev-ssr
Fednode integration branch: https://github.com/CNTRPRTY/federatednode/tree/xcpdev-ssrGitHub - CNTRPRTY/xcpdev-ssrContribute to CNTRPRTY/xcpdev-ssr development by creating an account on GitHub.
-
I’m sure Adam will find some gems resulting in a 10x speed up
-
@teysol spilled the beans in the issue but worth pointing out that we spoke with the earliest counterparty dev and he's agreed to help out with a lot of the issues we've been identifying 😁
-
(this is separate from the dev we'd like to fund to help specifically with performance work)
-
@hodlencoinfield not sure if you were around when Ouziel was working on Counterparty but he's a great guy, is intimately familiar with the codebase, and great to work with.
-
i just saw that!
-
i remember the name but i dont know if i ever had any interactions with him
-
Really great guy. I think he's a less experienced shitposter than most crypto folks but he'll learn.
-
It's good to start there. I'm still synchronizing my bitcoin node so I can help a little with the code and give my contributions..
-
@teysol If you think I can help you with any of those points just let me know.
-
FOSS
-
I’m looking forward to a true LTS version.
-
federatednode-counterparty-1 | [2024-01-13 04:41:20][INFO] Broadcast: bc1q0nhd5hqq04ds4ny7kfm35cxjzdm7g2rp3srg8l at 2023-12-11T06:53:00+00:00 with a fee of 0.0%% (071156b43179415a44deffd028711bd83075772df69e2ffc8f26fbd9c5630135) [valid]
federatednode-counterparty-1 | [2024-01-13 04:41:20][INFO] Broadcast: bc1q0nhd5hqq04ds4ny7kfm35cxjzdm7g2rp3srg8l at 2023-12-11T07:01:00+00:00 with a fee of 0.0%% (1a4fb9ef7fc3f4a4c8a022bedd1b192f17478965739ffe0626f3684b65d9d8db) [valid]
federatednode-counterparty-1 | [2024-01-13 04:41:20][INFO] Broadcast: bc1q0nhd5hqq04ds4ny7kfm35cxjzdm7g2rp3srg8l at 2023-12-11T07:02:00+00:00 with a fee of 0.0%% (8fa55c5a6a1c7aa826c8c986ca76498694c436ae5f974296879a88b6f2513abe) [valid]
federatednode-counterparty-1 | [2024-01-13 04:41:20][INFO] Broadcast: bc1q0nhd5hqq04ds4ny7kfm35cxjzdm7g2rp3srg8l at 2023-12-11T07:16:00+00:00 with a fee of 0.0%% (1bb15b6ea18daea487448d3df528c6a08184c979db2072cc50eedf8e0ab6aa3a) [valid]
federatednode-counterparty-1 | [2024-01-13 04:41:20][INFO] Broadcast: bc1q0nhd5hqq04ds4ny7kfm35cxjzdm7g2rp3srg8l at 2023-12-11T07:19:00+00:00 with a fee of 0.0%% (b1493465df89729d9f14009f69841b8df9227abea7fe76cbccb2712865cc6985) [valid]
federatednode-counterparty-1 | [2024-01-13 04:41:20][INFO] Broadcast: bc1qgzz7zr8t7jrhngzqfnz94s8metdr48w6pshhqs at 2023-12-11T06:47:00+00:00 with a fee of 0.0%% (bece08479e42ec59b2bbacc0760d3489840cc7f35d73c44a6e585b9e66f67e71) [invalid: feed timestamps not monotonically increasing]
federatednode-counterparty-1 | [2024-01-13 04:41:20][INFO] Broadcast: bc1qz26y3yxtpqgn44502mpp8evcpn8e7nc2yf7gxq at 2023-12-11T06:48:00+00:00 with a fee of 0.0%% (1e3e4ff894c9d28f142ddd560f88d54b580013711786ee7023b007ba1ce66086) [invalid: feed timestamps not monotonically increasing]
federatednode-counterparty-1 | [2024-01-13 04:41:20][INFO] Block: 820674 (56.40s, hashes: L:256c4 / TX:8dc70 / M:49e46) -
-
-
-
hahaha... wow...
-
incredible
-
-
btw, I don't mean to derail a technical discussion as this is off-topic, but I'm watching these 3 videos from 2018 and they have a lot of relevance to current day and reveal a history I was completely unaware of: https://www.youtube.com/watch?v=HyM8sx4JNUECounterparty Forks, Counterparty Foundation, and Consensus Failures (Part 1/3)
Intro/Outro https://www.youtube.com/watch?v=VfE1tWZjxv0 Part 1/3: https://www.youtube.com/watch?v=HyM8sx4JNUE Part 2/3: https://www.youtube.com/watch?v=vkfer0-SdWc Part 3/3: https://www.youtube.com/watch?v=Kjv8B7gSqxY References https://docs.google.com/document/d/1-VkIOjpFe6yX19B1FBhUOwCTEl0GLgeaAuDH1G7SZiM/edit?usp=sharing https://docs.google.com/document/d/13b2N8q0SnBpmLXpMJhFrK6UonaEvaT29m7iXdpjfKDk/edit?usp=sharing https://counterpartytalk.org/t/to-fork-or-not-to-fork-this-is-the-question/4233 https://counterpartytalk.org/t/whole-lotta-larpn-goin-on/4293 https://counterpartytalk.org/t/the-state-of-the-counterparty-project/4332 https://xchain.io/address/18BfbQ8kXcL8dwjYmX5fhyZs1YefxLFHG9
-
-
-
This is great
-
trip down memory lane!
-
A Blue One in Official Counterparty Chat
I have asked before months ago but it went unanswered, is there an official xchain chat?
-
So the funny thing about this is that JDog actually WANTED us to migrate SRC20 to broadcasts. That's why he wrote the BTNS protocol. Had we done that, xchain would have died months ago, it seems.
-
nice find! (I'm still getting my node up for this 😅) this is great news, should be easier to optimize!
-
-
Is BTNS a competitor to or an extension to Counterparty's token system?
As the CIP editor my first reaction was to reject the CIP but I gave it the benefit of the doubt.
What do you think?
https://github.com/CounterpartyXCP/cips/blob/master/cip-0028.mdcips/cip-0028.md at master · CounterpartyXCP/cipsCounterparty Improvement Proposals. Contribute to CounterpartyXCP/cips development by creating an account on GitHub.
-
can it be both? ;)
-
-
-
-
-
-
-
Ok i leave the BTNS proposal as "Draft". The alternative would be status "Deferred".
-
-
-
-
-
-
Informational CIPs explain ways to use the protocol, eg how wallets/ exolorers can make sense of json files or stamps.
Standards CIPs are for protocol updates. -
cips/cip-0001.md at master · CounterpartyXCP/cips
Counterparty Improvement Proposals. Contribute to CounterpartyXCP/cips development by creating an account on GitHub.
-
Right, but what does it mean to "reject" an "informational" proposal? 🤔 IMO it shouldn't be anyone's job to tell people how they must or must not use counterparty (any more than it should be someone's job to tell people how to use bitcoin). in fact, it *can't*, because counterparty is a permissionless protocol
let's distinguish carefully between discussions of actual protocol changes (which affect everyone!), of the reference implementation, and of *other stuff*, and keep them as separate as possible
that will help focus our discussions and cut down on controversy dramatically -
"i reject your reality and substitute my own"
is what JDog is doing to Counterparty with BTNS -
"Reasons for denying CIP status include duplication of effort, being technically unsound, not providing proper motivation or addressing backwards compatibility, or not in keeping with the Counterparty philosophy (as determined by a majority of the project maintainers as defined below)."
The latter is why i considered rejecting it. Counterparty is built around one name system/token standard. It is unclear if BTNS builds on top of this or is a competing standard ??? -
-
-
-
JP, I think maybe the question is, for something like BTNS, not why hasn't its CIP been rejected, but why has it been made? You can do it without changing Counterparty at all (as evidenced by the fact that its being done), so it's not really a proposal... it's happening.
-
same goes for Stamps stuff.
-
A useful analogy: imagine if we made a BIP for Counterparty 😂
-
-
-
but, like, he's doing it as we speak, right?
-
-
if his CIP were rejected, then, presumably nothing would change. by contrast, the .1 xcp fee for numerics not being accepted means that it will not be added. again, wondering not why it hasn't been rejected but why it's been 'proposed'
-
-
-
I am not really commenting on Jeremy in particular but trying to scope what needs a CIP and what doesn't
-
-
ah
-
-
in that case it'd be kinda interesting to revisit scope of purpose of CIP system
-
lotta missing context on my and adam's end. sorry about that.
-
-
are btns and stamps competitive?
-
i mean as technical alternatives to one another
-
-
-
-
lolllll i wasn't gonna say anything
-
got it. apologies i don't recall: broadcasts don't require an xcp fee right
-
-
okay that makes the controversy of the last week incredibly odd
-
-
-
last few years have been controversial to the earlier members in this chat to varying degrees
-
sure but like wasn't this whole debate nominally about the fact that a subset of counterparty users were "abusing" features of the protocol because there was no xcp fee associated with it
-
but like...
-
-
oookay i think i've got it...
-
-
-
yeah the whole thing is very odd. on the one hand, imo people can and will use the protocol in whatever way is technically feasible; on the other hand i don't really understand why one person's metaprotocol on top of a metaprotocol is okay another's is not.
-
exactly
-
because even if they have different purposes that's what both btns and stamps are.
-
-
i mean idk it's pretty neat that people are building standards within counterparty's featureset. makes it feel like more of platform, which i like
-
so rarepepes had the fakerares meme in 2016 and you had to burn pepecash to get listed.. anyone was accepted unless was outright nazi offence stuff
fake rares appeared in 2020 znd is heavily curated
bitcoin stamps follows the heavy curating method with its rules set not token selection -
my controversial opinion which i am sure some people will hate me for is that to the extent that it is a platform in that sense it makes sense not to implement a fee here and there but to have something more like a proper gas system 😬
-
please don't kick me out of the chat for saying that...
-
I will go further to say rarepepes was decentralised team of scientists apparently or at the end ...fakerares is more centralised around scilla n his crew I think, and stamps well Mike is the face
-
Decentrealised team is subjective
-
-
🤷♀️I think at the non-protocol level it can be centralised...
-
Lol 5/6 individuals is not really dectentral at all in fact I’d say that is very centralised
-
is why I said apparently.. it was mostly rare Mike not spaceMike we now come to understand
-
-
Who is rare Mike
-
-
You mean nola78 Mike?
-
presumably an epithet for a rare pepe guy lol
-
-
-
its very simple, one of the mikes is rare and the other is in space
-
I vote to keep spacemike as official terminology
-
-
Never heard of the Nola Mike being called raremike before asides from confused coit ramblings I’m sure there was a dude with that username once but, maybe I just missed that nickname or something tho
-
:)
-
ah i was just kidding lol.
-
regarding Mr Exchange dispenser ... instead of fixing the definition of the word empty counterparty had its hands tied behind its back
-
-
i've got literally no idea what Mr exchange dispenser is, sorry :/
-
-
Oxbt has a good distro lol
-
Arguable most fair launch token
-
-
Beahahahahahhahaha
-
Yeh surprised this didn’t get filtered from listings tbf
-
-
lol
-
jdogs censorship rules are anything but consistent
-
i don't want to stir the pot but im a little surprised that during the numeric fee kerfuffle stamps folks didnt push to have a fee added to broadcasts
-
it's left up to be pointed at as reason to justify his actions I expect
-
i just dont understand the difference conceptually
-
they joke about it
-
Will these clog the db of heavy description?
-
Nah
-
They get banged a lot on a mint tho I guess
-
i mean sure but presumably if there were a fee there''d be fewer of them
-
Hmmm yeh it’s kinda swings and roundabouts huh
-
-
I Feel like All use should be welcomed and adds to
CPs awareness strength even if optimisations needs to be done -
yep totally agree
-
that was from Counterparty chat
-
doesnt mike know that the high road is not acceptable in crypto
-
-
have already said what imo should be done fees-wise if anything but yeh complete agmt
-
-
-
yeah i mean these systems are vulnerable to weird attacks; centralization is chief among them
-
But well within his right, he was also missold decentral (by literally running all the thing ) and recent events have ushered more decentralisation so let’s not miss seeing the silver around these clouds
-
It has been a wooohsah moment
-
-
-
first of all, i don't call people things like that (i've always hated how acceptable personal abuse is in crypto), but yeah im trying to catch up
-
No gif of Martin Lawrence rubbing his earlobe apologies
-
I didn't mean you .. there are socks present apparently
-
oh i didnt think you were calling me that. i meant i wouldnt call you that...
-
-
if there's any braindump you can provide just dm me
-
dont wanna pollute the chat
-
-
for sure but there's a lot! appreciate everyone's patience
-
-
-
another idea up for discussion
https://github.com/CounterpartyXCP/cips/discussions/133Custom Outputs · CounterpartyXCP/cips · Discussion #133CIP: XXX Title: Custom Outputs Author: B0BSmith Discussions-To: ?? Status: Draft Type: ?? Created: 2024-1-12 Abstract Add the option to have custom outputs in a tx Rationale Counterparty has "...
-
-
that is not a *conceptual* difference
-
-
-
-
@teysol i get it but in both cases it could be argued for very similar reasons that a protocol feature is being 'abused'
-
-
again, I think the technical problems here (code quality, lack of benchmarking + optimization, API design) are being confused with the fact that 4100 STAMPs issuances in a single block is "ugly". making those broadcasts wouldn't fix the problem ofc :)
CORRECTION: those were BTNS issuances I was looking at 🙈 -
4000 stamps in a block are you sure?
-
-
they were broadcasts no ?
-
-
-
-
-
-
-
-
all blocks used to take tthat long to parse until recently was why bootstrap was the only way anyone could catch up
-
i mean thats batshit crazy lol
-
-
-
Several times, I noticed the problem with multi-send and these high tx fees. It seemed to me that free wallet allowed the user to set the price for only one out of the two transactions. There's a setting in the wallet where the user can dial in a minimum fee but it has a maximum value which is well below the requirement. This results in multisend not working. Is that a freewallet bug something with counterparty?
Are we forking freewallet?
You all know Jeremy left WabData tracking on when he cloned chrome to make fw? He denied that his application was storing private keys as plain text auto complete. Said I was making baseless personal attacks only to patch it seven months later.
No fix. After uninstall, keys are still there. I'm leary to use it for fear of worse bugs -
-
-
you can set fees on the 2nd tx if you use CP API but not in freewallet - even so its not good as users broadcasst tx1 and tx2 fails due to tx1 not being on CP Node mempool - more utxo bloat with no fix
-
-
-
-
-
i have a lot of javascript but it needs a api to function atop of
-
-
i know people dont love the cp api but have you detailed what youre missing somewhere?
-
was built on xchain apis
-
-
Imho, Ideally the explorer and wallet would be one desktop program which also allows somebody to become a full node
I know it is a ton of work, but something like that is possible, yeah? -
yeah strong agree on community nodes
-
this seems to reflect juan's recent thinking re: fednode
-
-
-
I really don't think it's that much work! We should easily be able to set up EC2 images or whatever so that it's plug-and-play to run your own explorer node
-
-
-
-
-
I'm also working on xcp.dev. I have 2 more pages to go for a complete refresh of the site. Will give you guys an update tonight
-
-
Counterwallet is very important IMO
-
I’ll live with CLI and API
-
Publish a list of good public nodes.
-
Joined.
-
You could have a customisable select box, pre filled with advised nodes but able to change/ remove/add to list too
-
Language is getting me here. I think it is time to sunset the word ‘freewallet’ into the history books.
Counterwallet Lite? -
-
-
-
-
-
-
-
Not needed I agree. A big plus to the stack and benefit to the community.
-
I had concern over a major security hole which may or may not have been intentional.
Yes it has a bad brand name. It is what it is called tho
For the record I don't have beef with any individual. I am critical of behavior and actions -
-
-
-
-
-
-
This idea is good, although the gas system should be in BTC not XCP
-
-
so I pay for my computer and pay for my xcp and now you want me to pay to use my xcp on my computer
-
loll
-
you knew it was controversial
-
-
yep! but I do think a lot of the discussion around fees is sort of beside the point
-
can't have a principled discussion about fees without principles
-
-
-
personally am very against this. have listed my reasons before but imo having a native token for txs is the reason that bitcoin and ethereum succeeded and open transactions failed
-
and antisquat
-
native coin needs to be a unit of account and unit of account needs utility
-
-
-
and you want me to pay your expenses? It is your responsibility. if you have a computer or want to use CP. When CP reaches the masses and storage capacity is be expensive... only then will we think about a fee.
Mark my words -
who do you pay to use bitcoin ser?
-
to the miner.
-
-
-
i mean it's just a real flaw in nakomoto consensus systems that nodes can't vote
-
nothing to be done i don't think.
-
in CP we have nodes, and the databases are going to fill up one day, and that will make it expensive to store
-
-
storage != compute tho, bob
-
-
there is an argument for gas wrt the latter imo
-
I think rewarding node operators directly is dangerous and breaks the model
-
-
i don't expect anything to be done with gas but since i'm not in a position of responsibility i thought i'd shitpost a little
-
but you keep the system alive by giving its native token utility and therefore value.
-
I support the idea of a BTC-based gas system. Whether that BTC is burned or rewarded to the node, the purpose is to discourage the storage of low quality, tokens and art that have no value and have only been created to attack the network. That would keep the network a cleaner.
-
-
totally disagree that unit of account should be btc
-
unit of account that does not natively integrate with platform breaks the virtuous cycle that makes blockchains work
-
again: cf. open transactions.
-
Well, suppose it is a token called gasxc, where would users get that token and how?
-
you'd just use xcp
-
small denominations of xcp that are actually related to the complexity of the operation as opposed to me and adam coming up with some number a decade ago lol
-
in ethereum it's more appropriate of course because users write their own smart contracts & because you need to deal with the halting problem, but would be a really neat way to set the basis for extending the functionality of counterparty in the future.
-
What about staking 1 xcp and receiving 100 gasxc to pay fees
-
counterparty doesn't have any utility for staking.
-
-
it's not a layer 1
-
👍
-
yep, as i said, just taking advantage of my position of non-responsibility to shitpost
-
could be done, the utxo would be frozen in a pwsh with OP_CHECKLOCKTIMEVERIFY and the larger the OP_CH... the more gasxc receives
-
/local host and CLI support would be world class. If anyone is working on or researching counterwallet, care to share your thoughts?
-
Bookmark for later.
-
Pay w xcp or pay to get xcp?
-
The reward is knowing the truth. Verifying not trusting.
-
to be clear, this wasn't meant as an attack on anyone, but rather was related to this: "small denominations of xcp that are actually related to the complexity of the operation as opposed to me and adam coming up with some number a decade ago lol"
-
absolutely, but in traditional bft consensus you have voting by nodes. otoh networks can't be open.
-
True. I would say the vote consists of a pool of one eligible voter, your node.
-
yep absolutely. blockchains are autarkical
-
There’s a lot of talk about a wallet référence implementation and I want to throw around the idea that we don’t need a wallet.
Wouldn’t it make sense for the API to provide raw and psbt hex that is singable by all wallets? Then we can provide an official JavaScript decoder package that will turn the hex into a human readable object.
Then the reference implementation becomes a call to the api for the hex and a dialog showing what your about to sign. From there it’s simple for any wallet provider to ingest the hex and sign the tx -
The wallet providers can use the decoder as their confirm pop up
-
Which as of now just shows as op return or a bunch of multisigs in a nonsensical way and users have no idea what it’s doing
-
I think it's nice to have the option of a single installation providing both a wallet and the node software, but it's not a super strong opinion. mostly i think counterparty needs a desktop wallet.
-
-
-
Leather etc
-
I think
-
I think those web3 in browser wallets all use the same libraries and require psbt txs
-
-
You can’t sign a full tx in them you can only sign the partials or smth like that
-
It was a disappointing rabbit hole to go
Down from my recollection Lel -
-
Deffo not asides from counterwallet
-
yeah i mean for normal product roadmap reasons i agree with this ofc.
-
Everyone would need to follow the API rules, which they haven’t been doing lately.
-
We are using unisat on our site. IWe convert the hex to a psbt to make it 1 click for the user. All the wallets that allow for ordinals trading will support psbt signing.
But to answer the question specifically, psbts are supported on Unisat, leather, okx, ordinalswallet, all by calling an single function in an injected window object on the client side and passing in the psbt hex -
API rules?
-
@herpenstein out of curiosity, what is your site? 🙂
-
Stampverse.io
-
fyi it doesn't like lockdown mode on safari lol
-
-
Channel too noisy, @me when I’m needed
-
I haven’t written any code for it at the counterparty-lib level. Just explored where it would need to go and how to do it yesterday
-
I also don’t have a full node and that will take a good 2 weeks to get up and running lol
-
-
yes @XJA77 can verify but think so.
-
Yes that's without bootstrap
-
-
-
-
I’m multitasking here sorry.
Protocol rules. Much larger pov than I can articulate now. -
Can anyone provide a list of the node stack protocol dependencies as is currently being proposed?
-
Any plans to support native counterparty assets? Like a named stamp?
-
-
Long term it would be silly not to. Unfortunately all of our immediate dev work has been thrown into the air due to the issues here.
-
Yes
-
Sounds good ser
-
-
Stamps-related CIPs were all JDog. His attempt to “embrace and extend” the protocol.
-
10 BTC worth of dust I think
-
huh ok...
-
He was “ trying to help / guide us”
-
I’m not a fan of the gas idea but I did like the suggestion of in wallet or distributed explorer.
Random idea but if gas comes into play what about a system that lets node runners make 0 gas txs and charges these fees for casual users.
Typing it out it sounds like another bottleneck to adoption but the gas itself is a bottleneck so rewarding those that strengthen and distribute the network might be a big motivator. -
Too many Mikes!
-
i don't want to be a jerk but i don't get the 'guidance'. *you were already doing what you wanted to do*...
-
What am I missing? Counterparty provides you with the primitives you need to do your stamps thing, right? what help was necessary
-
GitHub - blocklack-team/counterpartydb: A Counterparty db wrapper
A Counterparty db wrapper. Contribute to blocklack-team/counterpartydb development by creating an account on GitHub.
-
a rust wrapper for the database.
-balances by address
-blocks by hash and block index
-assets by name -
I will add more features soon
-
-
An update: For anyone not familiar, I'm one of the three original Counterparty co-founders, and was active in code development for the project especially in the 2014-2016/2017 timeframe. For the last good number of years though, my interests have led me to a totally different field, and life has happened (wife, kids, etc). I've maintained the github "owner" role of the Counterparty-related repositories for years, and in the absence of time to write code, have helped behind the scenes with resolving interpersonal conflicts and keeping someone at the wheel working on the project and fixing bugs.
Recently we've had some changes, such as j-dog leaving the project development team and Adam and Evan coming back into the community. I've polled the current "dev team" (Joe, JP and Shannon Code) and they are all in favor of Adam being given commit access again. I will be doing this shortly, as well as removing myself from dev team access, as having it is no longer necessary. Adam being back on the team and having the time to work on things will add a lot to the project!
I will continue to lurk in these chats (for the memes, if nothing else). After ten years, It's great to see that Counterparty is still around with a dedicated community. I wish the project the best of luck moving forward. -
The help JDog provided (and it was no small thing) was decoding the base64 on xchain so the art would show. We did appreciate that as it definitely helped make Stamps “real”
-
-
okay but @mikeinspace that's a stamps thing, right? not a counterparty thing
-
Exactly. Counterparty didn’t require changes at all
-
right, so I think this brings us back to the question of what's the scope & purpose of CIPs. curious to hear people's thoughts
-
to me it's a no-brainer that stamps and btns stuff are strictly out-of-scope, but I'd even argue that something like @herpenstein's psbt proposal can just be filed as an issue
-
Perhaps the API update. But the longer term update to the send function changes convenus so it should be a CIP
-
Perhaps consensus changes should be the only factor in CIPs
-
oh, sure, but your most recent cip doesn't need one i don't mean and convenus is precisely the line i would draw between what does and doesn't need a cip
-
Sounds reasonable
-
-
lol rare mike is a different mike, i miss uncle mike
-
the idea has been brought up by several others who also thought of it, but the notion is that not all bounties need to be for protocol development. Extending the idea outwards to other disciplines, like marketing. If a number of people go in on a billboard near/during Bitcoin Nashville, that improves counterparty. (if we are ready for an influx of noobs and are confident in our ability to scale)
There are other things I want to say on the topic, but in this setting right now, the relevance is that there should be a clearer distinction of what is needed to be funded for critical infrastructure development, feature creep, and an avenue to pursue for community funds directed at other "improvements."
Ive learned over the last few days that the counterparty culture has been to adapt the lingo of bitcoin devs when there are occasions that the implementation is simply wrong. CIP25 should not have been a CIP in name. Thinks (meant things but I like the typo) like that make it harder for general/casual users to differentiate -
with of course due respect paid to the time-honored tradition in crypto of reinventing literally every possible thing.
-
yes this is what helped ordinals to be so successful so quickly
-
-
When you run the ordinals indexer, there’s a web server that goes up locally and you can see all the information and images in a web ui
-
Interesting… not sure I see it that way at all. Ordinals went parabolic when the custodial solutions appeared removing the friction. They have a great meme which is why I think they succeeded
-
I mean this is very doable
-
yes ord runs on top of bitcoin rpc and leverages the bitcoind wallet, it also has a webserver built in
-
so its command line but its not a “separate” wallet
-
i think that structure could probly work well for counterparty too
-
let bitcoind handle key storage etc and simple pass whatever data is necessary to build the counterparty tx via rpc
-
another great thing about ord is the prebuilt binaries
-
It’s a combination of multiple factors. Most of the early trading was psbt based trading solutions that were a combination of decentralized and custodial
-
so anyone can just launch it with bitcoind running and you’re off to the races
-
i would def suggest checking out ord @teysol if you havent
-
its very simplistic and well designed
-
The custodian holds the psbts and matches them with another user willing to execute the tx
-
GitHub - ordinals/ord: 👁🗨 Rare and exotic sats
👁🗨 Rare and exotic sats. Contribute to ordinals/ord development by creating an account on GitHub.
-
So these ordinals systems are not a true dex, but a verifiably unruggable custodial trading marketplace
-
Where trades can be executed in a single verifiable tx
-
ehh i wouldnt call it custodial
-
the market places are just holding psbts, they arent holding any funds
-
I don’t have a better word for it.
-
That’s why I added the additional context
-
Lol
-
custodial means holding someone elses funds
-
so there must be a better word lol
-
They hold the psbt and find a match
-
Maybe we need a new word
-
Consignment
-
bulletin board
-
-
order relay
-
All good options
-