Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Proposal] Option to track block timestamp for local wallet/node without including in blockchain #105

SergiySW opened this issue Apr 13, 2017 · 3 comments


3 participants
Copy link

commented Apr 13, 2017

Perhaps similar way as Byteball
A: There are no timestamps in Byteball protocol, they are just not needed. That's why there are no reliable timestamps.
The ones you see in History tab are the times and dates when your wallet first learnt about the transaction (or, if you are on light wallet, when the light vendor first learnt about the tx).

Also it would be useful for services that confirm incoming RaiBlocks transactions based on time (such as 1-2-3 minutes from receiving)


This comment has been minimized.

Copy link

commented Aug 23, 2018

We track a few different timestamps in the database -- does that resolve this issue ?


This comment has been minimized.

Copy link
Collaborator Author

commented Aug 23, 2018

No, we track only last account change
Partially solved with #994

@zhyatt zhyatt added this to Unscheduled in V18 Dec 31, 2018

@SergiySW SergiySW moved this from Unscheduled to CP 3 (2018-01-23) in V18 Jan 1, 2019

@SergiySW SergiySW moved this from CP 3 (2018-01-23) to CP 2 (2018-01-16) in V18 Jan 1, 2019


This comment has been minimized.

Copy link

commented Jan 28, 2019

After sideband updates this issue resolved with #994

@zhyatt zhyatt closed this Jan 28, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.