Glad to hear it, dont forget you can stake your $SLR for an additional 2% income, and you will be supporting the SolarCoin blockchain by doing so.

Another 752 new claims paid in June... https://solarcoin.enapter.com/transactions?page=16&query=agrt

Over 2,000 net-new claims paid in May, looks like there was a backlog, but still that's great growth.  Source: https://solarcoin.enapter.com/transactions?utf8=%E2%9C%93&query=aagrt

Global node distribution is also becoming very healthy with hundreds of peers all over the globe, impossible to get a true representation but there are nodes as far afield as New Zealand, South Africa, Chile and Canada, with major concentrations in Australia, Germany and USA.

Things are looking bright, to the Sun!

That's not a specific error, you need to look further up in the trace to find the real error.  As the other response said, if you need support you will find more help on Discord.  It will be another missing dependency, almost certainly.

> sudo apt-get install libqt5svg5-dev -y

As I said you must have all the dependencies required, this can vary from platform to platform.

> git clone https://github.com/Pink2Dev/Pink2

Then make sure you have the dependencies and compile it locally.

Done.

There are several repos, did you use https://github.com/Pink2Dev/Pink2?

When you say you launched it, you mean you compiled it?

What exactly doesn't work, the compile, or the wallet?

I have Pinkcoin on various SBCs, what error are you getting?

It can vary.  We the community cant tell you exactly, in the old scheme it was paid every six months, but the Foundation are trying to do it more regularly.  Not much activity on Bitcointalk nowdays, you are more likely to get help on the general contacts https://solarcoin.org/contact/

I think you need to quantify what the "huge problems" are with the "product": are you saying there is a fundamental problem with electricity?

In fact that has been worked on by several community members including myself, my contribution here https://www.youtube.com/watch?v=AhpkXsFDTQE.  However a non-deterministic input like energy readings needs a trusted oracle (incredibly hard to actually achieve).

Now consider a little product like the https://www.zymbit.com/ that allows you to make a Raspberry Pi into a trusted platform with decentralized private/public key security, and effectively tamper proof in deployment.

Of course there is no guarantee the Foundation would grant SLR based on this tech, its a community project, but at least we try to make a real difference.

Project is far from over because one centralized entity chose not to use it anymore.  It used to be crypto people didnt care what centralized entities thought or did, decentralization was what mattered; now its all just about fiat gainz, how sad.

When the coin is in the hands of millions of people, we will see if exchanges are interested then.

No, on average you have the same chance to stake whether all your SLR is in one address or if it is split over many.  There is a minimum amount of SLR that is valid for staking TBH I never looked for what it is, but it is less than 1 SLR, so assuming you have at least 1 SLR on each address it doesnt matter.

Proof of Stake works by saying your chance of staking increases by the number of coins you have, so if you have 1000 and I have 10, you are 100 times as likley to stake in a given time period as me.  Now consider if your 1000 are on one addres, and I really have 100 addresses with 10 coins on each one, each of my addresses on its own has 1/100th of your staking potential, but I multiply that by 100 addreses and it is equal to yours.

a) So you did in fact make a real valid block, but later it was discarded, so it still shows in your wallet history, but its not in the "real" chain so it wont show as a part of your wallet total balance.

b) The transaction is not in the block-chain that we all agreed was the "real" one, the explorer only shows you the valid chain, it doesnt show you transactions/blocks that were rejected.  That is why you didnt lose any interest.

d) I dont properly remember now, but I think after a while it may vanish from your wallet history.  In any case, its not going to effect your wallet balance.

c) So let me preface by explaining what listening is.  When you start your wallet it sends connection requests to upto 8 peers (addnodes), those peers have to be setup to allow (listen to) inbound connections from other computers.  So with your 8 connections you are sending requests out, but you are not allowing any to come in, if no-one allows incoming, then the network would not exist.  Allowing outside connections onto your network from the internet, does of course carry some slight risk, in my view extremely low risk (I operate a listening node, I feel its safe), but you should make your own descision.

So due dilligence warnings aside, depending how your network is setup there are a couple of things you may need to do, the easy way and the harder way:
The easy way:
If your router supports UPnP and has it enabled, simply go to your SolarCoin Wallet > Settings > Options > Network tab and check the "Map Port using UPnP" box and Apply.  Probably worth restarting, you might not instantly get more than 8 connections, but if its working, within an hour you should start to see more than 8 connections.

