0 sats \ 3 replies \ @nout OP 10h \ parent \ on: Unlocking Liquidity Before Shared Output Expiration | Ark Protocol bitdevs
Is there some reasonable way to run my own swap service? Let's say with another friend that has Ark ASP running?
With the original Ark my main issue was that ASP was doing an onchain transaction every 5 seconds, effectively allowing at most 64 ASPs before the full bitcoin block capacity is used (not even considering any other transactions). I'm not sure if this got resolved in any way recently?
Since Ark is just another shitcoin so you would both need a swap service to go from shitcoin to bitcoin and back again.
I wouldn't count on any useful self-hosted tooling being made available for sovereign use, its evergreen vaporware that if it gets any traction will centralize (capture) as much as possible.
It's all trusted anyway so just use an SQL database for your guests, more cost effective and reliable.
reply
Oh apparently
arkd is actually that swap service that swaps to bitcoin and back, so you don't need to run anything else afaik, but the question is if there are indeed bindings to not just onchain but also lightning. My question stands about how this works with blockchain capacity and ASP interoperability.reply
Dunno about the current iterations use of chain space, they change this crap constantly so they can psyop non-technical people with diagrams they don't understand
There's no inter-interoperability, each Ark being its own application with its own utility token requires a swap to Bitcoin to move it to yet another application, it's not its own network
reply