Jump to content

Recommended Posts

13 hours ago, Marco Nilsson said:

 

Something sounds really off as you should definitely have staked by now. What's the beacon _public_ key in your config so we can match that to the network. 

Executed beaconstatus for it:

"Public Key" : "044f214bb7dc338e0e697809b506abf15949e816fa9dfba78a2a2fb4c09c888520cb666770bc320cc48dd10bde686dc263e5c073cb705d69aa89823155db4b562c"

 

Thanks for the helping out.

Share this post


Link to post
Share on other sites

My Problem is, I'm still listed in beaconreport as

"d92b9525a14df746f32ca1f14513ffc" : "S4ChkhqJHyrcbGSFUrC2YNz5GPLFVwLLfA"  and not as

"cd92b9525a14df746f32ca1f14513ffc" : "S4ChkhqJHyrcbGSFUrC2YNz5GPLFVwLLfA"

The first character is missing.

As far as I know, there is a hotfix available. But when I'm trying to compile it on linux, the wallet says, for testnet-staking only.

Why is it taking so long for that hotfix to work in the next release?

Share this post


Link to post
Share on other sites
23 minutes ago, KLiK said:

Executed beaconstatus for it:

"Public Key" : "044f214bb7dc338e0e697809b506abf15949e816fa9dfba78a2a2fb4c09c888520cb666770bc320cc48dd10bde686dc263e5c073cb705d69aa89823155db4b562c"

 

Thanks for the helping out.

 

That is the same as I see. Can you double check that your config carries the same pub/priv keys?

Share this post


Link to post
Share on other sites
6 minutes ago, JoeWinkler said:

Why is it taking so long for that hotfix to work in the next release?

 

We had a lot of crashes in Windows, but we found the issue and are doing the final test and release preparations. Unless something pops up it should be a few days.

Share this post


Link to post
Share on other sites

"6f64d69eb8c5ee9cd24178b589af83f" : "\r\nVivamus aliquam leo at nisl tristique eleifend. Nunc interdum elit eu lorem pulvinar euismod. Etiam ac sem non massa tincidunt congue quis eu enim. Vivamus vitae augue vel justo lobortis convallis. Integer et orci eget lorem placerat venenatis ac vitae mi. Curabitur vulputate nunc nunc, vitae hendrerit nulla vulputate id. Sed risus dui, convallis eget sem sed, ornare posuere mauris. In et tortor non ipsum cursus bibendum. Praesent ac dolor volutpat, imperdiet elit ac, tempus urna. Donec vitae volutpat lacus. Praesent felis nulla, tincidunt sed ligula at, consectetur consequat sem. Aliquam eu pharetra lorem. Nullam rhoncus id velit nec vestibulum. Morbi consequat massa et eros iaculis, at euismod augue finibus.\r\n\r\nCras aliquet augue sagittis viverra maximus. Maecenas metus dui, faucibus eu faucibus eu, porttitor sit amet nulla. Curabitur nibh eros, vestibulum ut massa non, viverra laoreet sapien. Duis sollicitudin nisi ac magna feugiat finibus. Vivamus vitae urna et risus condimentum ullamcorper. Integer a justo a tellus vulputate dapibus. Morbi consectetur egestas leo, ut rhoncus nisl fermentum ut. Ut blandit pulvinar sem vitae maximus. Maecenas scelerisque pulvinar eros, in vehicula ligula ultricies eget. Quisque at molestie nisl. Interdum et malesuada fames ac ante ipsum primis in faucibus.\r\n\r\nNullam ultricies lorem quis enim molestie, in ultrices lorem placerat. Etiam vulputate turpis id tempor egestas. Mauris feugiat quam mattis, sodales eros vitae, semper dui. Cras auctor ipsum et nunc fermentum, eu elementum nibh vulputate. Etiam nec viverra mi. Morbi diam augue, luctus vitae nisl sit amet, varius pharetra ipsum. Nullam metus elit, luctus eu metus vitae, tristique vulputate nisl. Praesent nec nisl vitae erat venenatis tempor non in nunc. Nunc at leo enim. Aliquam imperdiet vitae turpis et aliquet. Donec porta, ex in rhoncus tempor, dolor massa sagittis ante, eget egestas velit diam lobortis risus. Suspendisse volutpat, dui et rutrum hendrerit, neque erat ornare tortor, eu interdum purus lacus ut nulla. Duis vehicula quis nulla at congue. Suspendisse potenti.\r\n\r\nAliquam tortor quam, consectetur vel nisi in, facilisis malesuada urna. Praesent sodales mi eu risus vestibulum, quis ornare lectus convallis. Nunc id mauris justo. Vivamus in augue vitae dui dignissim porttitor venenatis non ipsum. Etiam sed aliquam ligula. Proin eget purus a ex pulvinar viverra a sed orci. Donec vitae elementum leo. Mauris eu eleifend ipsum. Sed eu sapien hendrerit, elementum quam quis, auctor lacus. Cras dignissim laoreet lorem non suscipit. In nec nulla at nisi laoreet euismod. Nulla tempus pulvinar risus, id tempor mauris consectetur vitae. Quisque quis ipsum at dui laoreet aliquam eu eu augue. Suspendisse id vulputate neque, ut pharetra tellus.\r\n\r\nInteger sit amet sagittis lacus. Integer id eros eu quam fermentum finibus. Maecenas condimentum enim vitae tempor fermentum. Quisque ultrices congue ipsum, tempor congue lacus elementum non. Nam luctus, turpis id molestie egestas, eros enim euismod libero, quis congue nisi tellus interdum tellus. Maecenas id ornare ex. Donec dapibus luctus justo, non convallis diam vehicula eget.",

Will it fix that issue in beaconreport as well?

Share this post


Link to post
Share on other sites
On 7.4.2018 at 6:03 AM, queiftm said:

Hi

When doing a execute beaconreport in the Gridcoin Debug Console the following shows up in the results a ways down:

 

"6f64d69eb8c5ee9cd24178b589af83f" : "\r\nVivamus aliquam leo at nisl tristique eleifend......(shortened)

 

What does this mean?

 

That problem exists for a long time now.

I haven't used Slack before.

 

Share this post


Link to post
Share on other sites
2 minutes ago, JoeWinkler said:

 

That problem exists for a long time now.

I haven't used Slack before.

 

 

PM me your e-mail and I'll send you an invite.

Share this post


Link to post
Share on other sites
10 hours ago, Marco Nilsson said:

 

A more direct communication platform like IRC, Telegram and Discord.

Just mined 300 GRC after 2 months around midnight...don't know how, don't know why? After 2 days ti came, even though I've run the GRC wallet weekly to sync & last week I've run it all week. :/

Share this post


Link to post
Share on other sites

I've tried to delete my beacon as in this instruction:

As you can see in
https://www.gridcoinstats.eu/cpid/cd92b9525a14df746f32ca1f14513ffc

I've got a successful message by 0.00022GRC, but still my beacon is not deleted,
so I've tried it again and again and again, but my beacon is still there.

What can I do, to delete my beacon?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

Cryptocurrenytalk Logo

 

News, information, and discussions about cryptocurrencies, blockchains, technology, and events. Blockchaintalk is your source for advice on what to mine, technical details, new launch announcements, and advice from trusted members of the community. Cryptocurrencytalk is your source for everything crypto. We love discussing the world of cryptocurrencies.

 

   
×

Important Information

By using CRYPTOCURRENCYTALK.COM, you agree to our Terms of Use.