CIP-0138? | Universal Query Layer

[klntsky]

A transport-agnostic query layer specification for use in dApps and wallets.

See CPS-12 for motivation.

(rendered version)

[ch1bo]

CIP-0116 defines this to include a TransactionOutput with this schema: https://github.com/cardano-foundation/CIPs/blob/b81611632f9dcea0b87d7d96cf673a720c77e929/CIP-0116/cardano-babbage.json#L445C6-L445C23

I would like to point out that chain data APIs seemingly do not decode the datum by default, i.e. when responding with transaction outputs.

I just stumbled over this yesterday in Hydra, which uses the cardano-api library to encode TxOuts and that results in a decoded datum mapped to json equivalence. See also our (messy, sorry) api reference: https://hydra.family/head-protocol/unstable/api-reference/#schema-TxOut

[rphair]

thanks @nazrhom - editors note to also tag you on discussions related to this CIP.

[rphair]

thanks @klntsky @nazrhom - marking Triage so this is officially brought into the review process at next CIP meeting (https://hackmd.io/@cip-editors/100) and my vote would be that a CIP number gets assigned there.

In the meantime we have to remove the bits of the CIP template scaffolding identified below:

[nazrhom]

Thanks @rphair

[rphair]

@klntsky @nazrhom proposal well received & confirmed as candidate at last CIP meeting. Please remember to rename the proposal directory accordingly & update the README link in the original posting. 🎉

one question @nazrhom ... I had assumed the .json files here illustrative examples, but if they are implementation files (therefore likely to require maintenance beyond the CIP) the recommendation is to host them in a repository that you and/or implementors will maintain. Please confirm which category these are in (apologies if you've already done that & I missed it).

[rphair]

Suggested change

	CIP:
	CIP: 138