I get cors errors on that

looking into it

please share your request

ah its port 4000 on api.counterparty.io and I now get 500 error

got it. can you please share your request

I got it figured out ... the 500 error is a result of using a non counterparty tx hex

People i have an anoucment.

My team has worked enormously... these last two weeks.

We have built bytesdust.com a dapp that uses PSBT.... and works with okx and phabtom wallet.

Also next week we will launch atomic swap between xcp/btc xcp/eth xcp/otheeCP20

on tesnet.

If anyone has problems just let me know... it's still in the testing phase.

but any feedback would be helpful.

awesome!

That's a nice portal for Okx users

Really cool

I'm connected via Okx web 3 mobile Wallet

yes

you can buy, transfer, assets

just check how easy is to buy a dispenser

dispenser is 100 satoshis but minumum dust is 500, so the wallet just round to the minimun dust... thats why i received 5 xcp testnet

Very cool website man! Congrats. Some initial feedback:
- the docs link didn’t work for me
- imo dispensers showing 2 addresses adds unnecessary confusion to where the BTC should be sent (but inside View you could show both)

the app does not allow you to copy the addres, you just go to the little box on how much xcp you want click on calculate and it sends you to the send page, all calculated and ready to sign and send the transaction.

Ok this makes sense in the wallet use case I suppose. In the navigation / explorer use case, then allowing copying text is useful

the docs are not available yet. when we launch on mainnet... you will be able to see how the atomic psbt works... believe me i am an expert in cryptography. and the only thing that allows us to do CP for atomic swaps is to have 2 phases, one of pairing (when the bidder and the asker match the order) and signing when both send the signed psbt to a coordinator, and the coordinator (who combines the psbt in one) and retransmits them to the node, if either of them spends the input the tx fails, or if they try to double spend it. ... as neither of them can make use of the signed psbt, only the coordinator retransmits..... is not 100000% p2p but 0.1 % p2p. except for the coordinator.

I think it's the other way around, 10000% p2p just 0.1% the cordinator.

the scroll animation on the homepage is fine but would get tiresome after awhile, it people are going to use this all the time they will want something clean, simple and that works. I do not mean this to he harsh but at some point the data I see on screen is more important that the UI to look cool

Noted...

Any suggestions on how to improve it?

Thanks for the feedback .... 👍

I think you need to have the hard brand hit at the start, it is cool but then once you are in the tool make it cleaner or less distracting

think about any tool that you use all the time that you like, it is not because it looks cool it is because it does what you want

so once I'm in the system to transact I want to have clear indication I'm doing what I should and acting on the data presented as I intend. Less is more in this case

linux shell.

I was more concerned with the animation being present

all the time

I would not want that in my shell all the time

but cool to see if and know what tool I'm using etc

ya I saw this, love it

could be a simple and a switch to turn off matrix in background

Without the matrix the interface looks is empty and sad, so we have to tell the designer to think of a solution.

The initial animation was a canvas, where the head had movement and tried to leave the screen, but then we thought that would scare the users....

Terms is spelt wrong, but that’s very minor

maybe pause the matrix, I do not need my banking app to have animation type vibe, but also would say this is a minor point and would not worry about it much

Hi, all. I am very happy to announce that there is a PR for APIv2 specification! https://github.com/CounterpartyXCP/Documentation/pull/184

*This is a draft proposal*. Nothing has been finalized. Having said that, v11.0.0, of which APIv2 will be a part, will be released in weeks, not months, and so I'd encourage anyone who's interested (especially infrastructure providers) to review and comment on the proposal.

This is a huge milestone. Special thanks to Ouziel Slama for his excellent work, and yet another heroic effort.

Looks neat to me…

I’ll maybe put a comment later when I’m near my password manager, but anything that could be done around name and quantity normalization is helpful, imo.

Like if it always/only returns the asset_name, I have to lookup if there’s an asset_longname.

