This repository contains the source code of the nameservice tutorial!
Click here to access the tutorial. You can also view it on the website.
Click here for instructions on how to build and run the code.
Translations:
--
go mod replace... can be by hand
go mod verify
go mod tidy
go build
ipfs hash
QmWHTHBapomvBksnuAWSQZ47ckj3LrGgmb7D2r1WXExNEX
ipfs daemon &
ipfs cat QmWHTHBapomvBksnuAWSQZ47ckj3LrGgmb7D2r1WXExNEX
nsd unsafe-reset-all
rm -rf ~/.nsd/config/genesis.json
nsd init syzer --chain-id buildings
nscli keys add jack < .secret_password
nscli keys add alice < .secret_password
nsd add-genesis-account (nscli keys show jack -a) 1000nametoken,100000000stake
nsd add-genesis-account (nscli keys show alice -a) 1000nametoken,100000000stake
nscli config chain-id buildings
nscli config output json
nscli config indent true
nscli config trust-node true
nsd gentx --name jack < .secret_password
nsd collect-gentxs
nsd validate-genesis
nsd start
nscli query account (nscli keys show jack -a) nscli query account (nscli keys show alice -a)
nscli tx nameservice buy-location AlexPlatz1 5nametoken 52.521918 13.413215 --from jack
nscli tx nameservice buy-location BrandenburgerTor1 5nametoken 52.516275 13.377704 --from jack
nscli tx nameservice set-dag AlexPlatz1 (cat ./data/dag.json) --from jack --gas 20000000000 nscli tx nameservice set-dag BrandenburgerTor1 (cat ./data/dag.json) --from jack --gas 20000000000 nscli query nameservice resolve AlexPlatz1
nscli query nameservice whois AlexPlatz1
nscli tx nameservice buy-location AlexPlatz1 10nametoken 52.521918 13.413215 --from alice
nscli rest-server --chain-id buildings --trust-node
npm test
bash test.sh
Edit config file in:
ls ~/.nsd/config/config.toml
resolver for whois
- FIX set-dag of AlexPlatz... maybe its resets lat lon
msg := types.NewMsgSetDAG(args[0], args[1], cliCtx.GetFromAddress())
- validate DAG valid JSON.
- add push to dag (now its replace)
- Branding internet of Buildings
- Purchasing buildings
- split ownership as CrowdHouse
- should it be in DAG.. maybe in the chain ?
- this in DAG
OWNERHISTORY/ApplicationIdentifier
- should go to to ownership chain
- is it enough to remove notarial office
- TDD approach to buildings with smart contracts
- automatically recalculate stress tests,
- automatically recreate energy norms
- automatically recreate ISO-Norms
- Forking buildings, and paying for DAG to clone
- should DAG be private
- maybe a private chain for it ?
- how enforce payments of for DAG's
- how to encrypt DAG's
- DAG can be private
- is IPFS good place to handle DAG?
- maybe just use private chain
- should DAG be private