We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We have interfaces to support clients reading from the chain without spawning a process (@agoric/client-utils) but to sign they need to spawn to agd.
@agoric/client-utils
It could use signAndBroadcast like Keplr's API, which could be implemented by an agd interface too:
signAndBroadcast
makeAgd({execFile}).withOpts({keyringBackend: 'test'}).account('gov1').signAndBroadcast(...)
Requirements if using Casting .
Given key material, Casting should provide an API to send CosmJS transactions to the leader.
When you ask Casting to do something, you don't get any state from that call
New state is propagated through RPC so that all consumers get the same.
You can evaluate and tell me the results of (with an ACK or a NACK) Publishing is how we get the side-effects
Alternately client-utils or rpc.
client-utils
rpc
Should probably make use of,
The text was updated successfully, but these errors were encountered:
Current meet-in-the-middle brainstorm:
test('oracle uses transaction client', async t => { const PORT = await t.context.startServer(t, []); const leader = makeLeader(`http://localhost:${PORT}/network-config`, { retryCallback: null, jitter: null, }); /** @type {import('@cosmjs/stargate').SigningStargateClient} */ const client = leader.makeClient({ seed: new Uint8Array([0, 1, 2, 3, 3, 2, 1, 0]), }); client.sendAction({ type: 'applyMethod', body: JSON.stringify([ { '@qclass': 'slot', index: 0 }, 'pushResult', [ { numerator: { value: { '@qclass': 'bigint', digits: '12345' }, brand: { '@qclass': 'slot', index: 1 }, }, denominator: { value: { '@qclass': 'bigint', digits: '67890' }, brand: { '@qclass': 'slot', index: 2 }, }, }, ], ]), slots: ['offerResult:3', 'board0133', 'board244'], }); });
Sorry, something went wrong.
turadg
No branches or pull requests
What is the Problem Being Solved?
We have interfaces to support clients reading from the chain without spawning a process (
@agoric/client-utils
) but to sign they need to spawn to agd.Description of the Design
It could use
signAndBroadcast
like Keplr's API, which could be implemented by an agd interface too:Requirements if using Casting .
Given key material, Casting should provide an API to send CosmJS transactions to the leader.
When you ask Casting to do something, you don't get any state from that call
New state is propagated through RPC so that all consumers get the same.
You can evaluate and tell me the results of (with an ACK or a NACK)
Publishing is how we get the side-effects
Alternately
client-utils
orrpc
.Should probably make use of,
Security Considerations
Test Plan
The text was updated successfully, but these errors were encountered: