Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Gravity Protocol

Pages: [1] 2 3
1
Gravity / Stay Stealthy
« on: August 15, 2018, 01:10:55 pm »
Stay Stealthy

Most cryptocurrencies today have transparent blockchains, so that transactions taking place within them are openly verifiable and traceable. However, users want to have the opportunity to transact in a secure and anonymous manner. Moreover, in a business environment a non-disclosure of a commercially sensitive information is a crucial thing, that helps you to avoid showing vulnerabilities to your competitors.

So there is a need for private financial transactions and that’s why we have implemented the Stealth Transactions feature into the Gravity Business Framework.

There is a certain bias in the digital world that stealth transactions are mostly used for illicit activities, but we believe that the ability to transact in stealth mode will facilitate further business adoption of the technology. This makes it a must have feature for a public blockchain in order for it to be adopted by SMEs.

More about anonymous cryptocurresnies and Gravity Stealth Trasnactions read here.


2
Gravity / Gravity Testnet Instructions Set #2
« on: July 24, 2018, 12:32:05 pm »
Hi, everyone!

Last week some technical updates have been introduced to the testnet. We issue a new set of instructions on the testnet participation. The Gravity Team takes a serious view on information support of the project. If you have any questions which are not presented in the instructions, please leave them in the comments.

Instructions in the Set
  • Update Gravity Protocol node
  • Resync Gravity Protocol node
  • Edit the blockchain configuration
  • Find our account’s private keys
  • Vote for Gravity Protocol witnesses
  • Comittee Memember Registration Tutorial
  • Vote for Gravity Protocol Committee Members
  • Gravity protocol’s proxy
  • Change a node in the Gravity Protocol wallet
  • Backup copy of a bin-file
  • Brainkey backup copy of your Gravity wallet

Update Gravity Protocol node
See the video version here.
  • First, we’ll go to the node’s directory
Code: [Select]
cd gravity-testnet-docker
  • Here we’ll stop our node
Code: [Select]
sudo docker-compose down
  • Then we’ll receive the update from github
Code: [Select]
git pull origin
  • And new versions of packages from Dockerhub
Code: [Select]
sudo docker-compose pull
  • Now we’ll run the node in daemon mode
Code: [Select]
sudo docker-compose up -d
  • If you prefer, you can display current sync status on the screen
Code: [Select]
sudo docker-compose logs — tail 10 -f
  • To hide the logs, press Ctrl+Z.

Resync Gravity Protocol node
See the video version here.

  • First we’ll go to the node’s directory
Code: [Select]
cd gravity-testnet-docker
  • Here we’ll stop our node
Code: [Select]
sudo docker-compose down
  • And run it again
Code: [Select]
sudo docker-compose up -d
  • If you prefer, you can display current sync status on the screen
Code: [Select]
sudo docker-compose logs — tail 10 -f
  • To hide the logs, press Ctrl+Z.

Edit the blockchain configuration
See the video version here.

  • First we’ll go to the node’s directory and open cli-wallet when the node is launched.
  • Then we’ll unlock the wallet. And now we’ll get to work.
  • We’ll get current configuration values. We’ll make a proposal to change the maximum asset feed publishers.
  • Now we’ll get the number of proposal id.
  • And we’ll vote.
  • Now we’ll close the cli-wallet using Ctrl+C
  • As you can see, we’ve created a configuration change proposal and voted for it.

Find our account’s private keys
See the video version here.

  • First, we’ll open the “Keys” tab.
  • Then we’ll enter the password to bin-file.
  • After that, we’ll press “Show keys”.
  • There are two owner keys and two active keys. Each pair has one public key. Your public key starts with ZGV, and your private key starts with “5”.
    *Just left-click on one of them to copy.

Vote for Gravity Protocol witnesses
See the video version here.
  • First, go to the “Voting” tab on the left.
  • Here we see a list of accounts who want to become witnesses. As you can see, some of them are active now, some are not.
  • There are some links in the “About” column. They mostly lead to articles, where people describe why they want to become a witness.
  • We can select up to 30 accounts we want to support. Our voting power is not affected by the amount of accounts we choose to support.
  • After the selections have been made, we’ll click “Vote”.
  • After that, we’ll enter the password to the bin-file.
  • And we’ll press “Vote” again.
  • So we’ve successfully supported our selected witnesses.