And if it always returns an integer quantity, I have to check for divisibility and normalize.

And if that’s not possible, making /assets endpoint include more info so I don’t need to make 120k calls to find out if the asset is divisible or not.

Afk but looks good overall

I just got to a “stable” node, as v10.0 still had issues. I need more time to make the proper tests and comparisons. Will do my best to make these asap.

Any link with all plans for v11? Why the jump of major version?

ach I made a mistake. it's v10.1.2. Damn, sorry. Thank you for catching Juan!

😮‍💨 relief lol

hate dumb oversights like that. appreciate it! here's the 10.1.2 milestone: https://github.com/CounterpartyXCP/counterparty-core/milestone/17

v10 is an substantial increase in the counterparty.db size…..

From 8GB to….

14GB!

(Being sarcastic lol. The “DB bloat” is such a non-issue we can definitely favor data denormalization for the foreseeable future 🤓)

I added comments to the API design

on Github? or somewhere else?

https://github.com/CounterpartyXCP/Documentation/pull/184

Read some of your comments, you should take a look at https://github.com/CNTRPRTY/xcpdev-genesis/tree/main/server/express_server/src if you haven’t.

Is doing many of the things you mention (like including the asset longname and divisibility. And is designed to be as simple as possible, easy to follow

Clean

KISS (keep it simple stupid)

just one thing. uses models, to serialize. That saves you a lot of bugs and makes the code easier read

Having models helps you because I see that you are not doing sanitation. what would happen if someone called an endpoint and injected malicious SQL into the query.

?

Im aware, and there is no need. (But if there is, because I’m missing something, please let me know.)

For the GETs, it is a read-only DB connection. And the SQLite library I’m using, and being used correctly (not manipulating the string manually, but using its native parameter bindings) protects any possible malicious injection.

Then the only POST endpoint just forwards the json body to the counterparty-lib, so here I’m delegating this responsibility. The lib should handle any malicious intent. And I forward the response.

And to be super clear, and as stated in the server README, it is not meant to be a production setup.

What is run in production is based on it, but not exactly the same. And it is consumed privately.

Easy to notice, the api always returns the client’s ip, and none of that is seen in the express server. Also all responses go though a caching process, also not seen in the code.

I have another update from bytesdust.com We added support for Bytedust the native token of the dex. and preparing to open atomicswapa on testnet soon.

https://www.xcp.dev/asset/BYTEDUST

I see it was just issued. Will it have any utility?

Yes, the fees collected from the dex will be paid to the bytedust holders.

We are setting up a company in Cyprus that links tokens to shares and legally obligates tej company to pay to bytedust hodlers.

At the moment, the Dex operates legally under Bitcoin Brothers, a company that i founded in 2016 .

but this is the goal.

If this week no one launches atomic swaps in CP, I think bytedust will be the first to do so.

I just try to do things that are legal and well done.

but guess what.
crypto is the market of distrust.

Of fourse bro, nothing is free. Atomic swaps that use PSBT do not use the native CP dex, it is a PSBt-based DEX that requires a coordinator to validate rules and ensures that the taker or maker does not do something malicious.

Look as if the coordinator were that guy that say.. hey,
Pss pss I know a guy who sells something you're looking for, I can managing the exchange between two of you and i take a small fee.

but that fee will not go 100% to us, it will go to a wallet where BYTEDUST holders will be able to burn the token for BTC collected from the DEX fees

The sburning process is very simple, the user sends a unsigned psbt containing an output (op_return) to an burn address to the coordinator the cordinator reply with a unsigned psbt that contains an output with the BTC equivalent of the burned BYTEDUST. The holder validates that the two psbts are correct, combines them and then signs it, he sends the signed psbt to the coordinator and the coordinator adds the signature to the combined psbt, thus in a tx the BYTEDUST is burned and the equivalent BTC is obtained.

Nice job @Jpcryptos !

thanks bro. Aprreciate it.