> For the complete documentation index, see [llms.txt](https://help.tokenpocket.pro/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tokenpocket.pro/en/wallet-faq-en/eos-wallet/what-voice-team-says.md).

# What Voice Team Says?

![](/files/-MN3sulRGHirFLb5h1hp)

**1. The Road to Beta**\
Six months ago, our CEO Brendan Blumer, and CTO Dan Larimer, went on a bit of a rant in a packed Washington D.C. auditorium. The subject? The state of social media.

Well, it wasn’t really a “rant.” It was more of a multi-movement oratory spanning the subprime mortgage crisis, the evolution of blockchain, and social psychology.

Full article> <https://voice.com/blog/road-to-beta/>

![](/files/-MN3t-SoRcYBHI5rGerI)

**2. Behind the scenes at Voice: Legal & Compliance**\
Come on the 14th of February, everyone will be able to experience the product and engineering work that we’ve been earnestly completing over the past year. As you participate in Beta, you will see the evolving creativity of our bleeding-edge engineering team.

Full article> <https://voice.com/blog/behind-the-scenes-at-voice-legal-compliance/>

![](/files/-MN3t8UBpEneF1ljJu43)

**3. A Regulatory Recap**\
In December of 2019, we sat down with the U.S. Securities and Exchange Commission in Washington D.C. to discuss our vision and plans for Voice: what it is, what we are trying to achieve, and how the tokens will work.

Full article> <https://voice.com/blog/a-regulatory-recap/>

![](/files/-MN3tCA4ok_nESjuUvWp)

**4. Beta (to start) in the USA**\
Followed by a steady rollout to English speaking territories, then globally.

We are excited to share that the first stop on the Voice Beta tour is the United States, and not just because if you sing this post’s title to the tune of Bruce Springsteen’s classic Born in the USA it sounds rather catchy.

Full article> <https://voice.com/blog/beta-in-the-usa/>


---

# 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://help.tokenpocket.pro/en/wallet-faq-en/eos-wallet/what-voice-team-says.md?ask=<question>&goal=<endgoal>
```

`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.