Vote for Gravity Protocol Committee Members
See the video version here.
  • Go to the “Voting” tab on the left.
  • Then select the “Committee” tab above.
  • Here we see a list of accounts who want to become committee members. Some of them are active now, some are not.
  • There are some links in the “About” column. They mostly lead to articles, where people describe why they want to become a committee member.
  • We can select up to 30 accounts we want to support. Our voting power is not affected by the amount of accounts we choose to support.
  • After the selections have been made, we’ll click “Vote”.
  • Now enter the password to the bin-file.
  • We’ll click “Vote” again.
  • So we’ve successfully supported our selected committee members.

Gravity protocol’s proxy
See the video version here.
  • First, we’ll open the “Voting” tab.
  • Here we see tabs containing witnesses and committee members.
  • If for example, we don’t have much time to figure out which of them are worth our support, and which are not…
    the proxys are here to help us.
  • Proxy is an account to which we can delegate our voting power. However, it doesn’t have access to our wallet or our tokens.
  • All we have to do now is select an account to which we’ll delegate the vote.
  • After that, we’ll insert the chosen account’s ID to a “Set proxy” line and press “Delegate”.
  • Here is where we’ll fill in our bin-file password and press “Yes, I agree”.
  • Please note: after setting the proxy you won’t be able to vote personally.
  • If instead you decide that you want to vote in person, you can always press “Cancel proxy”. And then press “Yes, I agree”.

Change a node in the Gravity Protocol wallet
See the video version here.
  • By default, the set node will be the one with the lowest ping. But if for whatever reason it doesn’t suit you, you can always change it.
  • You can access the selection of nodes in two ways.
  • The first way is to press the block number and then “Advanced settings”.
  • The second way is to press “Settings” and go to the nodes tab. Here we need to turn off automatic node selection.
  • After that, we’ll press the “Switch node” button in front of the node we’ve chosen.
  • In the future it will be possible to add random nodes here as well.

Backup copy of a bin-file
See the video version here.

  • To make it, we’ll first go to “Settings”.
  • Then we’ll select the “Backup” tab and press “Create backup now”.
  • Here we’ll enter the bin-file password and press “Download”.
  • As you can see, a backup file has been saved to the download folder.
  • Now we’ll need to move it to a more secure place. That’s it!

Brainkey backup copy of your Gravity wallet
See the video version here.

  • You may need this backup if for some reason you only have a bin-file.
  • First, we’ll go to “Settings”.
  • Then we’ll select the “Backup” tab.
  • Here we’ll enter the bin-file password below the “Brainkey” sign.
  • And then we’ll press “Show”.
  • After that we’ll copy the Brainkey to a safe file.


3
Gravity / Gravity Solutions: On the Way to the Marketplace 3.0
« on: July 19, 2018, 02:16:08 pm »
Gravity Solutions: On the Way to the Marketplace 3.0

A marketplace is an online platform where a customer can compare and buy a wide range of goods and services from several sellers at once. Marketplaces became a popular and necessary solution for SMEs (Small and Medium Enterprises) because they significantly extend their outreach to a global level and offer completely new methods for selling goods and services. Small enterprises found the idea that there’s no need to maintain and promote their online shop attractive, since those tasks can be rather expensive.

The key objective of early marketplace development is to extend the the availability and access to a range of product to the limit, which is not available for an offline retailer. The second stage of marketplace development is to enlarge the audience to an international scale. This is the stage where all marketplaces are currently. However, these stages imply a quantitative increase only, and it seems the next evolution will involve the qualitative optimization of the marketplace.

More on the decentralized marketplaces and DEX as a new marketplace see here in the full article on Medium.


4
Gravity / To Witnesses (Old and new)
« on: July 19, 2018, 12:16:51 pm »
As announced last week, the updated nodes have been introduced. We fixed all of the sync and emission issues, and our testnet is stable and ready for work.

To all the existing witnesses who are out of sync! Please update your node up to the latest version and resync. If you prefer to use a previous configuration, you should first add this checkpoint: checkpoint = [3079462, 002efd26658683618e4a6ca886b6383b8119fc9f].
Once the synchronization is complete, please, send us a message so we can vote for you.

To those who want to become a witness! You are very welcome to do so!

