I messed around with the reddit again today and I think it looks a lot better:
https://www.reddit.com/r/SpreadcoinOfficial/
Topic: [ANN] SpreadCoin | Decentralize Everything (decentralized blockexplorer coming) - page 153. (Read 790391 times)
March 13, 2016, 05:15:15 PM
March 13, 2016, 01:54:52 PM
I wish I knew more about code. It would be great to pitch in. Unfortunately, I only know introductory Python/C++ though :/
Maybe we can help Georgem in other ways!
I for one will be posting motivational videos and memes!
https://www.youtube.com/watch?v=rCZ3SN65kIs
Some inspiration! hahahah
March 13, 2016, 01:14:29 PM
Would you be interested in a testnet version where several of us could help in beta testing?
Well ofcourse, I'm just very occupied with my dayjob at the moment, that's what keeps creating the delays ...
Everybody here is waiting for the testnet version!
... tomorrow I have a deadline, but after that I've earned myself a few free days that belong to spreadcoin only!
Then I'll be like:
and
and finally
Stay tuned, like those energized eguitars!
I wish I knew more about code. It would be great to pitch in. Unfortunately, I only know introductory Python/C++ though :/
March 13, 2016, 09:09:11 AM
Would you be interested in a testnet version where several of us could help in beta testing?
Well ofcourse, I'm just very occupied with my dayjob at the moment, that's what keeps creating the delays ...
Everybody here is waiting for the testnet version!
... tomorrow I have a deadline, but after that I've earned myself a few free days that belong to spreadcoin only!
Then I'll be like:
and
and finally
Stay tuned, like those energized eguitars!
March 13, 2016, 04:42:37 AM
it would be cool to integrate a decentralized exchange in the wallet
March 13, 2016, 04:18:51 AM
Georgem,
Upon a node being kicked from the network due to not meeting the criteria of a productive node, will the network automatically recognize the next node "in line" with the next highest collateral? Meaning, will there be a queue of nodes bidding to get on the SN network (if for instance someone couldn't or didn't want to buy more SPR to get on the network - they merely keep their node with less than sufficient collateral running on a vps waiting for a spot to open)?
Upon a node being kicked from the network due to not meeting the criteria of a productive node, will the network automatically recognize the next node "in line" with the next highest collateral? Meaning, will there be a queue of nodes bidding to get on the SN network (if for instance someone couldn't or didn't want to buy more SPR to get on the network - they merely keep their node with less than sufficient collateral running on a vps waiting for a spot to open)?
The way I focus on implementing it is not by kicking nodes from the network.
What will happen is that your "bad" node will be left out of the payment-cycle and receive no reward, but your node doesn't stop doing it's (although crappy) job.
Ofcourse it is also possible that your node is misbehaving so badly that other servicenodes have put it on a temporary blacklist, then your node is like a mental patient talking to itself.
But there is no "shutting down" mechanism involved at all.
Furthermore, the network knows at all times the amounts of collateral that any servicenode is currently willing to invest.
Those are locked SPR amounts, visible in the blockchain.
i.e. Say a node gets kicked for being a crappy node, and I have a node on a VPS with the collateral of say 995 (the highest of any other sitting on a VPS), would my node be immediately inaugurated into the service network, or would I have to do something to make it a SN after recognizing there was a spot open?
Forgive me if you have addressed this somewhere. I didn't see it in your original update - only that one could *take* a seat. Not *receive* a seat after waiting.
Forgive me if you have addressed this somewhere. I didn't see it in your original update - only that one could *take* a seat. Not *receive* a seat after waiting.
Yes, that's what I'm trying to achieve, a more or less automatic re-entrance.
If your node was already running, but couldn't occupy a seat because all seats were taken, then the moment the situation changes, you'll immediately re-enter the game.
In this regard... seats don't really exist, you never occupy anything. it's rather a continuum that is constantly recalculated to find out if you are eligible for a reward.
And this continuum (the spread) can be visualized in the form of seats. This visualization is for us humans, not for the network.
Well there is more to the story, because the scoring mechanism has some say too, and it is quite possible that you..
a) have a running servicenode
b) are eligible to receive a reward
but
c) your scoring is so bad that your reward is nullified.
I am doing experiments with letting your servicenode be prepared so that it can automatically react to a constantly changing situation.
If you look at this screenshot under "Auto collateral tasks"...
... this will be a mechanism you can setup to let your servicenode automatically do all kinds of things so it can quickly react when the "collateral market" changes.
For example you can say here:
If your current COLLATERAL falls lower than the MEAN of all other collaterals in the network, then go ahead and ADD enough SPR so that your COLLATERAL is again atleast as large as the MEAN.
There will be more such trigger points you can define in an IFTTT (if this then that) fashion.
Would you be interested in a testnet version where several of us could help in beta testing?
March 13, 2016, 03:12:58 AM
Yes, that's what I'm trying to achieve, a more or less automatic re-entrance.
...
If you look at this screenshot under "Auto collateral tasks"...
... this will be a mechanism you can setup to let your servicenode automatically do all kinds of things so it can quickly react when the "collateral market" changes.
For example you can say here:
If your current COLLATERAL falls lower than the MEAN of all other collaterals in the network, then go ahead and ADD enough SPR so that your COLLATERAL is again atleast as large as the MEAN.
There will be more such trigger points you can define in an IFTTT (if this then that) fashion.
This is a great explanation. It definitely cleared things up and I'm even more excited than I was - it's nice to be able to tangibly imagine how we will actually be able to run our service nodes!
I really like that you are attempting to make it user friendly. It seems as though your approach will limit frustrations with maintaining Service Nodes, which I'm sure is your goal. Being able to "fire and forget" will be nice for a lot of people. I am so excited to see this in action. I second minerpage!!
I am doing experiments with letting your servicenode be prepared so that it can automatically react to a constantly changing situation.
Sounds like testing the finishing touches to me!!!!!
March 12, 2016, 05:46:14 PM
March 12, 2016, 04:14:26 PM
Georgem,
Upon a node being kicked from the network due to not meeting the criteria of a productive node, will the network automatically recognize the next node "in line" with the next highest collateral? Meaning, will there be a queue of nodes bidding to get on the SN network (if for instance someone couldn't or didn't want to buy more SPR to get on the network - they merely keep their node with less than sufficient collateral running on a vps waiting for a spot to open)?
Upon a node being kicked from the network due to not meeting the criteria of a productive node, will the network automatically recognize the next node "in line" with the next highest collateral? Meaning, will there be a queue of nodes bidding to get on the SN network (if for instance someone couldn't or didn't want to buy more SPR to get on the network - they merely keep their node with less than sufficient collateral running on a vps waiting for a spot to open)?
The way I focus on implementing it is not by kicking nodes from the network.
What will happen is that your "bad" node will be left out of the payment-cycle and receive no reward, but your node doesn't stop doing it's (although crappy) job.
Ofcourse it is also possible that your node is misbehaving so badly that other servicenodes have put it on a temporary blacklist, then your node is like a mental patient talking to itself.
But there is no "shutting down" mechanism involved at all.
Furthermore, the network knows at all times the amounts of collateral that any servicenode is currently willing to invest.
Those are locked SPR amounts, visible in the blockchain.
i.e. Say a node gets kicked for being a crappy node, and I have a node on a VPS with the collateral of say 995 (the highest of any other sitting on a VPS), would my node be immediately inaugurated into the service network, or would I have to do something to make it a SN after recognizing there was a spot open?
Forgive me if you have addressed this somewhere. I didn't see it in your original update - only that one could *take* a seat. Not *receive* a seat after waiting.
Forgive me if you have addressed this somewhere. I didn't see it in your original update - only that one could *take* a seat. Not *receive* a seat after waiting.
Yes, that's what I'm trying to achieve, a more or less automatic re-entrance.
If your node was already running, but couldn't occupy a seat because all seats were taken, then the moment the situation changes, you'll immediately re-enter the game.
In this regard... seats don't really exist, you never occupy anything. it's rather a continuum that is constantly recalculated to find out if you are eligible for a reward.
And this continuum (the spread) can be visualized in the form of seats. This visualization is for us humans, not for the network.
Well there is more to the story, because the scoring mechanism has some say too, and it is quite possible that you..
a) have a running servicenode
b) are eligible to receive a reward
but
c) your scoring is so bad that your reward is nullified.
I am doing experiments with letting your servicenode be prepared so that it can automatically react to a constantly changing situation.
If you look at this screenshot under "Auto collateral tasks"...
... this will be a mechanism you can setup to let your servicenode automatically do all kinds of things so it can quickly react when the "collateral market" changes.
For example you can say here:
If your current COLLATERAL falls lower than the MEAN of all other collaterals in the network, then go ahead and ADD enough SPR so that your COLLATERAL is again atleast as large as the MEAN.
There will be more such trigger points you can define in an IFTTT (if this then that) fashion.
March 12, 2016, 02:50:05 PM
How realistic would it be to host a website on these nodes? Bypassing a single dedicated server?
hm, not sure I understand your question.
Do you want to host websites on the same server that runs a node?
No problem, I am doing that all the time. It would be a waste of space/cpu to host a dedicated server "just" to run a node.
Or, do you mean that you want a node to give back html-sites (answer http requests like a webserver) when a certain IP/port is opened in a browser?
Kinda like giving back a "webstats site" with servicenode information to the public? And it would be the servicenode itself that "serves" those html pages to the clients?
That's probably not what you are asking about, but those are all interesting questions that we will explore...
Actually you hit it on the head. I am wondering if it would be possible to take the current Spreadcoin website (Spreadcointalk) and place it on the service nodes so that they answer http requests like a webserver. If i'm not mistaken this would entirely decentralize the website. Making it impossible for a country of origin to stake claim to it. Websites like Pirate Bay or other torrent websites would no longer be "owned" by anyone. You could create websites that no longer hide on the deep web. And, once the service node network grew enough I would imagine we would maintain the network in every country. Meaning that anyone could access a website through their closest servicenode. This means that governments around the world could no longer block websites for any reason. The ability to create a websites "For the People, By the People". No more government restrictions on anything placed online. If Spreadcoin was the first it would be one of the most revolutionary things to hit the internet.
That is an interesting thought. Separately, perhaps you have spreadcoin assist networks made up of a variety of different types of nodes - i.e. Tor network, OpenBazaar, and a few other coins off the top of my head - like Shadowcash - at least they are developing a marketplace of sorts. I don't think there would be much financial incentive, but if you liked any of those projects you could help support them with service nodes - at least the coins... idk about the other nodes.
But yea, building an entire decentralized internet of sorts would be pretty damn cool - with the entire infrastructure being Spreadcoin nodes.
We could even develop a tertiary Spreadcoin network if we wanted more nodes???
March 12, 2016, 02:39:08 PM
Georgem,
Upon a node being kicked from the network due to not meeting the criteria of a productive node, will the network automatically recognize the next node "in line" with the next highest collateral? Meaning, will there be a queue of nodes bidding to get on the SN network (if for instance someone couldn't or didn't want to buy more SPR to get on the network - they merely keep their node with less than sufficient collateral running on a vps waiting for a spot to open)?
i.e. Say a node gets kicked for being a crappy node, and I have a node on a VPS with the collateral of say 995 (the highest of any other sitting on a VPS), would my node be immediately inaugurated into the service network, or would I have to do something to make it a SN after recognizing there was a spot open?
Forgive me if you have addressed this somewhere. I didn't see it in your original update - only that one could *take* a seat. Not *receive* a seat after waiting.
Upon a node being kicked from the network due to not meeting the criteria of a productive node, will the network automatically recognize the next node "in line" with the next highest collateral? Meaning, will there be a queue of nodes bidding to get on the SN network (if for instance someone couldn't or didn't want to buy more SPR to get on the network - they merely keep their node with less than sufficient collateral running on a vps waiting for a spot to open)?
i.e. Say a node gets kicked for being a crappy node, and I have a node on a VPS with the collateral of say 995 (the highest of any other sitting on a VPS), would my node be immediately inaugurated into the service network, or would I have to do something to make it a SN after recognizing there was a spot open?
Forgive me if you have addressed this somewhere. I didn't see it in your original update - only that one could *take* a seat. Not *receive* a seat after waiting.
March 12, 2016, 12:15:22 PM
How realistic would it be to host a website on these nodes? Bypassing a single dedicated server?
hm, not sure I understand your question.
Do you want to host websites on the same server that runs a node?
No problem, I am doing that all the time. It would be a waste of space/cpu to host a dedicated server "just" to run a node.
Or, do you mean that you want a node to give back html-sites (answer http requests like a webserver) when a certain IP/port is opened in a browser?
Kinda like giving back a "webstats site" with servicenode information to the public? And it would be the servicenode itself that "serves" those html pages to the clients?
That's probably not what you are asking about, but those are all interesting questions that we will explore...
Actually you hit it on the head. I am wondering if it would be possible to take the current Spreadcoin website (Spreadcointalk) and place it on the service nodes so that they answer http requests like a webserver. If i'm not mistaken this would entirely decentralize the website. Making it impossible for a country of origin to stake claim to it. Websites like Pirate Bay or other torrent websites would no longer be "owned" by anyone. You could create websites that no longer hide on the deep web. And, once the service node network grew enough I would imagine we would maintain the network in every country. Meaning that anyone could access a website through their closest servicenode. This means that governments around the world could no longer block websites for any reason. The ability to create a websites "For the People, By the People". No more government restrictions on anything placed online. If Spreadcoin was the first it would be one of the most revolutionary things to hit the internet.
March 12, 2016, 09:38:33 AM
How realistic would it be to host a website on these nodes? Bypassing a single dedicated server?
hm, not sure I understand your question.
Do you want to host websites on the same server that runs a node?
No problem, I am doing that all the time. It would be a waste of space/cpu to host a dedicated server "just" to run a node.
Or, do you mean that you want a node to give back html-sites (answer http requests like a webserver) when a certain IP/port is opened in a browser?
Kinda like giving back a "webstats site" with servicenode information to the public? And it would be the servicenode itself that "serves" those html pages to the clients?
That's probably not what you are asking about, but those are all interesting questions that we will explore...
March 12, 2016, 07:26:52 AM
How realistic would it be to host a website on these nodes? Bypassing a single dedicated server?
Very realistic.
The long-long term goal is to host a Coinbase type account. You would need to host web pages to do that.
There could be a BIP out of this.
I've always found it stupid that you can make a Bitcoin transaction for less than $0.10 but that transaction could be sitting around unspent for years, and years and years.
The real cost of one Bitcoin transaction that sits around for a year could be $10, or $100 [each year]
Visa handles billions of transactions, but they are all throughput. No mempool.
The Bitcoin blockchain is being treated like a bank account, so we'll design some banking features into the Spreadcoin second layer. As we can do this with fresh eyes, we can design out some of the crap of banking and keep the good stuff.
March 12, 2016, 05:38:59 AM
How realistic would it be to host a website on these nodes? Bypassing a single dedicated server?
Very realistic.
The long-long term goal is to host a Coinbase type account. You would need to host web pages to do that.
March 12, 2016, 04:10:29 AM
How realistic would it be to host a website on these nodes? Bypassing a single dedicated server?
March 12, 2016, 12:56:28 AM
300 SPR for the person that guesses when Georgem goes Legendary (nearest will do).
April 4th 2016.
Ima guess May 5th
March 12, 2016, 12:49:18 AM
Coins, did you happen to get any word from poloniex? Who was in charge of that last time? Is this something we still want to pursue?
A couple more questions:
How do you end up getting mobile location data through full bitcoin node? Do they receive that information from SPV wallets?
Do you have any good links for me to look over on this stuff? I want to get up to speed here.
A couple more questions:
How do you end up getting mobile location data through full bitcoin node? Do they receive that information from SPV wallets?
Do you have any good links for me to look over on this stuff? I want to get up to speed here.
SPVs are dumb clients, pretty much.
They need someone to spoon feed them data. If you have a second layer with thousands of full bitcoin nodes, you'll end up serving most of the SPVs, especially if you are hosting your full node in a professional facility with fast hardware and fast bandwidth. You'll be able to learn a lot by providing good coverage and good infrastructure for SPVs to connect to.
Slide 9, you'll find a link to Andreas's bitcoin book
https://docs.google.com/presentation/d/1qyExM5c1Ws7eUEj3J_gJ76zFe2WQaLdqJHMbJIJ_jng/edit?usp=sharing
I will look into that! Thanks!
March 12, 2016, 12:46:33 AM
Thank you!
I am going to play around with the layout a bit more. As I said, I don't know CSS, but maybe I can find some interesting downloads until we perhaps get someone on the team who can make it more aesthetically pleasing.
I am going to play around with the layout a bit more. As I said, I don't know CSS, but maybe I can find some interesting downloads until we perhaps get someone on the team who can make it more aesthetically pleasing.
Check it out!
https://www.reddit.com/r/SpreadcoinOfficial/
I used someone else's code for the theme, but am making some minor adjustments myself (read as: copy & paste reddit developer!). Working on integrating spreadcoin's color scheme now. Who knows... maybe I'll be alright at CSS after all this...
March 11, 2016, 08:47:06 PM
Coins, did you happen to get any word from poloniex? Who was in charge of that last time? Is this something we still want to pursue?
A couple more questions:
How do you end up getting mobile location data through full bitcoin node? Do they receive that information from SPV wallets?
Do you have any good links for me to look over on this stuff? I want to get up to speed here.
A couple more questions:
How do you end up getting mobile location data through full bitcoin node? Do they receive that information from SPV wallets?
Do you have any good links for me to look over on this stuff? I want to get up to speed here.
SPVs are dumb clients, pretty much.
They need someone to spoon feed them data. If you have a second layer with thousands of full bitcoin nodes, you'll end up serving most of the SPVs, especially if you are hosting your full node in a professional facility with fast hardware and fast bandwidth. You'll be able to learn a lot by providing good coverage and good infrastructure for SPVs to connect to.
Slide 9, you'll find a link to Andreas's bitcoin book
https://docs.google.com/presentation/d/1qyExM5c1Ws7eUEj3J_gJ76zFe2WQaLdqJHMbJIJ_jng/edit?usp=sharing
Jump to: