Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ICS ?: Relayer Query Endpoints #61

Closed
mossid opened this issue Mar 28, 2019 · 3 comments
Closed

ICS ?: Relayer Query Endpoints #61

mossid opened this issue Mar 28, 2019 · 3 comments
Labels
tao Transport, authentication, & ordering layer.

Comments

@mossid
Copy link

mossid commented Mar 28, 2019

The chains need to expose endpoints to query packets, headers, evidence, etc., in a standard form for the relayers to connect easily without acknowledging about the internal consensus logic. The relayers should be able to connect to any node which is running a full node of an IBC chain and start relaying packets to another.

@mossid mossid changed the title ICS ?: IBC Query Endpoints ICS ?: Relayer Query Endpoints Mar 28, 2019
@cwgoes
Copy link
Contributor

cwgoes commented Mar 29, 2019

I agree but I am not sure if exact REST formats should be in scope of this repo, that sounds like an implementation spec. We should definitely define the exposed data and proof requirements.

@cwgoes
Copy link
Contributor

cwgoes commented Mar 30, 2019

What I think we should do is define pendingDatagrams clearly - see #37 (comment)

@cwgoes cwgoes added tao Transport, authentication, & ordering layer. and removed category-ibc-misc labels Aug 17, 2019
@cwgoes cwgoes added this to the IBC 1.0.0-rc1 milestone Aug 17, 2019
@cwgoes cwgoes modified the milestones: IBC 1.0.0-rc3, IBC 1.0.0-rc4 Aug 24, 2019
@cwgoes
Copy link
Contributor

cwgoes commented Aug 24, 2019

Closing in favor of #217.

@cwgoes cwgoes closed this as completed Aug 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tao Transport, authentication, & ordering layer.
Projects
None yet
Development

No branches or pull requests

2 participants