The hard way:
If you dont use UPnP for security reasons, then you must go to your router and port forward TCP port 18188 from the internet to the machine that you run your SolarCoin wallet on.  I cant tell you exactly how to do that as every router is different, but you should be able to google port forwarding for your make/model.  I never encountered a firewall problem on Windows, but you may need to allow inbound connections from anywhere to local port 18188 on your actual PC firewall if that still isnt working.

Aside from just getting more connections, you can actually see if you have inbound connections by going to Help > Console > Console tab and type "getpeerinfo", it will give you a list of IP addresses and there is an "inbound" : true if you are getting inbound connections.

1 - So imagine there are hundreds of people all running wallets trying to make the next block in the blockchain, its a competitive process and the exact time when a new block will occur is unknown.  Lets say you and I make a block at almost exactly the same time, I send my block "A" to my network peers, you send your block "B" to your network peers.  Somehow we all as a network have to agree on which block A or B is the real block and which is the one we will all discard - if you talk to blockchain people this is the "consensus mechanism" they refer to; how to reach consesnsus between anonymous peers with no leader to make descisions?  The descision is made by whichever block gets the next block made on it first, if A gets block A+1 before B gets a new block, A is the victor and your B block is discarded; the idea here is that on average the more peers receive a block and work on it, the more consensus it has - if my block reached 100 people and your block reached only 50 people, mine is twice as likley to make a new block as yours.
2 - Yes its normal, as I said its a natural part of the consensus mechanism that allow blockchains to operate with no central control.
3 - As I said, it happens regularly, its just a part of the uncoordinated nature of block-chain.
4 - When your block B was discarded, its as if it never existed, so all the interest you were owed in that block, is still owed, plus the additional interest since then; you didnt lose anything.
5 - Addnodes just help you get connections to other peers so that has had no impact on this.  The speed of your up (outbound) internet connection and the total number of connections you have might have a slight impact.  If you only have 8 connections, set your node up for listening, it might help a tiny bit.

P.S. Welcome to SolarCoin!

Does your transfer hash show in the block explorer, if no thats down to the pool, if yes then make sure you have the latest version 2.3.0.0 and are fully synced and not on a fork

Are you on a fork?  Make sure you have the latest v2.3.0.0 and are properly in sync

This can happen if you are out of sync, check if you have all the blocks against the block explorer https://chainz.cryptoid.info/slr/
You may also see that if your wallet is locked, make sure you are unlocked for staking

Hi everyone, I have created some Tor hidden services for those that have fullnodes and want to run anonymously, or for those in locations with blocking/firewalls.

addnode=mm33yxydm4z4jxzy.onion
addnode=kq7dbof2pj5cpevu4mkknpc6zd6qnjkn3og3olebxyfmw6wkvdg4adad.onion

My services talk to clearnet too (Im not doing this for my own anonymity), this is a service to the growing community.  Im not certain these work yet, I didnt seem to find any other .onion nodes, so if someone would like to try and set this up, here are a few resources:

Install Tor (not the browser)  https://2019.www.torproject.org/docs/debian.html.en

Configure Tor (Method 2 works, NOT Method 1) https://en.bitcoin.it/wiki/Setting_up_a_Tor_hidden_service
just remember to change port 8333 (BTC) with port 9982 (MANNA)

From my manna.conf:

listen=1
proxy=127.0.0.1:9050
externalip=mm33yxydm4z4jxzy.onion
discover=1

The onion=127.0.0.1:9050 and onlynet=onion options dont work in version 0.8.3.0.
Also you cant specify a v3 (the long one) .onion address as externalip=

Hi everyone, I have created some Tor hidden services for those that want to run anonymously, or for those in locations with blocking/firewalls.

addnode=yzyot5tgwcpiy5cw.onion
addnode=ajm3fnha2pr7bfhe3xyfo3ocq6jpzftnc6lx4snoavradwhhrilb23ad.onion

My services talk to clearnet too (Im not doing this for my own anonymity), this is a service to the growing community.  Im not certain these work yet, I didnt seem to find any other .onion nodes, so if someone would like to try and set this up, here are a few resources:

Install Tor (not the browser)  https://2019.www.torproject.org/docs/debian.html.en

Configure Tor (Method 2 works, NOT Method 1) https://en.bitcoin.it/wiki/Setting_up_a_Tor_hidden_service
just remember to change port 8333 (BTC) with port 18188 (SLR)

From my solarcoin.conf:

listen=1
proxy=127.0.0.1:9050
externalip=yzyot5tgwcpiy5cw.onion
discover=1

The onion=127.0.0.1:9050 and onlynet=onion options dont work in version 2.1.8.
Also you cant specify a v3 (the long one) .onion address as externalip=