This contract system is an implementation of Ethereum-based naming service.
DexNS Name is a special structure that contains address of the owner, address of the destination (Name will be resolved into this address), metadata, signature (Keccak-256 hash of the name).
Contracts must provide the following functionality:
Register string Names.
Manage Name content (addresses and metadata).
Display Name content: destination address, metadata, signature.
Transfer the Name ownership from one address to another, except that another smart contract that does not implement a special function onNameOwnerChanged can not become the owner of the name as a result of the transfer of ownership of the Name.
Assign/unassign Names to addresses if the address is the Name owner. This is needed for blockchain explorers to display Name instead of the assigned address.
Bug bounty
$8500 for finding a critical bug.
A critical error is an error that can be directly used as a result of which:
A Name can be registered without payment.
Already-existing, not expired Name can be re-registered to another owner.
Name content can be managed by the address that is not currently an owner of the Name. (Name assignment can be managed by the address that is not currently an owner of the Name)
The consequences of the expiration of ownership of a Name could be avoided.
Other errors that can directly violate the workflow of contracts and lead to a breach of contract operability.
$2000 for security vulnerabilities and bugs, that could not be directly exploited but can affect contracts in some specific circumstances.
Any bugs that can occur in some specific circumstances and violate contracts workflow.
$100-500 for code flaws that can not violate contract workflow.
Any code flaw reports and suggestions that can improve DexNS contracts workflow. This bounty will be paid if the suggested solution will be implemented in final version of DexNS contract system.
Scope
DexNS Frontend contract.
DexNS Storage contract.
Contract overview
This contract system is an implementation of Ethereum-based naming service.
DexNS Name is a special structure that contains address of the owner, address of the destination (Name will be resolved into this address), metadata, signature (Keccak-256 hash of the name).
Contracts must provide the following functionality:
destination address
,metadata
,signature
.onNameOwnerChanged
can not become the owner of the name as a result of the transfer of ownership of the Name.Bug bounty
$8500 for finding a critical bug.
A critical error is an error that can be directly used as a result of which:
A Name can be registered without payment.
Already-existing, not expired Name can be re-registered to another owner.
Name content can be managed by the address that is not currently an owner of the Name. (Name assignment can be managed by the address that is not currently an owner of the Name)
The consequences of the expiration of ownership of a Name could be avoided.
Other errors that can directly violate the workflow of contracts and lead to a breach of contract operability.
$2000 for security vulnerabilities and bugs, that could not be directly exploited but can affect contracts in some specific circumstances.
Any bugs that can occur in some specific circumstances and violate contracts workflow.
$100-500 for code flaws that can not violate contract workflow.
Any code flaw reports and suggestions that can improve DexNS contracts workflow. This bounty will be paid if the suggested solution will be implemented in final version of DexNS contract system.
Participate
Submit an issue at the DexNS contracts repo: https://github.com/EthereumCommonwealth/DexNS/issues
The first person who submits the issue bugreport will be paid if the problem reported is considered to be an error.
For any questions: dexaran@ethereumclassic.org