# Frequently asked questions

## Do I need to buy $VIVRA to vote?

No. V1 voting uses a verified email. Token holdings do not affect vote weight. See [Your first vote](premier-vote.md).

## Does Vivra find candidates automatically?

In V1, the team submits addresses and the Scanner analyzes them. The automatic discovery tool, “Vivra Scout,” is outside V1 scope.

## Does the score choose the winner?

No. The team selects five eligible candidates, then the community votes. The score helps compare projects; it is not a price prediction. It has five pillars totaling 100 points.

## Is the Buyback Bot a seventh AI agent?

No. It is a deterministic program with a schedule and caps. The six AI agents do not have access to wallet keys.

## Why 72 hours and seven days?

The 72 hours cover the operational takeover. Buybacks and evaluation continue on the cycle schedule; the verdict is planned for Day 7. See [The takeover cycle](le-cycle.md).

## Where do fees from revived tokens go?

Once Pons accepts the CTO and the redirection takes effect, 100% of the future creator fees received by Vivra are allocated to buying back and burning $VIVRA. Fees already credited to the former creator are not recovered.

## What happens if Pons rejects the CTO?

The operation, agents, and verdict can continue. The fee mechanism for that token does not start. Application approval and fee redirection are separate states to verify.

## Does the buyback guarantee a price increase?

No. Limits constrain execution without guaranteeing a market outcome. An operation can stop, and a project can receive a `dead_again` verdict.

## Are the mockups' addresses and performance figures real?

No. The frontend handoff explicitly identifies the illustrative tickers, addresses, volumes, and results as fictional. This GitBook does not present them as live data.

## Does this documentation prove Vivra has launched?

No. It documents the supplied sources. [Implementation status](etat-implementation.md) distinguishes existing components from unresolved dependencies; no mainnet deployment was verified for this GitBook.