mirror of
https://github.com/embarklabs/embark.git
synced 2025-01-26 05:28:57 +00:00
446197baff
Users can turn of blockchain support if they want to using the blockchain.js configuration. In practice however, this has never properly worked as several places in Embark's codebase weren't actually honoring that configuration value. This commit introduces the necessary changes so that disabling blockchain support will: No longer generate blockchain related EmbarkJS artifacts No longer try to deploy Smart Contracts but still compile them
embark-ens
Implements ENS support in Embark
This module:
- registers console commands to interact with ENS
- deploys & setups ENS contracts depending on the network
- implements ENS support in EmbarkJS
- setups generated code acording to the config
API
command: ens:resolve
- returns the address of an ens name
arguments:
name
- ens name to resolve
response:
error
- if an error occurs, null otherwiseaddress
- address associated to the ensname
given
command: ens:isENSName
- checks is it's a (valid) ENS name
arguments:
name
- ens name to validate
response:
error
- if an error occurs, null otherwiseresult
- true/false depending ifname
given is a valid ens name
command: storage:ens:associate
- associates an hash to an ENS domain
arguments:
options
name
- ens namestorageHash
- hash to associate
response:
error
- if an error occurs, null otherwise
Web API
endpoint: GET /embark-api/ens/resolve
- returns the address of an ens name
arguments:
name
- ens name to resolve
response:
{
address: <address of ens name>
}
endpoint: GET /embark-api/ens/lookup
- returns the ens name of an address
arguments:
address
- address to query
response:
{
name: <ens name of address>
}
endpoint: POST /embark-api/ens/register
registers a domain or subdomain
arguments:
subdomain
- ens domainaddress
- address to associate
response:
{
name: <ens name>
address: <address>
}
Dependencies
- async
- eth-ens-namehash
- embarkjs.utils
- secureSend
- embark utils
- AddressUtils
- hashTo32ByteHexString
- recursiveMerge