-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
feat: RP for plugin-tee-verifiable-log-api #1260
base: develop
Are you sure you want to change the base?
feat: RP for plugin-tee-verifiable-log-api #1260
Conversation
is this a duplicate of #1259 ? |
@@ -43,3 +43,42 @@ curl -X GET "http://localhost:3000/fine-tune/8566c47a-ada8-441c-95bc-7bb07656c4c | |||
-H "Content-Type: application/json" \ | |||
-H "Authorization: Bearer jvBpxrTNqGqhnfQhSEqCdsG6aTSP8IBL". | |||
``` | |||
|
|||
|
|||
## Verifiable Attestations |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Love this!
I think the easiest way to insert into documentation is to add this as a section called Enable Verifiable Logs for the Eliza in TEE Doc docs/docs/advanced/eliza-in-tee.md
. Then add a reference to your discord or discord user to contact about the implementation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we can work on this together for formatting & further enhancements/tutorials down the road. Separate into to two Plugin Sections:
- TEE Plugin
- Core Components
- TEE Verifiable Log Plugin
- Core Components
- Tutorial
- Enable Verifiable Log
- Conclusion
- Mention contributors for implementation and who to reach out to learn more about Verifiable Logs in TEE
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No problem, let's work on this together. that’s exactly the idea behind building this plugin.
Let me explain further:
- RP for plugin-tee-verifiable-log #1259 : This is a standalone log plugin that doesn’t modify other plugins or the client.
- feat: RP for plugin-tee-verifiable-log-api #1260 : This modifies the direct client to provide a query interface for verifiable logs.
LGTM, outside of the 1 suggested edit. I can help document tomorrow and run a test to fix any bugs i may encounter |
@@ -69,6 +71,9 @@ export class DirectClient { | |||
const apiRouter = createApiRouter(this.agents, this); | |||
this.app.use(apiRouter); | |||
|
|||
const apiLogRouter = createVerifiableLogApiRouter(this.agents, this); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If VERIFIABLE_LOGGING
is not enabled, will this fail to start the agent? or will it just fail the API call?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fail the api call
|
sorry,I have configured two GitHub accounts locally. The problem with @gene-sf is that I forgot to switch the configuration file when submitting the code. I have completed the following operations:
|
@shakkernerd I noticed that PRs #1331 and #1333 were reopened and this PR closed, which has left me a bit confused about the current direction. Should I merge my changes into the develop branch, or is there a different branch we should treat as the standard? I’ve submitted #1369. both cpppppp7 and I have been working diligently to make progress on this code contribution. I’d appreciate any clarification to ensure we align our efforts effectively. 😊 |
Hi @gene-zhan Thanks for bringing this to my attention. Good to hear about your active contributions. |
@shakkernerd Thank you for your response! I accidentally submitted duplicate PRs (#1259 #1260 #1331, #1333, and #1369). I recommend prioritizing the merge of #1369, as this branch already includes the latest develop code. The other branches contain the same code but currently have conflicts that need to be resolved. Merging #1369 would help reduce additional workload. Thank you again for your understanding and support! 😊 |
Relates to:
Risks
Low
Background
What does this PR do?
This PR builds upon
plugin-tee-verifiable-log
by modifying the direct client to add remote attestation and query interfaces for verifiable logs.To better understand what verifiable logs are and why we implemented this feature, it is necessary to refer to the preceding PR that introduces
plugin-tee-verifiable-log
and provides the context for its development.What kind of change is this?
Documentation changes needed?
Yes, we will add documentation about api detail.
Testing
Where should a reviewer start?
Understand the existing
plugin-tee
plugin-tee
and use its key derivation interface.To better understand what verifiable logs are and why we implemented this feature, it is necessary to refer to the preceding PR that introduces
plugin-tee-verifiable-log
and provides the context for its development.Understand what
plugin-tee-verifiable-log
doesDetailed testing steps
It have completed the integration tests and can run the
pnpm test
file in the test directory.