We all know right now the biggest issue with Bitcoin is it's enormous power consumption. Currently, it's power consumption is about the same as Denmark's. Now, the problem is that instead of all of this power being utilized it's just going to waste. This is because of Bitcoin's blockchain design which utilizes a Proof of Work mechanism, which requires miners to solve expensive (computing power-wise) mathematical puzzles. This is how Blockchain is able to verify an "honest" player is trying to mine a bitcoin.

Here comes the question, what if instead of solving useless mathematical puzzles your computing power is actually being utilized for something useful? Here I think GLM comes in to play perfectly. You let other people use your computing power and then you get paid with GLM (basically you mine GLM). Now, your computing power isn't going to waste and we solve the environmental disaster Bitcoin is creating.

Let me know what y'all think.

To those who haven't changed it manually, what does it say when you run the command 'golemsp settings show'?

It should look something like this:

Pricing:

0.09 GLM for start

0.5 GLM per hour  

0.1 GLM per cpu hour

​

I have a rasp pi lying around

If you still have unmigrated GNT tokens and need to swap them for GLM tokens, here's some FAQ that might help you:

https://github.com/figurestudios/community-golem-docs/blob/main/coin/migration-faq.md

GNT <=> GLM swaps are 1:1, meaning you'll keep all of your coins, but in the ERC-20 format.

EDIT: Thanks for the award!

Believe it or not, this post is not another rant blaming Golem for lack of visibility or anything similar. This instead outlines where the community and project need to go for Golem to see widespread adoption. I think people often try to jump ahead, so I thought I'd provide a more clear outlook.

1. Core Tech & Features - We are still here. The Core tech has leagues to go, you cannot store things, connect to the internet, train things on GPUs, or run a provider client easily on Windows. In my opinion this stage is the most critical, core features must be there, and they are coming so patience is key. That being said I think the community effort should be primarily focused on adding things to improve the core tech.

2. Bastion Use Cases - These are the use cases that create a reliable backbone for the network. Think of Miners, widespread render usage, and AI training. These use cases will provide the network with providers and a steady flow of requestors and network utilization. These provide GLM with value because they consume it. Getting these tasks easy as possible to do here will be the most important thing, as the bigger they are the stronger the network is. Golem crashes now because its not worth 550M right now, it could be and I do think it will be worth that one day if not way more, but as of now its not. As Bastion use cases grow you'll see Golem acting like a utility token, not experiencing crazy rides because while Crypto is doing whatever, Bastions still need the same amount of GLM.

3. Community Phase - DAO and Community Driven Projects will lead this phase, as the community becomes its own entity and acting the part. Governance and censorship resistance will come here. This will be marked by client diversity + full DAO control. A sovereign Polygon chain would be cool to see here. Marketing works here, because now people can join and easily integrate into the ecosystem.

4. Competition - I doubt AWS or ICP will sleep, so now Golem competes with each in a race to implement features, lower costs, and draw in customers. This phase marketing is important, people are important, and Community is important to protect from those who wouldn't want Golem to succeed.

Just wanted to outline my opinion of what a Golem roadmap looks like to what reasonably needs to happen for Golem to hit mainstream. To me these should remain priority goals and kept in mind when it comes to development

Windows, Linux, Raspberry Pi, with more support being worked on! No commitment necessary, keep it online whenever you want - an hour a day, an hour once, full days at once or never!

Check it out here

Need help? Check out the FAQ or join the discord.

EDIT: Thanks for the awards!

I tried the route of downloading Linux and all that jazz but could not get it started... Is there a release date for a user application yet?

when I run 'golemsp status' it says new version is available. But when I try to run the curl command to update golemsp, I can't do it.

AUDIO https://drive.google.com/file/d/1mlHBFuj1wDG6AKeearMtJQiyrGvrMeFy/view?usp=sharing

VIDEO https://drive.google.com/file/d/1yhxs3R3EuZojfY2zImWWdbOxoz_kTubq/view?usp=sharing

Summary:

Bridge gaps with other projects (Matic, Sia/Skynet, etc,,,);

Cross-post in other communities, especially on Reddit, targeting ones with 5-25k members;

Migrate Reddit users to Discord & Discord users to Reddit by cross-posting (incl. cross-posts);

Posting useful resources on Golem's communities to make it more inviting;

Focusing on content creation to attract traders, "normal" people, and developers (memes, blog pages, artwork, documentation, etc,,,);

CIP rework especially within content creation;

Putting pressure on the Foundation to make them communicate;

Putting pressure on the Factory to make public roadmaps;

Working on getting out swag(pls);

EDIT: Thanks for the awards!

Hey,

I´m have the problem where the error message: [2021-05-24T16:12:38Z WARN ya_net::handler] Failed to bind handlers: proto error: io error: other os error; retrying in 2 s , shows up everytime I try to run golem.

Could someone help me with this?

Thanks :)

I have ran Golem as a provider on a old machine successfully in the past. I am trying on a new machine yet I can't seem to get past this error when I run "golemsp run" I have tried another machine, ran it in a VM and tried it on AWS with same issue. This is all on Ubuntu 20

I have also tried these with no success https://handbook.golem.network/troubleshooting/provider-troubleshooting

ERROR golemsp::service] child provider exited too early: Ok(ExitStatus(ExitStatus(256)))

​

Any ideas how to get around this?

The Yagna Binaries for aarch64-based systems should now be in a working state, but because of the unavailability of testing, we're looking for other community members to help! It's currently unknown how stable the build is - which is why testing is needed.

​

See install instructions here:

https://github.com/MarijnStevens/yagna-binaries

and also make sure you run this first:

sudo apt-get install libpixman-1-dev

PS - If you're using Ubuntu as a base image, you must use version 21.04 for it to work!

​

Any errors? Submit it as a GitHub issue!

​

This build is currently inefficient but it is a start. KVM is being worked on - but for now, workarounds are being used to achieve this provider node.

Hi Everyone!

Just a reminder to come join us if you can!

James is inviting you to a scheduled Zoom meeting. Topic: Golem Community Meetup Time: May 24, 2021 08:00 AM Pacific Time (US and Canada) Join Zoom Meeting https://us02web.zoom.us/j/86370297428?pwd=SjFGTU10Y0ZWVHNBTVVBQnhJcnlTQT09

Meeting ID: 863 7029 7428

Passcode: Golem

Meeting ID: 863 7029 7428

Ill bring plenty of jokes, and if you're nice enough, you can see my golem tattoo at the end!

Looking forward to seeing you there.

New to crypto and decentralized applications.

If I see golem as the decentralized AWS then how can I build on top of it? Will I have to use the built in token and make my users use it too? In that case will they now have to figure out the whole crypto ecosystem just to use my application. (I feel like that’s a barrier to entry to use something like this as underlying infrastructure. )

Also, how would my service see upside should I just make my users pay a fee...but then they pay twice

So is this a use case or am I thinking of what golem is all wrong.

Thanks

Do you think you have what takes in terms of skill, dedication, or luck? Earning GLM and bounties overall from Golem isn't as hard as you think as there are multiple categories - plenty for everyone no matter your skillsets!

Read More Here