Brian allows users to perform transactions, research web3 info and data, and deploy smart contracts with a simple prompt. All the features are already available on the Brian app (a non-custodial solution) and can be integrated into any app through the Brian APIs.
How do we use ENS?
- Send Transactions with a prompt: On the send transactions feature, we use ENS in several ways:
"Transfer 1 eth to vitalik.eth": the ens is forward resolved to the address
"Register vitalik.eth for 3 years": it is possibile to register an ens with a prompt (coming at the end of april)
"Renew vitalik.eth for 3 years": it is possibile to renew a registered ens (coming at the end of april)
"Is vitalik.eth available?": check if an ens is available (coming at the end of april)
"when does vitalik.eth expire?": check your ens expiration (coming at the end of april)
You can also do multiple operations like:
"Register these two ens: vitalik.eth and limone.eth" (coming at the end of april)
"Register vitalik.eth for 1 year and renew limone.eth for two years" (coming at the end of april)
We'll continuously add new ENS-related actions (e.g., subdomain registration) and work on user intent recognition, offering the market an easy and innovative solution for registering an ENS!
- Brian Public Knowledge base: In our public knowledge base we have added several ens docs, allowing users to search info like "what is ens?" "what is the ens registry?"
This is already available both on the brian app and brian api.
We can also launch a new kb dedicated only to the ENS ecosystem. On this custom-built kb we can add specific docs, articles, github repos, etc., allowing users to ask more in-depth questions.
Brianknowsai History
-
accepted into ENS Identity 5 months ago.
People donating to Brianknowsai, also donated to
