Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in
D
destream-blockchain
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 2
    • Issues 2
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Registry
    • Registry
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • DeStream-public
  • destream-blockchain
  • Issues
  • #3

Closed
Open
Opened 7 years ago by Anton Borisov@root
  • Report abuse
  • New issue
Report abuse New issue

Create own TestNet

Created by: AK315

Please solve the reCAPTCHA

We want to be sure it is you, please confirm you are not a robot.

  • Anton Borisov
    Anton Borisov @root commented 7 years ago
    Owner

    Created by: mbdestream

    1. Stratis source codes analysis to understand what part of Stratis is in charge for communication with network;
    2. Reading available stratis documentations and searching information about testnet creation.
  • Anton Borisov
    Anton Borisov @root commented 7 years ago
    Owner

    Created by: AK315

    To learn how to create our own TestNet we need to explore function call chain from starting own block-chain node (by means of cli command) until other block-chain nodes are being found and connected.

  • Anton Borisov
    Anton Borisov @root commented 7 years ago
    Owner

    Created by: mbdestream

    1. Node traffic analysis to figure out what remote addresses are used;
    2. Node deployment on test server and tuning it, running;
    3. Source codes research, rework code places to replace ip-addresses and dns-names with our test server ip and dns-addresses;
    4. Traffic analysis to understand whether the local node communicates with test server node;

    On current stage we have successfully connected local development node with test server node. But we have to figure out why the traffic between our nodes contains requests to unknown ip-addresses.

  • Anton Borisov
    Anton Borisov @root commented 7 years ago
    Owner

    Created by: AK315

    Now we have to introduce a new key in Node cli that will designate using of our DeStream TestNet

  • Anton Borisov
    Anton Borisov @root commented 7 years ago
    Owner

    Created by: mbdestream

    Cli is extended by adding new command line arguments:

    1. "-destreamtest" to run node configured to connect with destream test node;
    2. "-destreamtestserver" to run test server node.
  • Anton Borisov
    Anton Borisov @root commented 7 years ago
    Owner

    Created by: AK315

    OK. Implemented.

Please register or sign in to reply
Assignee
No assignee
Assign to
None
Milestone
None
Assign milestone
None
Time tracking
No estimate or time spent
None
Due date
No due date
0
Labels
None
Assign labels
  • View project labels
Confidentiality
Not confidential
Lock issue
Unlocked
1
1 participant
user avatar
Anton Borisov
Reference: destream-public/destream-blockchain#3