Add ECU (Electronic Coin Unit) token configuration

[jl5047537]

Add configuration for the ECU (Electronic Coin Unit) jetton.

Jetton Master:
https://tonviewer.com/EQAlFh-_a1UbCPz119-FzTTLw0RQvaDTCBU4sCafh_n64SYo

Project website:
https://ecu-token-info.vercel.app/

Telegram:
https://t.me/ecuton

Please make sure you change the original .yaml fields in the accounts/, collections/ or jettons/ directories and leave the auto-generated .json files in the repository root alone. Also please make sure that you do not use ton.api links in your pull request.
Example pull request:

address: Address of your token  symbol: Symbol of your token websites: - "link" social: - "link"

ATTENTION! The Tonkeeper team does not charge any fees for checking/verifying tokens/collections. The procedure is ABSOLUTELY FREE. Ignore comments in commits that require payment to speed up/successfully check the PR. Stay safe fren!

Пожалуйста, убедитесь, что вы изменили исходные поля .yaml в каталогах account/, Collections/ или jettons/ и не трогаете автоматически сгенерированные файлы .json в корне репозитория. Так же, пожалуйста, убедитесь, что вы не используете ссылки ton.api в вашем пул реквесте.
Пример пул реквеста:

address: Адрес вашего токена  symbol: Сивол вашего токена websites: - "ссылка" social: - "ссылка"

ВНИМАНИЕ! Команда Tonkeeper не берет никакой оплаты за проверку/верификацию токенов/коллекций. Процедура АБСОЛЮТНО БЕСПЛАТНА. Игнорируйте комментарии в коммитах, требующих оплаты для ускорения/успешности проверки. Будьте внимательны и осторожны!

[salateur]

I kinda can't understand the idea behind the project.
Like what's is the usability? If it's an utility token, how can it be used and why it needs verification?

[jl5047537]

Thank you for your review.

ECU is used within a smart contract as a unit for creating unique digital records.

When a user sends ECU to the contract, they receive a separate unit,
which represents a unique record stored and verifiable on-chain (at the hash level).

The core idea is to work not with a balance, but with individual digital units,
each existing as an independent and verifiable entity.

These units can be:
— transferred to other users
— stored as independent records
— removed through the contract with the underlying value returned

In essence, this acts as an alternative to centralized databases,
where records are created, stored, and verified directly by the contract.

The application scope includes systems where uniqueness and verifiability are important:
access control, membership, digital status, and other forms of digital identity.

A simple current use case:
a user sends ECU and receives a record representing membership or access.
If they no longer need it, they can remove the record and retrieve the value through the contract.

ECU is used as a dedicated internal unit to ensure consistent behavior of these records within the contract logic.
Using a separate token allows the system to define clear rules for creation, transfer, and removal of records without affecting unrelated assets.

The project is already live, and users are creating and using these records in practice.

Verification is requested so users can clearly identify the correct token when interacting with the contract and avoid confusion with unrelated assets.