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

On responses via Gamma - blockhight is wrong. #26

Closed
EsterEdelstein opened this issue Nov 10, 2018 · 2 comments
Closed

On responses via Gamma - blockhight is wrong. #26

EsterEdelstein opened this issue Nov 10, 2018 · 2 comments
Assignees
Labels
bug Something isn't working gamma Gamma - local ORBS blockchain

Comments

@EsterEdelstein
Copy link
Contributor

{"OutputArguments":[{"Name":"uint64","Type":"uint64","Value":600}],"CallResult":1,"BlockHeight":7347,"BlockTimestamp":0}.
Problem with the “Name” field

Blocktimestamp- is always 0.

BlockHeight - also looks like a random number.

@EsterEdelstein EsterEdelstein added bug Something isn't working gamma Gamma - local ORBS blockchain labels Nov 10, 2018
@EsterEdelstein EsterEdelstein changed the title On respones via Gamma - the Blocktimestamp is always 0, also blockhight seems wrong. On responses via Gamma - the Blocktimestamp is always 0, also blockhight seems wrong. Nov 10, 2018
@EsterEdelstein
Copy link
Contributor Author

The block timestamp looks good, the block hight is still wrong.
see example of the first block created via gamma v0.5
esticontract.go -signer user1
{
"RequestStatus": "COMPLETED",
"TxId": "DHj4zMCMVCPaHQhWg8hHTMoXyLmnyJuwdtDxNJ329rDdLa3dQoSyRcD",
"ExecutionResult": "SUCCESS",
"OutputArguments": [],
"TransactionStatus": "COMMITTED",
"BlockHeight": "17775",
"BlockTimestamp": "2018-11-27T12:21:27.844Z"
}

@talkol

@EsterEdelstein EsterEdelstein changed the title On responses via Gamma - the Blocktimestamp is always 0, also blockhight seems wrong. On responses via Gamma - blockhight is wrong. Nov 27, 2018
@talkol
Copy link
Member

talkol commented Nov 29, 2018

Block height is not wrong.. the system is closing blocks very quickly so empty blocks are closed when the server is idle.

We can slow the rate down, but that will mean that if you send a transaction you will wait this time.

Meaning if block time was 1 second, then when you send a transaction you may need to wait up to a second until you get a response.

What time do you want?

@talkol talkol closed this as completed Dec 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working gamma Gamma - local ORBS blockchain
Projects
None yet
Development

No branches or pull requests

3 participants