Author Topic: time_point_sec format  (Read 1917 times)

0 Members and 1 Guest are viewing this topic.

Offline tytus

propose_parameter_change first-user "2016-10-01T18:45:11" {"block_interval" : 6} true

this succeeded ! thanks !!!

Offline tytus

Not on bitshares, on a testnet. I am trying to learn about the functionality.

unlocked >>> propose_parameter_change first-user "2016-09-05T20:15:11" {"block_interval" : 6} true
propose_parameter_change first-user "2016-09-05T20:15:11" {"block_interval" : 6} true
1789965ms th_a       wallet.cpp:1923               sign_transaction     ] Caught exception while broadcasting tx c283d1f52d387762553da42710abefc281d0eaed:  0 exception: unspecified
10 assert_exception: Assert Exception
!o.review_period_seconds || fc::seconds(*o.review_period_seconds) < (o.expiration_time - d.head_block_time()): Proposal review period must be less than its overall lifetime.

unlocked >>> propose_parameter_change first-user "2016-10-05T20:15:11" {"block_interval" : 6} true
propose_parameter_change first-user "2016-10-05T20:15:11" {"block_interval" : 6} true
1842255ms th_a       wallet.cpp:1923               sign_transaction     ] Caught exception while broadcasting tx ad42f368eb9aa1d88ba965fa1b3f9570b5a4b9d2:  0 exception: unspecified
10 assert_exception: Assert Exception
o.expiration_time <= d.head_block_time() + global_parameters.maximum_proposal_lifetime: Proposal expiration time is too far in the future.

I can not find the right parameters :-( I will try to lookup the web

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
something like this:    "2016-09-02T15:15:11"
but why would you propose a parameter change on bitshares?

Offline tytus

what is the format of timestamp to use in "propose_parameter_change" ?