- 08 January 2024 (348 messages)
-
this demand is to avoid fund loosing for users -
All I hear is what u want from xchain -
make up some decision that makes sense -
maybe once all this fork drama is done with ALL numerics will appear back on xchain... but, XChain wont be running any version of counterparty-lib without a fee on numerics. -
cool. thanks for the clarification. build on!
-
Also.. made an update to counterparty2mysql with optional update to ignore numerics in parsing in case anyone is stuck parsing blocks... I believe spells of genesis and a few other backends use counterparty2mysql still ... https://github.com/jdogresorg/counterparty2mysql/commit/77c6274e05448aae6eec46343baa8f20fe730a95added optional numeric asset filter · jdogresorg/counterparty2mysql@77c6274
PHP script that populates a MySQL database with Counterparty data - added optional numeric asset filter · jdogresorg/counterparty2mysql@77c6274
- 09 January 2024 (29 messages)
-
no -
Joined. -
lets run a poll in here for a few hours
-
XCP Fee for Numeric Assets?
59 vote(s). -
Let’s keep this poll going for the rest of the day so people in different timezones have a chance to see it
-
POLL RESULTS
XCP Fee on Numerics?
---
55% = Yes, 0.25 XCP
16% = Yes, 0.5 XCP
10% = Yes, Discuss
19% = No
XCP Fee on Numerics (YES/NO)
---
81% = YES
19% = No
What Should Fee Be?
---
55% = 0.25 XCP
16% = 0.50 XCP
10% = OTHER
Activation Block
---
790,000 = Current block
+ 1008 = 144 blocks per day x 7 days
---
791,008 = Activation Block
It appears that general consensus is to institute an 0.25 XCP Fee on Numerics at block 791,008.
@hodlencoinfield Agreed? -
poll says 70% of people IN THIS GROUP, think we should do it
-
consensus is hard
-
Friendly reminder for those who are relatively new to dev channel.... poll was taken here, consensus was to move forward with fee... but we did not... just pointing it out so yall know its not me just randomly coming up with a fee on numerics and forcing it today.... its been a long road
-
where this ws throwed?
-
it was here bro... you were in the channel at the time.... scroll up... you prolly voted in it 😛️️️️
-
a poll of devs... not just random community members who spam the option their leader says 😛
-
funny... now ppl are voting in the poll to change the results... but, results are captured above already... sorry, cant change history 😛
-
this might have made a difference before this morning but the second you forked its a mute point
-
true, consider me an attack... do what is necessary to defend against the attack... build the infastructure to support what you feel is best for CP... I have..... we all know this sucks right now, but in the long-run, good for CP dev, we having more dev conversations and talk about optimizations now than in the past few years.
-
rushed
-
For some people, who use the word like icing, the concept must be foreign.
It is not rule by majority -
voted -
I just withdrew CIP29 which justified xcp fees on numerics.
I wrote that CIP long ago and I think it is outdated.
Whoever still wants this fee, please write a new updated CIP to replace CIP29.
https://forums.counterparty.io/t/fee-on-numeric-assets/6601/6Fee on Numeric AssetsI suggest adding a 0.01 XCP fee on every issuance (initial and subsequents issuances alike). Also, invalid issuances should be ignored and no longer be stored in the DB. I am against the planned 0.25 XCP fee on numeric assets. Why fee on every issuance From my understanding, the problem lies with the issuances table. Many use cases, like data storage, should move to broadcasts. To encourage this, a fee must be applied to every issuance, not just the first one. Otherwise you can issue an asset...
-
just catching up... what happened to 0.1, not polled as an option? -
We now got 4 registration fees 0.5XCP, 0.25XCP, 0.1XCP and 0.0 XCP depending on which version of counterparty your running -
a few days ago @jdogresorg you proposed a 0.1 fee, which I happen to support
then a poll gets run for a few hours without that option in it
0.25 seems high for a numeric, 0.1 seems enough of an anti-spam measure?
it's getting harder to follow the bouncing balls on this issue -
Pretty sure that’s an old poll
-
oh sorry, my misunderstanding, I just saw it in the timeline now, thought it was done and posted
I'll resume my seat and read-only mode then -
is it me, or did xchain just rate limit itself into not displaying data?
-
as xchain is not server side has to do a call to db for each visitant i think
-
Joined. - 10 January 2024 (246 messages)
-
What is todays update sirs -
What is the offical xcp dev fund? Is there one ?
-
Not sure there's one -
no there is not
-
that's probabely why counterparty is not growing
-
Ok, so if I raised funds then I would basicly send it to jdog
-
I have created two donation lots for my upcoming auction one for xcp dev and one for stamp dev, you can send your assets to the vault and it will be auctioned, all funds sent to development
-
he is definitely the most active dev in the space
-
yea that is fine we have done it in the past, can be for xchain freewallet support
-
are you aware that counterparty is forking ?
-
creating two funds will basically support the existence of two counterparty based ecosystems
-
sure, people can show support for which they support and we dont know how this will all play out
-
For this to survive both sides will need dev funds
-
I beleive we need to organise ourself to prevent forking as much as possible
-
Agree, if you have any ideas how we can do that, im happy to discuss
-
Counterparty asset regstration grew massively in 2023 .. growing pains are the problem
We burn xcp to make sql databases work better -
Yes I'm working on a little text, to express my opinion. I think we need to put in place a better governance system
-
usage is called spam because it tastes different
-
FYI... figured you guys might appreciate some clarity on why fork and how to move forward... just sharing my opinion, reject it if you want.
Block 770000 = 1/1/2023
1/1/2023
---
121,795 Total Assets
99,450 Named Assets
8,940 Subassets
13,405 Numeric Assets
Currently
---
229,498 Total Assets
107,187 Named Assets
10,196 Subassets
112,115 Numeric Assets
sqlite> select count(*) from assets where block_index<=770000;
121795
sqlite> select count(*) from assets where asset_name not like 'A%' and block_index<=770000;
99450
sqlite> select count(*) from assets where asset_name like 'A%' and asset_longname is not null and block_index<=770000;
8940
sqlite> select count(*) from assets where asset_name like 'A%' and asset_longname is null and block_index<=770000;
13405
sqlite> select count(*) from assets;
229498
sqlite> select count(*) from assets where asset_name not like 'A%';
107187
sqlite> select count(*) from assets where asset_name like 'A%' and asset_longname is not null;
10196
sqlite> select count(*) from assets where asset_name like 'A%' and asset_longname is null;
112115
As you can see, 9+ years of stable growth on named assets and subassets which support platform with anti-spam fee
In 2023, the total number of assets on the platform doubled... and over 100K "free" numerics were spammed...
These numbers only take into account the total number of assets created numerics vs everything else... it doesn't even really address the TRUE size of bloating the database, which is counterparty stores the full base64 image data in a table that is required on almost every sql query join... thats a separate issue
While everyone is freaking out about fork and worrying about what it means... I think we should all ask how did we get here and what is the core issue, as that is how to best move forward IMO.
Core issue is should there be a fee on numeric assets... up to the community to decide... I think it is abuse and have taken my stand...
Others in the community who run projects on this platform should take time to review these numbers and forumulate and voice their opinions publicly...
You may disagree with the fork, but IMO only way out of this is clarity on what community wants, and community members who have a large stake in the project (developers who actually run projects on the chain) should have their views heard loudly at this critical time. -
200,000 assets made in 2023, oops its 100,000 but still growth compared to previous years
-
Now Xchain is not counterparty oficial ledger anymore if the aim is to support development of the protocol what is critical needed at this moment are opensource tools (wallet and explorers) we cannot relay as protocol anyomore in closed source tools as this fork is demonstrating
-
one of the greatest recent developments was 'no bootstrap'
-
but this is what is needed at this moment, good for the longterm, but no the only thing needed, this is why a foundation is very important, a foundation could be in charge to evaluate the priorities for the whole ecosystem, be in charge of dev funds and destinate it with bountys to the crytical part in each moment
-
it was awful needing a bootstrap
-
it was not dont trust verify
-
Foundation has been discussed and tried, it is complex
-
good to spinup faster a node
-
wasn't possible as code was too slow hence bootstrap . so getting that fixed was amazing
-
i know, the only problem was the registration as foundation in the US?
-
wrong, there is a BLACKBOX.Counterparty_General_Fund
-
-
(Jdog manages it)
-
Owner / Issuer1JDogZS6tQcSxwfxhv6XKKjcyicYA4Feev
shouldn't acommunity fund address start with a 3 -
I use 3 addreses fine
-
don't see enough p2sh 3 type addresses so am working to fix that
-
yea that was the main issue
-
Best development in 2022 was sorting out the hashes /parsing as the whole ecosystem relied on a known good database
-
the 'good' database as it was called
-
no wonder Counterparty struggled when it was that way
-
Should we have a CIP to make NOBOOTSTRAP the default behaviour ?
-
I think would help people to take it more seriously
-
this si de default behaviour of counterparty fednode juans repo https://github.com/CNTRPRTY/federatednodeGitHub - CNTRPRTY/federatednode: Federated Node Build System - Core Version - Don't trust, verify
Federated Node Build System - Core Version - Don't trust, verify - CNTRPRTY/federatednode
-
he does such great work
-
yes
-
Honestly raising funds is where all the crap comes from. Stay away from fiat and the good devs will do it for the right reasons. Foundations are a trap. Hushmoney.org -
Counterparty Fork Controversy: A Deep Dive into the Current Debate and Our Position
https://twitter.com/shaban_shaame/status/1745094416765710447Shaban Shaame (@shaban_shaame) on XCounterparty Fork Controversy: A Deep Dive into the Current Debate and Our Position Counterparty is currently undergoing a fork. The main reason for this fork is Jdog, the main maintainer of the Counterparty protocol and the builder of widely used tools such as Xchain (a block…
-
Perfectly said!
While I may not agree with the way the fork was activated by Jdog, he sure is getting results of new infrastructure being built out! -
💯 agree on this -
Shaban what is your plan if jdog refuses to stop running his fork
-
Every day it gets more and more out of consensus
-
I don't know yet 🙂
-
listen to every party
-
I think this is the problem, either counterparty is 9.61.1 or 9.62
-
It cant be both or it is nothing
-
After some highly scientific research I think the main contention is ease of use for stamp users, if a wallet were to somehow auto buy the xcp fee or collect btc automaticly to buy xcp at some point people wouldnt blink imo
-
i think the main point of contention currently is jdog running a hostile fork
-
we could have these conversations if he wasnt doing that but its not the case
-
counterparty cant even upgrade to 9.62 if it wanted to now
-
its already out of consensus
-
those still talking about xcp fees for numerics are missing the forest for the trees
-
if jdog can unilaterally fork the entire protocol on a whim with zero notice then it is HIS protocol to do with as he wishes
-
maybe some people want that
-
i certainly dont
-
We desire a decentralised open source protocol software stack
-
i believe most everyone in here does
-
i would hope so
-
it would not be the same, the ledgers will not match
-
exactly
-
no
-
it would kill the entire ethos
-
what happens when he does it again when he doesnt get his way?
-
feels more alive than ever
-
J-Dog (@jdogresorg) on X
Shoud be noted that the "ROGUE" developer J-Dog, who controls all the websites, properties, and API servers for Counterparty - HAS NOT merged any changes to the main repo - HAS NOT updated any official counterparty properties to 9.62.0 (website, api servers, counterwallet, etc)…
-
“I have no desire to continue maintaining counterparty, or a fork, after this drama plays out.”
-
so just stop then @jdogresorg
-
why are you torturing yourself?
-
yeah i think we’re learning alot of lessons lol
-
jdog doesnt want to maintain his fork
-
let it die
-
stop using xchain my man
-
good reason to not try to negotiate with him
-
cp api coinb.in & xcp.dev all work very well
-
yeah it can be used to sign txhex
-
as produced by counterparty api
-
is not pretty but it functions 100%
-
i not suggesting everyone use those tools, but pointing out that xchain freewallet are not essential
-
For the short term yes
-
For the longer term no
-
Which is a problem we now have to fix
-
non technical folk need to be patient whilst those with the tech chops make life easy again
-
You just need xcp in your wallet
-
The fork will deduct your balance and the non fork won’t
-
the xcp debit is done by the "CP Node"
-
They will auto pay
-
Because freewallet pulls balances from xchain
-
mints are bitcoin txs there is no xcp component until it hits the CP Node
-
Solving the wrong problem.
-
the cp node then debits xcp (if you have it for numerics & if you on the version that has those rules)
-
are you using Counterparty or JDog Party ?
-
if you use counterparty you do not need to pay 0.1 XCP for a numeric
-
Why would you want to pay for a numeric? Do you mean stay on the dogchain?
-
its automatic .. you do not get to decide which code someone else runs
-
i took me a while to understand it even after i had seen the damage it did
-
We hardly knew ye.
-
So far I think only stamp devs have? Kek
-
Does emblem vaults use xchain for balances?
-
@shannoncode
-
It does, and we are adding a guard that checks consensus across a few API’s -
Not good
-
The guards… are good but….
-
If anything this really sheds light onto infrastructure gaps. We will soon run our own balance checking infra
-
Have you thought about stopping minting?
-
Current vaults are fine but… not ones being created now
-
Pausing is a better word
-
How much longer do I have to wait to list my 40/50 vaults that weren't migrated? (Because of multiple assets or not in certain categories)
And why is old sale data not reflected on migrated vaults?
Spent alot on vaults that have been dormant way too long now -
Or shall I spend more to cancel?
-
CP nodes do not communicate, "consensus" is not achieved via PoW so checking a dozen nodes could give you a dozen different results - all valid
-
a dozen is an exaggeration but you get my point
-
We have
-
Oh sweet
-
This is not quite correct - the tx scripts do not change depending on which version of CP you use
-
What has changed is the behaviour of the node
-
No answer, OK, thanks,
-
on other blockchain networks nodes communicate . cp nodes do not communicate
-
its the word we have, the ledgers diverge
-
it is a fork
-
if we’re at the part of this conversation where we start to debate the definitions of words then we’ve really lost the plot
-
its social consensus
-
we choose to believe what is real
-
very esoteric
-
consensus is hard, we all know that.... especially when some ppl refuse to engage and dig in their heels... we have a way out of this, it'll be resolved soon, and I'm fine with my actions.... History will dictate who was on the right or wrong side... what I care about is CP community... fork is no good for anyone, neither is more fighting.... IMO we are 1-2 days away from calling off fork.... wish you were still engaging joe, but respect your right to refuse to engage 👍️️
-
lol
-
i dont engage in bad faith
-
“do this OR ELSE”
-
yup, got it. I know your mad... can only say, I understand, and respect your viewpoint so many times bro 🤷️️️️
-
^ you
-
i dont force people who depend on my services onto a forked chain with zero notice
-
i dont do that because i operate on good faith
-
Clear Governance and decision making is key to maintaining a decentralized project. The lesson we learn is the system should not depend on single implementation and we clearly need to define who decide who vote etc
-
Yeah this wasn’t an accidental fork
-
One person is knowingly running an alternate version
-
That’s offloaded to bitcoin
-
was that not a tweet ?
-
MrHodl will know
-
i like MrHodl shame he does not like permissionless use of his blockchain
-
Close, “fuck your mother if you want fuck” Jihan Wu -
-
Fork your mother if you want fork is a nice come back to that
-
Yes, thanks @IndelibleTrade for that classic
-
is that voice call still planned?
-
*bow* - 11 January 2024 (59 messages)
-
Joined. -
that was my first rare pepe lol
-
if you guys want one just send me an address!
-
FYI guys this offer was for @teysol and periwig who are featured in the card so you can stop DMing me lol
-
Fck sorry :-) -
Who owns FORK asset? maybe I do idfk lol -
-
this is frok
-
You too huh... glad it ain't just me lol
-
I did as well , followed by deleting the dm -
Thought we just giving away Rares now 😂
-
I don't know... he's had a long day.. stress might make him buy the bar a round
Worth a shot -
This time.
-
They better be they created the problem in the first place -
The issue at hand is not new; it has always been present, only becoming apparent during high-volume enviroments. The real problem lies in the 'counterparty2mysql' issue, but elsewhere. For example, XChain also struggles during periods of intense BTNS minting, indicating its inability to handle high-volume environments. In contrast, the Counterparty protocol has demonstrated robust performance across a variety of conditions (BTNS minting and also Stamps minting [10k issuances in 60 mins] ). Therefore, I recommend thoroughly understanding the underlying problem before discussing it. Imposing a fee isn't a solution. The reason we have managed so far is due to operating within a niche market. Had there been a higher volume of transactions earlier, we would have faced the same challenges.
-
you can believe what you want but it doesn't change what is actually happening.
-
I’ll work for XCP.
-
That sounds like a circular economy.
-
And CP devs + Stamps still working together as we speak. But would be great if the community come Up with CIPs or revive old ones for this while everything else its being build.
Or hopefully some fund or people want to invest in OS tooling and infra. -
There is a chat with different developers who you may want to also reach out to as this channel may not represent reality or the future.
-
Adam is one of those.
-
For sure
-
Nothing new under the sun.
-
This aged well.
-
There is a bootstrap which is not accurate but can help you for a first step
-
I know many nodes run with it
-
I dmes you ser
-
this isn't directed at you, more so its directed at the siuation
its unbelievably frustrating that a native token exists, representing stake in the protocol because it must be destroyed to translate to a named asset, is viewed so negatively
yea there was no premine, it was all done with burning btc. well, it may as well have been a premine because its viewed that way
do governments build roads from donations and then seek more donations to maintain and make more roads? counterparty is a protocol that runs on donations of time and energy and is subsequently fleeced of value. Its a one way street, minimal value is returned to counterparty dev initiative. it's progress relies on donations from the flavor of the week's project. stamps is the latest iteration.
counterparty is amazing thing and so is its community. if XCP is not going to be the glue that holds the community together that's fine. i just had to get this off my chest. we will survive as we always have -
yes i dont mean to say that they are asking for money. the profit motive is enough for them to build the tools. but again its fine to run off bounties/donations. it seems to be what we have to do
-
XCP is illiquid because it costs houndreds of thousands of dollars to list on an exchange. we havent gotten enough donations together for that
-
-
regardless, we'll be fine i just had to air out some thoughts thanks
- 12 January 2024 (15 messages)
-
Im not an expert here, but my Guess It that It cost thousand of dollars because its iliquid. Why they wouldnt want the token if there IS money to make?
-
Maybe there IS someone in this group with a bigger expertise here that can share his pov
-
i honestly dont care anymore
-
Gm. Haven't checked since some time, and had to resync my fednode and it's crazy how slow it syncing CP. Is it also taking like 2 min / block for everyone here?
-
It's not normal, even if it wasn't fast before, it wasn't that slow. I'm wondering if it's some problem on my part, might need to wipe the CP database and restart
-
what are you getting right now on your fednode?
-
No ser like 5-6 seconds per block
-
I've rebuilt cp
-
This may or may not be related... I haven't touched the official CP API servers since this drama started... but heard complaining.. working on a solution... in testing solution, had issues connecting to api.counterparty.io... seems the database is lagging? I was unaware of the issue (busy) and dunno why exactly stuff is lagging... but, i've restarted CP on both the API servers so stuff should catch up..... CP has had a running problem... which usually has only presented itself under very heavy mempool loads, where CPU gets too busy parsing hundreds of thousands of transactions every second... so John n I made some edits to mempool parsing frequency in cases of over X transactions in mempool... exact number of X escapes me.... but may be related to busy mempool, may be related to high disk IO or something... not sure, no time to test... but I do know that CP has a lingering issue, which presents itself occasionally.. where you can start up CP, it will parse to current, but WILL NOT update with txs from mempool, and WILL not parse new blocks without a restart.... i've battled this issue many times over the years... restarting counterparty-lib always fixed (windows solution, reboot 😛️️️️️️) to get parsing again.. so wrote scripts to detect lagging counterparty and restart automatically.... dogeparty has experienced this same exact recently... got a script checking API every 30 seconds if it is up and lagging... after database lags (8 blocks), my script detects "counterparty database is behind" and then kicks counterparty to restart it
-
just doing full braindump in case it helps... also, solving issue on CP API servers by restarting... hope that helps.. but may have to put lame lagging/down/reboot script monitor on CP servers... hope restart fixes for now.... in the past, you restart, and eventually it all just starts working again 🤷️️️️
- 13 January 2024 (93 messages)
-
/report
-
Is one of the reasons XCP is illiquid due the fact there a perception there isn't a lot if it?
We could do away with the idea of XCP being divisible and switch to using XCPtoshis
Divisibility is a stange beast .. its all UI perception as its all INT data types at the protocol level (correct me if i am wrong) .. without it we can leverage the Moscow time meme -
It will help add to user confusion in a big way too
-
interesting
-
The way to really increase liquidity is dex usage imo
-
That creates both buyers and sellers
-
this, currently, would need to be BTC-pay DEx, which I think we all know is unlikely to take off. And even if it did would be limited by the speed of bitcoin blocks.. It seems a common party line from XCP users (that are not "traders") always points to DEx and furthermore cites dispensers. Dispensers alone can never provide "liquidity" or a "market" as there is no capacity for 'bids' only 'asks'.
I love DEx's and wish everything could use them (hence my affinity towards counterparty) but our reliance on dex-trade (dot) com as the ONLY actual market is the major factor leading to such a dearth of liquidity. Basically, even though it's not best I think the head in the sand "we don't need a centralized exchange" line of thinking is shooting ourselves in the foot... -
I've only been around for 3yrs but this it the most action I've seen in some of these chats (even when it's contentious).
I think the ship will be sailed in a great direction because of it
Happy that I'm on it. -
-
even if though - I am firmly of the belief that listing on a somewhat known exchange would do leaps and bounds for the ecosystem. A healthy market should have all alteratives..
-
i was more referring to using the dex to sell pepes and what not, not dispensers or btcpay, the only time in the recent past we’ve had a strong demand for xcp was due to arbitrage between vaulted pepes on opensea and pepes on the dex through rarepepewallet
-
It would be good to see new ways to access the dex, FreeWallet doesn’t work for me and Counterwallet is 50/50 depending on servers and timeout -
adding dex to rarepepewallet.wtf is high on my priority list
-
now that my collection lives on a hardware wallet im more motivated than ever lol
-
lol I just ordered a ledger.. thanks Joe 🙏 -
also working on trezor support, thats what i was working on when the recent chaos began
-
but ive had zero issues with ledger
-
and after using both i actually like the interface on ledger better
-
I have a trezor already but I just got ledger for this.. plus they have very nice colorways I got orange and purple.. made me think they would maybe do a limited edition rpw printed edition. The demand is definitely there
-
If not hold tight scare city haha
-
Yeah I know
-
But it’s for the culture
-
-
This is how I keep my rareness
-
i haven’t, running direct from counterparty api right now
-
nice, will take a look
-
I think now counterblock is the piece broken in counterwallet
-
i havent tried using counterblock in years
-
With the last dispenser close
-
Is with the close delayed after 5 blocks will find J-Dog message about the issue
-
.
-
Issue with v9.61 in counterwallet+counterblock · Issue #1294 · CounterpartyXCP/counterparty-lib
From @jdogresorg in a chat: """ For the past week or so counterwallet has been down because counterblock (counterwallets backend) has been choking on parsing blocks. There is a probl...
-
Would generate potential fund loss ...
-
i disagree with any rollbacks
-
we can only go forward
-
reminds me of the time i accidentally issued quantity to a locked asset
-
edge case bug that allowed it so it was patched but that asset remains with the additional quantity
-
i think hacky might be the only way out of the spaghetti we find ourselves in
-
i did like the idea of a technical debt jubilee that droplister floated
-
i dont think hes in here but basically the idea was get the codebase on solid ground and snap shot the state at X block then move to the new version
-
we can throw a big party too lol
-
yeah im confident we can work through them
-
but at least there are options
-
Yeah for sure
I was building a DeX component into my Satoshi Soldier wallet -
There is a special edition pepe ledger, I think it was batzdu
-
making a counterparty wallet needs so much infos
-
counterblock is maybe good wallet api source ?
-
Is counterblock in fednode?
-
as in rest api I dunno counterwallet
-
yes
-
full master is it ?
-
Idk if I have it running
-
it doesn't work work atm due to dispenser issue apparently
-
delayed close
-
could it be made to do a json rest api ?
-
I know xcpdev are looking into this but seems you got some of the juicy data right there tucked away
-
Ser i dmed you
-
Can we easily make it 'run' even if its choked ? so we can expose the api for some dev .. then we can perhaps build atop of it whilst it's being fixed ... so when it's fixed and ready
- 14 January 2024 (22 messages)
-
Is there a dev donation address?
-
I will definitely send a bit and share it on stamps channels
-
This isnt the right question, if there is a dev working on something you like you should contact them direct for donation, there’s currently no one in charge of dispersing funds to devs in any sort of “official” capacity
-
I use APIs for balances and holders. I know the xchain API and site were down, and are maybe back up. But I'm still getting an error for holders. Anyone know if that will be working again or another solution for getting this info via API? I'm currently using PHP and connecting with curl
xchain.io/api/balances/ is working
xchain.io/api/holders/ returns 500 error -
I would suggest using counterparty api directly, pretty straight forward with php
-
I can send an example
-
Yeah, I couldn't find docs
-
Docs.counterparty.io
-
I don't know. I think I'm missing something with that.
-
Ok gimme a couple minutes I’ll send you an example
-
Attaching to federatednode_counterparty_1
counterparty_1 | blocks = list(cursor.execute('''SELECT * FROM blocks WHERE block_index = (SELECT MAX(block_index) from blocks)'''))
counterparty_1 | File "src/cursor.c", line 1019, in APSWCursor_execute.sqlite3_prepare
counterparty_1 | File "src/statementcache.c", line 386, in sqlite3_prepare
counterparty_1 | apsw.CorruptError: CorruptError: malformed database schema (_dispenser_refills_delete) - no such table: main.dispenser_refills
counterparty_1 | [2024-01-14 20:49:20][INFO] Running v1.1.5 of counterparty-server.
counterparty_1 | [2024-01-14 20:49:20][INFO] Running v9.61.1 of counterparty-lib.
counterparty_1 | [2024-01-14 20:49:20][INFO] Acquiring lock.
counterparty_1 | [2024-01-14 20:49:20][INFO] Connecting to database (SQLite 3.24.0-r1).
counterparty_1 | [2024-01-14 20:49:20][ERROR] Unhandled Exception
counterparty_1 | Traceback (most recent call last):
counterparty_1 | File "/usr/local/bin/counterparty-server", line 11, in <module>
counterparty_1 | load_entry_point('counterparty-cli', 'console_scripts', 'counterparty-server')()
counterparty_1 | File "/counterparty-cli/counterpartycli/__init__.py", line 16, in server_main
counterparty_1 | server.main()
counterparty_1 | File "/counterparty-cli/counterpartycli/server.py", line 156, in main
counterparty_1 | db = init_with_catch(server.initialise, init_args)
counterparty_1 | File "/counterparty-cli/counterpartycli/server.py", line 118, in init_with_catch
counterparty_1 | return fn(**init_args)
counterparty_1 | File "/counterparty-lib/counterpartylib/server.py", line 83, in initialise
counterparty_1 | return initialise_db()
counterparty_1 | File "/counterparty-lib/counterpartylib/server.py", line 467, in initialise_db
counterparty_1 | util.CURRENT_BLOCK_INDEX = blocks.last_db_index(db)
counterparty_1 | File "/counterparty-lib/counterpartylib/lib/blocks.py", line 1327, in last_db_index
counterparty_1 | blocks = list(cursor.execute('''SELECT * FROM blocks WHERE block_index = (SELECT MAX(block_index) from blocks)'''))
counterparty_1 | File "src/cursor.c", line 1019, in APSWCursor_execute.sqlite3_prepare
counterparty_1 | File "src/statementcache.c", line 386, in sqlite3_prepare
counterparty_1 | apsw.CorruptError: CorruptError: malformed database schema (_dispenser_refills_delete) - no such table: main.dispenser_refills
my fednode is getting worse and worse 😂 -
I should probably just reinstall one
- 15 January 2024 (17 messages)
-
So far all done for the good will of the world.
-
‘Issues’
-
One of the top tabs in a repo
-
:)
-
getting the rooms mixed up. I got kicked out of here for being critical. here I mostly just read. I am grateful to have been let back in
-
there is no pecking order... speak your mind and views, listen to others... remove ppl who are too disruptive and are not helping move conversations forward after everyone is exhausted with their viewpoint... I personally have not removed ppl from here (that I can recall) in the past few years... I believe I deferred to Joe n other admins to do any muting or removals.... I am admin here, but not owner... anyone who is admin can remove me as admin, or mute me, or kick me (if they feel it is necessary)... I have not quit on purpose, cuz I dont want to have me leaving become more of a problem, or have it seen as ppl kicking me out, or as me "rage-quitting" cp.... but want it clear, I have admin powers, but core devs (which includes Adam) are in control now, and have all the power, inculding the ability to remove me, mute me, etc... and they have my 100% support in taking any such actions which they feel is best for CP, including removing me.
-
Now off to shoot ppl in the face on call of duty n not talking in chats nemore for a while 🙂
-
- 16 January 2024 (2 messages)
-
New release
https://github.com/blocklack-team/counterpartydb - 17 January 2024 (4 messages)
-
This is a low-priority issue for me but I'm wondering if anybody knows if the fix is still in the works to let "callable" assets be locked.
https://xchain.io/tx/cbbac8a8471e7bc1e5f6e06fdbbf35c41cce20e15c74ffc43d55576534cc582d
Had heard something about that earlier. If I should submit it to GitHub, LMK, will do. Thanks. -
Strange, the bug should have been fixed. I just submitted a github issue for you.
-
Thanks JP.
-
Joined. - 18 January 2024 (5 messages)
- 19 January 2024 (148 messages)
-
will counterparty ever have betting? i dont know much about that function in counterparty but being able to bet on sports would be cool
Official Counterparty Dev Chat
Public archive of Telegram messages.
- 04 Jan 2024 (22)
- 05 Jan 2024 (767)
- 06 Jan 2024 (182)
- 07 Jan 2024 (187)
- 08 Jan 2024 (348)
- 09 Jan 2024 (29)
- 10 Jan 2024 (246)
- 11 Jan 2024 (59)
- 12 Jan 2024 (15)
- 13 Jan 2024 (93)
- 14 Jan 2024 (22)
- 15 Jan 2024 (17)
- 16 Jan 2024 (2)
- 17 Jan 2024 (4)
- 18 Jan 2024 (5)
- 19 Jan 2024 (148)
- 21 Jan 2024 (1)
- 22 Jan 2024 (41)
- 23 Jan 2024 (20)
- 24 Jan 2024 (4)
- 25 Jan 2024 (5)
- 26 Jan 2024 (31)
- 27 Jan 2024 (20)
- 28 Jan 2024 (1)
- 29 Jan 2024 (3)
- 31 Jan 2024 (2)