setup.py update I think and yes. Someone should confirm this though.

To update:

cd counterpartyd_build
C:\python32\python.exe setup.py update

It does not rebuild the database every time, only sometimes.

It's a significant disadvantage, yes, but I don't see any good alternatives.

They can construct the troll tx, wait to find a block themselves, and then include the tx in it. Then they get the fees they paid in the tx.

LOL.  +1

Maybe silly idea, but is there a way to code this so that a user has an option of sending either BTC or XCP into the escrow?

What I meant is trading for "real" PPC (or whatever cryptocurrency/asset/token with its own blockchain/ledger). I understand that CFDs could do the trick for short-term speculation (however; we need trusted broadcasts first). But as I am more of a long-term investor wanting to diversify, CFD are a bad option. I believe that even if the concept of BTC and XCP is here to stay - BTC and XCP probably are not. And I don't want them to take my CFDs with them when they go.

Neither do I favour an IOU-concept like ripple for my purpose (which, as I understand could work in XCP as well..).

But a nicely working trustless DEX would of course be revolutionary...

It's ok from here in London, UK.

Yes, it's slow to load. Perhaps too much load on the server.

Agreed, a trustless DEX across blockchains would be rather special.

Did you see techo051's post?


I haven't had a chance to fully read it yet. It's talking about using BitMessage as a trustless mechanism to bridge across OT servers.

The ramifications if true is that it would be possible to create a trustless gateway service between a DEX and a disparate blockchain. ie purchase PPC in Counterparty and then trustlessly exchange it for 'real' PPC.