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

Trouble with broadcasting #114

Open
MrXtar opened this issue Mar 16, 2017 · 4 comments
Open

Trouble with broadcasting #114

MrXtar opened this issue Mar 16, 2017 · 4 comments
Labels

Comments

@MrXtar
Copy link

MrXtar commented Mar 16, 2017

Chrome. Windows.

I'm trying to broadcast custom_json. And sometimes the transaction not included in blockchain.

For example, sending custom JSON {"test":"test0.9343139010386905"}

with command:

steem.broadcast.customJson(
'MY_WIF',
[],
['xtar'],
'test',
'{"test":"test0.9343139010386905"}',
function(err, result) {
console.log(err, result);
});

Getting response. err is null and result is:

{"ref_block_num":3762,"ref_block_prefix":780210655,"expiration":"2017-03-16T15:09:05","operations":[["custom_json",{"required_auths":[],"required_posting_auths":["xtar"],"id":"test","json":"{"test":"test0.9343139010386905"}"}]],"extensions":[],"signatures":["1f4b4b8f43f0224fdfc8d5bd8175bd49b98c3eb8a881bd62686f1708c6fc481d9534cba6cfc3a4fea555fd4c36aa0f2086b31f43a654e1b282f699278a25928b96"]}

image

Immediately after sending I see the transaction in my history with steem.api.getAccountHistory, But it disappears in 3 seconds.

And no transaction in blockchain included:
https://steemd.com/@xtar

Not every time. Sometimes.

Why it happening?

Try it many times. Do you have the same issue too?

@roadscape
Copy link
Contributor

Are you still experiencing this issue?

@yamadapc
Copy link
Contributor

yamadapc commented Jul 5, 2017

Seems like this would not be a bug in this library?

@yamadapc yamadapc added the Bug label Jul 5, 2017
@voorash
Copy link

voorash commented Aug 9, 2017

This sounds like the bug in steem itself where posts were showing up and then vanishing. I don't know if there is a bug number for it but reports of it were all over the place on steemit.

@marvin-we
Copy link

I don't think that this is a bug:

A custom json operation has 2 validations:

  • The id has less than 32 chars
  • and the json data needs to valid UTF8 json

--> That means the operation is always acccepted.

When the operation is now added into a block (which happens ~3 seconds) Steem is searching for something that can apply the block by using the id. E.g. if the ID is set to "follow", the follow plugin will say "Hay, I can process this shit" and will check and apply it. As you used "test" as the id and I wasn't able to find something that can process this id in the source code, I guess that the custom_operation_interpreter is used which simply returns 0. So I would assume that the operation is not accepted to added to a block ...

As this is an official steem repo you may have better connections to clarify this with a Steem Dev Team member, but from my point of view it is working as expected.

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

No branches or pull requests

5 participants