Author Topic: wrong timestamp: "next_maintenance_time": "1970-01-01T00:00:00"  (Read 122 times)

0 Members and 1 Guest are viewing this topic.

Offline yousq

  • Newbie
  • *
  • Posts: 1
    • View Profile
hi, I'm working in a new cryptocurrency exchange, and we are planning to support BTS.

I have created a private testnet using my own "genesis.json" in which the initial_timestamp is 2018-05-12T09:47:40,

But the command "get_dynamic_global_properties" in cli_wallet returned :
...
  "time": "2018-05-12T09:47:40",
  "current_witness": "1.6.0",
  "next_maintenance_time": "1970-01-01T00:00:00",
  "last_budget_time": "1970-01-01T00:00:00",
...

why dose the "next_maintenance_time" come to be "1970-01-01T00:00:00"(my system time is correct)?

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 3205
    • View Profile
    • Steemit Blog
  • BitShares: abit
  • GitHub: abitmore
Re: wrong timestamp: "next_maintenance_time": "1970-01-01T00:00:00"
« Reply #1 on: May 30, 2018, 04:59:44 am »
hi, I'm working in a new cryptocurrency exchange, and we are planning to support BTS.

I have created a private testnet using my own "genesis.json" in which the initial_timestamp is 2018-05-12T09:47:40,

But the command "get_dynamic_global_properties" in cli_wallet returned :
...
  "time": "2018-05-12T09:47:40",
  "current_witness": "1.6.0",
  "next_maintenance_time": "1970-01-01T00:00:00",
  "last_budget_time": "1970-01-01T00:00:00",
...

why dose the "next_maintenance_time" come to be "1970-01-01T00:00:00"(my system time is correct)?
Post your genesis.json somewhere.

Show more output of "get_dynamic_global_properties".

I guess after generated the first block, all the values will change.
BTS account: abit
BTS committee member: abit
BTS witness: in.abit