> For the complete documentation index, see [llms.txt](https://polarzero.gitbook.io/promise/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://polarzero.gitbook.io/promise/how-to-use/interacting-with-promises.md).
# Interacting with promises
Go to the dashboard from the menu.
The dashboard shows different sections to interact with the App:
* the promises you created ;
* the promises you're involved with, meaning that you've been added as a participant ;
* the Twitter handles you have verified.
Clicking on a promise, from the first two sections, will open a drawer through which you can interact with this promise's contract.
{% hint style="info" %}
Any interaction with a promise is only available to participants in that specific promise.
It will always trigger a transaction, that requires the user to approve and pay some gas for it to go through.
{% endhint %}
Click on a promise to start interacting with it.
The drawer for interacting with a promise.
Opening the drawer will display, at the top, the same table as for the promises in the **Explore promises** page ; only omitting to list the IPFS directory [Exploring promises](/promise/how-to-use/exploring-promises.md#what-does-a-promise-look-like).
Below are the various ways of interacting with the promise, also available directly from the contract.
Add a participant
This button allows anyone involved in the promise to add new members to participate. They will inherit the same permissions as the initial participants. If any had already approved the promise, this approval will be reset, and they will need to approve it again.
Approve promise
Approving the promise shows that each member is indeed participating in that agreement, and is not an arbitrarily included Ethereum address. Only a participant can approve for themselves.
Any time a participant is added, everyone needs to approve the promise again. This is done, so they can approve it, knowing exactly what they agree to, and with whom.
The popup shown for adding a participant.
Verify Twitter
This section allows any participant with a Twitter handle attached to this promise, to ensure that they actually own it.
Please visit [Verifying a Twitter account](/promise/how-to-use/verifying-a-twitter-account.md) for the detailed steps.
Lock promise
Once all the participants have approved the promise, it can then be locked. That means it will no longer be possible to add new participants.
This **Locked** status is a proof of reliability for your promise, as it means that it can't be modified anymore. Additionally, it means that all participants have confirmed they own their Ethereum address, and indeed agreed to participating in that promise.
## Related resources
| App |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Interacting with a promise (InteractPromiseDrawer)](https://github.com/polar0/chainlink-fall-2022-hackathon/blob/main/frontend/components/user-dashboard/InteractPromiseDrawer.js) |
| [Add a participant](https://github.com/polar0/chainlink-fall-2022-hackathon/blob/main/frontend/components/user-dashboard/RowPromiseAddParticipant.js) |
| [Approve the promise](https://github.com/polar0/chainlink-fall-2022-hackathon/blob/main/frontend/components/user-dashboard/RowPromiseApproval.js) |
| [Lock the promise](https://github.com/polar0/chainlink-fall-2022-hackathon/blob/main/frontend/components/user-dashboard/RowPromiseLock.js) |
| [Verify a Twitter account](https://github.com/polar0/chainlink-fall-2022-hackathon/blob/main/frontend/components/user-dashboard/RowPromiseVerification.js) |
| Contracts |
| ---------------------------------------------------------------------------------------------------------------------------------------------- |
| [PromiseContract.sol](https://github.com/polar0/chainlink-fall-2022-hackathon/blob/main/backend/hardhat/contracts/PromiseContract.sol) |
| [PromiseContract (tests)](https://github.com/polar0/chainlink-fall-2022-hackathon/blob/main/backend/hardhat/test/unit/PromiseContract.test.js) |
| Chainlink |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [VerifyTwitter.sol](https://github.com/polar0/chainlink-fall-2022-hackathon/blob/main/backend/hardhat/contracts/VerifyTwitter.sol) |
| [VerifyTwitter (unit tests)](https://github.com/polar0/chainlink-fall-2022-hackathon/blob/main/backend/hardhat/test/unit/VerifyTwitterMock.test.js) |
| [VerifyTwitter (staging tests)](https://github.com/polar0/chainlink-fall-2022-hackathon/blob/main/backend/hardhat/test/staging/VerifyTwitter.staging.test.js) |
| [External Adapter - twitter verification](https://github.com/polar0/chainlink-fall-2022-hackathon/tree/main/backend/chainlink-ea-twitter-verification) |
| [Operator contract](https://mumbai.polygonscan.com/address/0xd4d1fe6ff0a871ccf37bcfbce3135f548e5f05b5) |
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://polarzero.gitbook.io/promise/how-to-use/interacting-with-promises.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.