Skip to content
This repository has been archived by the owner on Apr 15, 2019. It is now read-only.

Invalid timestamp fixes - Closes #365 #500

Merged
merged 1 commit into from
Jul 20, 2017
Merged

Conversation

reyraa
Copy link
Contributor

@reyraa reyraa commented Jul 20, 2017

@reyraa reyraa requested a review from Isabello July 20, 2017 09:51
@reyraa reyraa self-assigned this Jul 20, 2017
@reyraa reyraa changed the base branch from development to 1.0.2 July 20, 2017 09:57
package.json Outdated
@@ -38,7 +38,7 @@
"debug": "=2.2.0",
"jasmine-spec-reporter": "=3.3.0",
"jquery": "=2.2.4",
"lisk-js": "=0.4.2",
"lisk-js": "^0.4.4",

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should be =

secondSecret = null) => Peers.sendRequestPromise('transactions',
{ recipientId, amount, secret, secondSecret });
secondSecret = null, offsetSeconds = 10) => Peers.sendRequestPromise('transactions',
{ recipientId, amount, secret, secondSecret, offsetSeconds });

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this cover voting transactions, second sig reg etc? All tx need to use this new property.

@reyraa reyraa force-pushed the 365-invalid-timestamp branch from 9e0372a to d841445 Compare July 20, 2017 10:20
@Isabello Isabello changed the title Invalid timestamp - Closes #365 Invalid timestamp fixes - Closes #365 Jul 20, 2017
@reyraa reyraa requested a review from yasharAyari July 20, 2017 12:29
Copy link

@Isabello Isabello left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great !!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants