This is a question better posed for the official XCP forums :-)

However, I will try to answer. There are no individual transactions for the assets delivered via a dividend issuance. There is single one 'main' dividend transaction instruction with specific rules as to how to issue the dividends to the individual addresses . CounterpartyD then receives this instruction and performs the issuance behind the scenes. Each individual CounterpartyD client also does the same and you then have consensus by protocol

cheers

Sure, that makes sense. And the API would be a good fit for that.

I will look into that as soon as I finish up some of the other changes that I have been working on recently

Cheers

If you run and have access to the CLI, you can do anything

The daemon went down so we were backed up a bit. After restarting it we're up to date

You can check the main page to see which are the last block processed, if its not up to date it most likely means the daemon is down

Ok. Completed as per above. You can now get the both the latest DEX prices for a BTCPAY & NonBTCPay asset pairs.

The code for the NonBTCPay assets pair is still new so it's under testing. Do let me know if you see anything out of place

ex:

http://xcp.blockscan.com/api2.aspx?module=price&asset1=BTC&asset2=SJCX

http://xcp.blockscan.com/api2.aspx?module=price&asset1=SJCX&asset2=XCP
http://xcp.blockscan.com/api2.aspx?module=price&asset1=XCP&asset2=SJCX


Cheers

I like what you did with CoinMachine.co. Straight forward and clean design. Tried the service and the notifications were prompt and precise

Is the match_expire_index used to used to designate the block index when the order was matched?

That was what I thought so too... Having said that, how would suggest that we determine the block that an order matches?

Can this be done by looking at the larger value of either the tx0_index or tx1_index ?

I have updated both the order_matches and orderinfo(matches) with the block number