Please, start running the node: https://github.com/GravityProtocol/gravity-docs/blob/master/tutorials/running%20node%20with%20docker.md
Become a witness: https://github.com/GravityProtocol/gravity-docs/blob/master/tutorials/becoming-a-witness.md
And lastly, report to the Telegram channel.


5
Gravity / Gravity Testnet Report 25.06.2018–11.07.2018
« on: July 16, 2018, 09:04:21 am »
Gravity Testnet Report 25.06.2018–11.07.2018

Hi everyone!
Last fortnight was filled with lots of events! Our team worked on desync issues, refined the Wallet and Block Explorer, and created a new design for the Block Explorer. For more information, read the report below.

The Gravity website moved to a new domen gravity.io, all the old links now redirect users there. The Korean version of the website is also in progress.

The most recent version of our White Paper is on the website now, and everyone can have a look at it here

We are working on a new Roadmap. The old version included everything on one map, but the new one is more detailed and divided into sections: Business, IT, Go-To-Market and so on. You can have a look on it here on our website.

All of the tutorials on the network are now on github. If you have any suggestions or questions, please let us know at our telegram dev-chat.

Statistics for 10.06.2018–24.06.2018
Number of accounts: 2619 (99 new)
Number of signed blocks: 3 827 600 (1,369,338 new)
Number of transactions: 784 881 (103,165 new)
Number of active witnesses: 13
Number of reserve witnesses: 45
Number of active committee members: 11
Number of reserve committee members: 29

Network Activity Index
Network Activity Index is calculated in the testnet once per week and its amount affects the size and availability of emission. Emission is released only if the Activity Index in the last week was greater than in any other previous week. This emission is distributed amongst all the accounts in the network according to their Gravity Index.

In the fifth week of testing, Network Activity Index was 67689, and as a result, 0 ZGV was created.

In the sixth week of testing, Network Activity Index was 26425, and as a result, 0 ZGV was created.

For the past two weeks, Network Activity Index was lower than it was on the first week (161469), and as a result, there was no emission in the blockchain those weeks.

Technical Updates
As described in the last Testnet Report, there were issues with nodes staying in sync while trying to calculate Activity Indexes and Emission. Over the past three or four weeks the development team has been working on performing those calculations asynchronously in order to keep the block interval down to one second. This update has passed our local tests and the updated nodes will be introduced into the testnet soon.

Another event that we wanted to share is that the testnet had a breakdown. The likely culprit was the Emission calculation event. This caused some nodes to become out of sync and go offline. Any nodes that were out of sync were voted out of active witness positions.

Tests still need to be performed on the Activity Index calculation (which happens daily) and the Emission event (which happens weekly). Making sure that the calculations function correctly on the testnet is an important step towards launching the main net. After these things have been tested, testnet participants can update their nodes and become active witnesses once again.

Node Update
This week an update of the nodes was released. Now the Activity Index and Emission are calculated asynchronously in three stages:

  • Collecting the source data for calculations, waiting the fixed delay to make it irreversible (currently 1000 blocks)
  • Starting the asynchronous calculations, waiting the fixed delay to complete the calculations for sure (currently 2000 blocks)
  • Applying the calculation results

Now all the witness nodes are updated and function normally. Next Monday we plan to test the Emission, and after that we’ll add to the testnet everyone who wants to become a witness.

Infrastructure

The Block Explorer
A brand new, completely redone version of the Block Explorer appeared this week. We fixed the Explorer’s mobile version display bugs and will continue working on it.

The Wallet
During past two weeks our team has been working on Stealth Transactions. It should be finished shortly.

A new memo-message function was added to the Wallet. You can now add a message to the token transaction.

Also, some small bugs in mobile version and design layout were fixed.

Future Plans
We plan to redraft the current version of the Wallet and refresh its design as well as refine the UI.

Media Publications About The Gravity Protocol

Thetodaycn.com
区块链研发公司 Gravity Solutions 致力为中小企开拓数十亿美元市场机遇

Kejiit.com
区块链研发公司 Gravity Solutions 致力为中小企开拓数十亿美元市场机遇

Isouthtech.com
区块链研发公司 Gravity Solutions 致力为中小企开拓数十亿美元市场机遇

Theshandong.com
区块链研发公司 Gravity Solutions 致力为中小企开拓数十亿美元市场机遇

Niuniuwang.cn
区块链研发公司 Gravity Solutions 致力为中小企开拓数十亿美元市场机遇

Newsbiz.cn
区块链研发公司 Gravity Solutions 致力为中小企开拓数十亿美元市场机遇

Itodaynews.cn
区块链研发公司 Gravity Solutions 致力为中小企开拓数十亿美元市场机遇

Ifuntech.cn
区块链研发公司 Gravity Solutions 致力为中小企开拓数十亿美元市场机遇



6
To Kill a Middleman: Why Blockchain is Vitally Important for Small Businesses

The term “Blockchain” has been a buzzword for a while. Everyone has heard of blockchain, but few use it outside of cryptocurrency trading and speculation. Usually, people talk about “creating trust where there is none” when referring to blockchain. You may also hear things along the line of, blockchain helping to “kill the middleman”.

However, many may not truly understand, what “the middleman” is, how to get rid of it, and, the main thing, why blockchain hasn’t been adopted on mass yet.

A full article about the issues which discourage SMEs to use blockchain and how Gravity Protocol is going to solve these issues - here on our Medium blog.


7
Gravity / Gravity Mobile Wallet
« on: July 16, 2018, 08:15:30 am »
Gravity Mobile Wallet


We’re happy to inform you that the work on the Gravity Mobile Wallet has already started. The Gravity mobile client is primarily а highly secure wallet for ZGV and custom token storage, and it also works as an access to the network.

The first version of the mobile client includes voting, accounts management, ZGV tokens transfer, the balance and your activity in the network. We plan to implement Gravity Wallet on the two major platforms, Android and iOS.

Full article with walletfeatures description, UI screenshots and future plans on the Wallet is here on our Medium blog.




8
Gravity / Gravity Testnet Report 10.06.2018–24.06.2018
« on: June 26, 2018, 10:17:15 am »


Hello everyone!
Last fortnight our team was actively working on the network, developing and improving it. We fixed some small bugs, solved the calculation delay problem (and we’re testing it now), and published several articles and manuals about working with testnet.

Statistics for 10.06.2018–24.06.2018

Number of accounts: 2520 (56 new)
Number of signed blocks: 2 458 262 (1,099,762 new)
Number of transactions: 681 716 (148,716 new)

Number of active witnesses: 25 (2 new)
Number of reserve witnesses: 25
Number of active committee members: 11
Number of reserve committee members: 29

Network Activity Index

Network Activity Index is calculated in the testnet once per week and its amount affects the size and availability of emission. Emission is released only if the Activity Index in the last week was greater than in any other previous week. This emission is distributed amongst all the accounts in the network according to their Gravity Index.

In the third week of testing, Network Activity Index was 80, and as a result, 0 ZGV was created.

In the fourth week of testing, Network Activity Index was 30, and as a result, 0 ZGV was created.

For the past two weeks, Network Activity Index was lower than it was previously, and as a result, there was no emission in the blockchain those weeks.

Acknowledgement

We are grateful to our team for their active work on the project and wee would also like to thank some people personally. Many thanks to Brendan Jensen, who brought lively discussions to our official Twitter account and actively helps the community on our Telegram dev chat and Discord channel. Many thanks to Rieki Cordon and Cryptick Cryptick as well for their interesting ideas and activities.

Technical Updates

A main distinctive feature of our system, is Network Activity Index calculation and the emission calculation based on that calculation. Both of these operations require vast amounts of computing power and they cannot be calculated immediately. At the beginning, when the testnet was launched, everything worked fine. But as the testnet grew larger, the calculations began to take more and more time. They quickly surpassed the one-second limit. This is an issue because if blocks are not calculated every second, the system will experience forks and desyncs. In the testnet, forks are solved automatically, but some of the values still remain out of sync. Due to this desync, the last emission was released with a delay.

Due to this desyncing, we moved the heavy part of the calculations to a parallel stream. The calculations will be done the same way, but this way, there will be аn insignificant delay, within reasonable limits. We plan to implement this calculation method on Monday, and it will be tested and approved for an update on Tuesday. At that time, we’ll notify all witnesses to update the software so we can check on how the nodes work. After that we’ll need a lot of transactions to break the last emission record, in order to trigger another emission.. At that point, we’ll see if the system is stable and if there are any bugs to be fixed.

Plans for the future

We continue to work on “The Battle of the Bots”, which aims to increase the amount of bots as well as their activity in the network. Stay tuned!

Infrastructure

Gravity Wallet

New user statuses were added to the Gravity Wallet, and here’s also a new module with a referral program. We fixed the adaptive template and some small local bugs. Gravity Wallet design is ready, and now we work on the back-end. We’ll also continue working on stealth-transactions.

Mobile Version

We’re also working on a mobile app for Android and iOS and soon we’ll publish an article on the process of developing the wallet, which we would love to have some feedback on..

Explorer

We fixed some small bugs. There also will be some refinements related to the referral program.

Governance

Links to guidelines were also added which can help users to test the network within their in user account. There is also a new Rewards module, where users can find out, how much they will receive for a specific action.

During these two weeks we’ve also worked on the Gravity website. We updated the copy, added a [b=https://www.gravityprotocol.org/gravity_yellow_paper.pdf]Technical Paper[/b], refined module where network testing is described, and added links to our bitcointalk and Reddit threads. There’s also a module for fortnight reports now. Wechat was also added to the Chinese version of our website.

Our priority now, is to complete and release stealth-transactions, finalize the referral program and refine adaptability. Next week we’ll start working on new modules of the Gravity Wallet — dashboard, for example, where the data from all accounts will be stored. We will also add a module with information about tokens.

Documentation

We’ve completed the White Paper. Everyone can have a look on it in our Telegram dev chat.

Media Publications about the Gravity Protocol

descentralizados.cl
 Gravity Protocol: Enciende la radio, ¡Estás al aire!

bitecoin.com
 区块链崭新应用-Gravity Solutions推出公用测试网

toutiao.com
 区块链崭新应用 — Gravity Solutions 为中小企制订协议和推出公用测试网

coinhoo.com
 区块链崭新应用-GRAVITY SOLUTIONS推出公用测试网


baijiahao.baidu.com
 区块链崭新应用 — Gravity Solutions 为中小企制订协议和推出公用测试网

p2peye.com
 区块链崭新应用-Gravity Solutions推出公用测试网

jincandou.com
 区块链崭新应用 Gravity Solutions 为中小企制订协议和推出公用测试网

sina.com.hk
 分散式賬本解決方案 區塊鏈的嶄新應用

yes-news.com
 分散式賬本解決方案 區塊鏈的嶄新應用

hkitblog.com
 分散式賬本解決方案 區塊鏈的嶄新應用


9
Gravity / Re: Gravity Testnet Instructions Set
« on: June 24, 2018, 05:18:14 pm »
Resyncing the node

Witnesses:

1. To avoid missing the blocks, witnesses have to use the backup node
Make sure that your backup node is running.

2. In the cli_wallet change your witness signing key to backup key

Code: [Select]
update_witness g1234r1234v1234z1234 "my url" ZGV...backupSigningPublicKey true
Make sure that block production continued from your witness

3. Restart the main node
docker:

Code: [Select]
docker-compose down
docker-compose up -d

without docker:

Code: [Select]
Ctrl+C
./witness_node --data-dir=data --resync-blockchain

Wait for synchronization after update

4. Switch your witness back to its main signing key

Code: [Select]
update_witness g1234r1234v1234z1234 "my url" ZGV...mainSigningPublicKey true
Make sure that block production continued from your witness

5. Restart the backup node the same way as the main

Non-witnesses:

1. Restart the node
docker:

Code: [Select]
docker-compose down
docker-compose up -d

without docker:

Code: [Select]
Ctrl+C
./witness_node --data-dir=data --resync-blockchain
Wait for synchronization after update



10
Gravity / How to update Gravity Protocol node
« on: June 24, 2018, 05:17:29 pm »
How to update Gravity Protocol node

We’re going to learn how to update Gravity Protocol node.

  • First, we’ll go to the node’s directory.
Code: [Select]
cd gravity-testnet-docker
  • Here we’ll stop our node.

Code: [Select]
sudo docker-compose down
  • Then we’ll receive the update from github.

Code: [Select]
git pull origin
  • And new versions of packages from Dockerhub.

Code: [Select]
sudo docker-compose pull
  • Now we’ll run the node in daemon mode.

Code: [Select]
sudo docker-compose up -d
  • If you prefer, you can display current sync status on the screen.

Code: [Select]
sudo docker-compose logs — tail 10 -f
  • To hide the logs, press *Ctrl+Z.


11
How to make proposals and to edit a blockchain configuration

We’re going to learn how to make proposals and to edit a blockchain configuration.

  • First we’ll open cli-wallet when the node is launched.
Code: [Select]
sudo docker-compose exec gravity_node cli_wallet -w /var/lib/gravity/wallet.json
  • Then we’ll unlock the wallet.

Code: [Select]
unlock 1234567
  • And now we’ll get to work.
  • We’ll get current configuration values:

Code: [Select]
get_global_properties
  • We’ll make a proposal to change the interval between the blocks using the template:

Code: [Select]
propose_parameter_change [from account] [time, the value must be greater than CURRENTTIME + committee_proposal_review_period and lower than CURRENTTIME + maximum_proposal_lifetime] {json with the new values} true
  • For example:

Code: [Select]
propose_parameter_change “g2090i8190e9280o7900” “2018–06–13T17:28:00” {“block_interval”: 3} true
  • Now we’ll get the number of proposal id.

Code: [Select]
get_account_history “g2090i8190e9280o7900” 1
2018–06–13T17:00:20 proposal_create_operation g2090i8190e9280o7900 fee: 20.00007 ZGV result: 1.10.1

  • And we’ll vote.

Code: [Select]
approve_proposal g2090i8190e9280o7900 1.10.1 {“active_approvals_to_add” : [“g2090i8190e9280o7900”]} true
  • Now we’ll close the cli-wallet using Ctrl+C

And we’ll change the fees:

  • First we’ll get current values of the configuration

Code: [Select]
get_global_properties
  • Then we’ll make a proposal to change the fees.

Code: [Select]
propose_fee_change “g2090i8190e9280o7900” “2018–06–13T04:32:00” {0 : {“fee”: 1, “price_per_kbyte”: 0,1}, 34 : {“fee”: 10000000}} true
  • Now we’ll get the number of proposal id.

Code: [Select]
get_account_history “g2090i8190e9280o7900” 1
2018–06–13T17:00:20 proposal_create_operation g2090i8190e9280o7900 fee: 20.00007 ZGV result: 1.10.1

  • And vote:

Code: [Select]
approve_proposal g2090i8190e9280o7900 1.10.1 {“active_approvals_to_add” : [“g2090i8190e9280o7900”]} true


    12
    Gravity / Comittee Memember Registration Tutorial
    « on: June 24, 2018, 05:10:32 pm »
    Comittee Memember Registration Tutorial

    We’ll be learning how to create a member of the committee from an account.

    Video instrustion is here.

    • To begin, we need to open the file with the program node.
    Code: [Select]
    cd gravity-testnet-docker
    • Now, let’s start our node with demonization.

    Code: [Select]
    sudo docker-compose up -d
    • Next, run the cli-wallet with extra parameters.

    Code: [Select]
    sudo docker-compose exec gravity_node cli_wallet -w /var/lib/gravity/wallet.json
    • At this time, we’ll create a password for the wallet.

    Code: [Select]
    set_password password
    • Unblock the wallet and we’ll be sent into our account.

    Code: [Select]
    unlock password
    • Here, we’ll import our account.

    Code: [Select]
    import_key “your-account” “your-active-private-key”
    • Now that we’ve done this, we have a lifetime membership for this account,

    Code: [Select]
    upgrade_account “account” true
    • From this account we’ll be creating a member of the committee.

    Code: [Select]
    create_committee_member “account” “url” true
    • Execute the following command, an example is in the video description.
    • Now close the cli-wallet using the keyboard shortcut Ctrl+C.
    • Now your account is a candidate to be a member of the committee.
    • All that is left to do is convince people to vote for you.

    If you’ve already created a witness node, you can skip the password setting steps for the wallet, import the account and purchase a lifetime membership.


    13
    Gravity / Turn a node into a witness node
    « on: June 24, 2018, 05:02:04 pm »
    Turn a node into a witness node

    We’re going to turn a node into a witness node.

    Video instructions you can find here.

    • First, open node’s directory.
    Code: [Select]
    cd gravity-testnet-docker
    • Then, run the node in daemon mode, and run the cli-wallet with advanced settings.

    Code: [Select]
    sudo docker-compose up -d
    sudo docker-compose exec gravity_node cli_wallet -w /var/lib/gravity/wallet.json
    • Next, Set a password for the wallet and unblock the wallet.

    Code: [Select]
    set_password password
    unlock password

    • Import your account in the wallet.

    Code: [Select]
    import_key “your-account” “your-active-private-key”
    • Here’s where you’ll get a lifetime membership, and then create a witness.

    Code: [Select]
    upgrade_account “account” true
    create_witness “account” “url” true

    • Now you’ll need to get your witness-ID.

    Code: [Select]
    get_witness “account”
    • As you can see, the witness-ID for this specific account is “1.6.*” You’re going to want to memorize it or write it down. There is also a public key for signing blocks which also needs to be saved.
    • Now you can derive a private key using the public key, save the private key as well.

    Code: [Select]
    get_private_key [public signing key] (without quote)

    • Now close the cli-wallet using Ctrl+C.
    • After that, you’ll need to edit the config.ini file.

    Code: [Select]
    sudo nano ./data/config.ini
    • Add your witness-ID, and replace the keys.
    • Don’t forget to delete the sharp symbol (#) in front of witness-id to turn the comment line into a code line.
    • After you’ve added your witness-ID and replaced the keys, press Ctrl+X.
    • Then press Y to save the changes.
    • Now you’ll need to restart the node. For that, use the docker-compose down and docker-compose up commands.

    Code: [Select]
    sudo docker-compose down
    sudo docker-compose up -d
    • And there you have it, a running witness node!
    • Now, all you have to do is convince people to vote for you.


    14
    Gravity / Install Gravity Node for Public Testnet with Docker
    « on: June 24, 2018, 04:56:19 pm »
    Install Gravity Node for Public Testnet with Docker

    We’ll learn how to install a gravity-protocol node using another method. It is also suitable if you have a version of the operating system differs from Ubutnu 16.04. You need to install: git, docker, docker-compose. If you need use the command: docker login.

    See video instruction here.

    • First of all we need to clone the repository, we do this using git clone.

    Code: [Select]
    git clone https://github.com/GravityProtocol/gravity-testnet-docker.git
    • Next, we’ll check the newly created directory. As you can see, the directory is there, so let’s cd to it.

    Code: [Select]
    ls
    cd gravity-testnet-docker

    • Now we need to download an image with the node. We’ll use docker-compose pull, to do that.
    Code: [Select]
    sudo docker-compose pull
    • After the image has downloaded, we need to boot up our node.
    • Let’s use docker-compose up, to do that.

    Code: [Select]
    sudo docker-compose up
    • Soon you’ll see blocks being created.
    • To terminate the node you’ll need to press Ctrl+C.


    15
    Gravity / Install Gravity Node for Public Testnet
    « on: June 24, 2018, 04:52:55 pm »
    Install Gravity Node for Public Testnet

    In this tutorial we’re going to show you how to assemble your own Gravity protocol node. Choose a server with Ubuntu 16.04 for the correct node installation. You need to install: git, docker, docker-compose. If you need use the command: docker login.

    See the video instruction here.

    • Please note, that you must have git, docker and docker compose installed on your machine.
    • First we’ll clone the repository by using git clone.

    Code: [Select]
    git clone — depth 1 https://graphenelab.unfuddle.com/git/graphenelab_gravitypublic -b testnet
    • Right now, our repository is still private so in this video I’ll need credentials to log in.
    • After the clone is complete, you need to double check the that the new folder has been created.

    Code: [Select]
    ls
    • Then switch to that folder.

    Code: [Select]
    cd graphenelab_gravitypublic
    • Now we need to give the command to compile the node.
    • Please note that you may need to use sudo depending on the type of user account credentials that you have.

    Code: [Select]
    sudo docker-compose build
    • Now you’ll have to wait for approximately 20 minutes for the node to compile.
    • There will be some warnings in red, but you can safely ignore them.
    • Now, that the node is compiled, you need to boot up the node. We’ll use the ‘docker compose up’ command for that.

    Code: [Select]
    sudo docker-compose up
    • After a while, you’ll see blocks being created every few seconds.
    • To terminate the node press Ctrl+C.


    Pages: [1] 2 3