[ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency

[BrainShutdown]

CAUTION!  THE FOLLOWING USERS ARE KNOWN TROLLS AND FUDSTERS.

ADAM WHITE
ICEBREAKER
ARIELBIT

Please do not feed or reply to!

Slipped page bump 

[1714881684]

1714881684

[1714881684]

1714881684

[1714881684]

1714881684

[toknormal]

Sorry for that, some times trolls choose to post supporting a different project to produce exactly that effect on others.

r.o.t.f.w.l. !

Mustn't do our hectoring windbags the indignity of miss-appropriating their interests  

[wpalczynski]

Of course those are paid trolls.  Why else would they be hanging for so long?  XMR must be a dying coin, apparently operated by kids.  Who the hell would want to invest in that community after seeing this constant avalanche of crap?

  

I don't think they represent XMR as much as they think they do. There are good people in every community is just the trolls that need to be ignored. I don't believe community members from any community want to be represented by trolls. They are a problem for both the community they claim to be representing and the community they troll.

I think trolls are a side effect of anonymous forums, it just dehumanizes people and brings the worst out of some.  I am sure if we were at some sort of real life event/debate, they would be ashamed to behave like that.

Well, dev from xmr have come to troll here a week or two ago, xmr is already on my blacklist

Quote please?

[qwizzie]

CAUTION!  THE FOLLOWING USERS ARE KNOWN TROLLS AND FUDSTERS.

ADAM WHITE
ICEBREAKER
ARIELBIT

Please do not feed or reply to!

Slipped page bump  

Can I get into the list pls, I think I have earned that, after all you need to be literally like your nick to still support this scam:

nope, you need to make a lot more fud posts to get on that list. Oh and we give more points to creative fud posts by the way, use that to your advantage.

[BigTimeProducer]

Of course those are paid trolls.  Why else would they be hanging for so long?  XMR must be a dying coin, apparently operated by kids.  Who the hell would want to invest in that community after seeing this constant avalanche of crap?

  

I don't think they represent XMR as much as they think they do. There are good people in every community is just the trolls that need to be ignored. I don't believe community members from any community want to be represented by trolls. They are a problem for both the community they claim to be representing and the community they troll.

I think trolls are a side effect of anonymous forums, it just dehumanizes people and brings the worst out of some.  I am sure if we were at some sort of real life event/debate, they would be ashamed to behave like that.

Well, dev from xmr have come to troll here a week or two ago, xmr is already on my blacklist

Quote please?

I admit my mistake, he was misquoted in the other DASH thread, not the DRK thread.

[BrainShutdown]

I love your nick  

nope, you need to make a lot more fud posts to get on that list. Oh and we give more points to creative posts by the way, use that to your advantage.

 

If you try hard enough you will make it!

[alex-ru]

https://letstalkbitcoin.com/blog/post/lets-talk-bitcoin-196-distortions-towards-privacy-or-many-hands-makes-light-work

[wpalczynski]

So the lead dev has a private key which lets him control all the MasterNodes? Why does he need to control all MasterNodes? In the future, will he be in control or is this just temporary and if so how long will this continue?

No, he does not. There is a private key for engaging the spork but that's it. This allows us to prevent forks for the time being while bugs are getting troubleshooted on mainnet when new features get rolled out.

If he chose to for whatever reason, could he crash/stop/impede the DRK network with this "masterkey"?  What exactly does this key allow him to do?

He is refering to the Spork, is a message that is send out to the network so that you can activate, deactivate a hard fork. It works similar to the way alerts work in BTC. Is probably one of the coolest things on DASH/DRK and he chooses to troll about it. It poses absolutely no risk and gives no power, it just allows a mature network to innovate and do hard fork after hard fork in the name of progress, like DRK has been doing to implement its features.

From the OP:

Multi-Phased Fork Implementation (aka the “Spork”)
In response to unforeseen issues with the rollout of RC3, the Darkcoin development team created a mechanism by which updated code is released to the network, but not immediately made active (or “enforced”).  Communication is sent out to users informing them of the change and the need for them to update their clients.  Those who update their clients run the new code, but in the event of errors occurring with that new code, the client’s blocks are not rejected by the network and unintended forks are avoided. Data about the error can then be collected and forwarded to the development team.
Once the development team is satisfied with the new code’s stability in the mainnet environment - and once acceptable network consensus is attained - enforcement of the updated code can be activated remotely.  Should problems arise, the code can be deactivated in the same manner, without the need for a network-wide rollback or client update.
This innovation allows for far smoother transitions than in the traditional hard fork paradigm, as well as the collection of test data in the live network environment.
We set out with the intention of calling this method of updating the “Soft Fork”, but the Darkcoin community quickly dubbed it the “Spork” and the name seems to have stuck.

Thanks for the answer.  

With other coins, should the community (read miners and masternodes) choose not to accept whatever new aspect the developer(s) are trying to implement in the existing coins code they could simply not upgrade to the latest version put out by developers and run the current version of the code as they have done since the last update they agreed to apply.  This would allow the network to continue to operate normally although perhaps temporarily without the support of the developers since they could not reach a consensus with the miners.

I am understanding from your answer, if I understood correctly, that this Spork would in no way provide the DRK dev with the ability of subverting the miners ability to operate as is without accepting and applying the new code?

Basically if the DRK dev tried to implement a code change which was greatly unpopular among the community, miners, etc. this Sprok could not be used in any way to force everyone (miners, masternodes)  to accept these unpopular changes?

Thanks in advance.

[iCEBREAKER]

https://letstalkbitcoin.com/blog/post/lets-talk-bitcoin-196-distortions-towards-privacy-or-many-hands-makes-light-work

DigitalTrash

Unproven Privacy.  Autocratic.  Dev Killswitch.  Premined.  Trusted 2nd Tier.  Proof of Stake.  Completely Shitty.

[the-baker]

So the lead dev has a private key which lets him control all the MasterNodes? Why does he need to control all MasterNodes? In the future, will he be in control or is this just temporary and if so how long will this continue?

No, he does not. There is a private key for engaging the spork but that's it. This allows us to prevent forks for the time being while bugs are getting troubleshooted on mainnet when new features get rolled out.

If he chose to for whatever reason, could he crash/stop/impede the DRK network with this "masterkey"?  What exactly does this key allow him to do?

He is refering to the Spork, is a message that is send out to the network so that you can activate, deactivate a hard fork. It works similar to the way alerts work in BTC. Is probably one of the coolest things on DASH/DRK and he chooses to troll about it. It poses absolutely no risk and gives no power, it just allows a mature network to innovate and do hard fork after hard fork in the name of progress, like DRK has been doing to implement its features.

From the OP:

Multi-Phased Fork Implementation (aka the “Spork”)
In response to unforeseen issues with the rollout of RC3, the Darkcoin development team created a mechanism by which updated code is released to the network, but not immediately made active (or “enforced”).  Communication is sent out to users informing them of the change and the need for them to update their clients.  Those who update their clients run the new code, but in the event of errors occurring with that new code, the client’s blocks are not rejected by the network and unintended forks are avoided. Data about the error can then be collected and forwarded to the development team.
Once the development team is satisfied with the new code’s stability in the mainnet environment - and once acceptable network consensus is attained - enforcement of the updated code can be activated remotely.  Should problems arise, the code can be deactivated in the same manner, without the need for a network-wide rollback or client update.
This innovation allows for far smoother transitions than in the traditional hard fork paradigm, as well as the collection of test data in the live network environment.
We set out with the intention of calling this method of updating the “Soft Fork”, but the Darkcoin community quickly dubbed it the “Spork” and the name seems to have stuck.

Thanks for the answer.  

With other coins, should the community (read miners and masternodes) choose not to accept whatever new aspect the developer(s) are trying to implement in the existing coins code they could simply not upgrade to the latest version put out by developers and run the current version of the code as they have done since the last update they agreed to apply.  This would allow the network to continue to operate normally although perhaps temporarily without the support of the developers since they could not reach a consensus with the miners.

I am understanding from your answer, if I understood correctly, that this Spork would in no way provide the DRK dev with the ability of subverting the miners ability to operate as is without accepting and applying the new code?

Basically if the DRK dev tried to implement a code change which was greatly unpopular among the community, miners, etc. this Sprok could not be used in any way to force everyone (miners, masternodes)  to accept these unpopular changes?

Thanks in advance.

Well, the same logic applies as in the Bitcoin example you made: If the miners don't like the new version, they won't install it, and thus there will be nothing for the key to activate

[wpalczynski]

So the lead dev has a private key which lets him control all the MasterNodes? Why does he need to control all MasterNodes? In the future, will he be in control or is this just temporary and if so how long will this continue?

No, he does not. There is a private key for engaging the spork but that's it. This allows us to prevent forks for the time being while bugs are getting troubleshooted on mainnet when new features get rolled out.

If he chose to for whatever reason, could he crash/stop/impede the DRK network with this "masterkey"?  What exactly does this key allow him to do?

He is refering to the Spork, is a message that is send out to the network so that you can activate, deactivate a hard fork. It works similar to the way alerts work in BTC. Is probably one of the coolest things on DASH/DRK and he chooses to troll about it. It poses absolutely no risk and gives no power, it just allows a mature network to innovate and do hard fork after hard fork in the name of progress, like DRK has been doing to implement its features.

From the OP:

Multi-Phased Fork Implementation (aka the “Spork”)
In response to unforeseen issues with the rollout of RC3, the Darkcoin development team created a mechanism by which updated code is released to the network, but not immediately made active (or “enforced”).  Communication is sent out to users informing them of the change and the need for them to update their clients.  Those who update their clients run the new code, but in the event of errors occurring with that new code, the client’s blocks are not rejected by the network and unintended forks are avoided. Data about the error can then be collected and forwarded to the development team.
Once the development team is satisfied with the new code’s stability in the mainnet environment - and once acceptable network consensus is attained - enforcement of the updated code can be activated remotely.  Should problems arise, the code can be deactivated in the same manner, without the need for a network-wide rollback or client update.
This innovation allows for far smoother transitions than in the traditional hard fork paradigm, as well as the collection of test data in the live network environment.
We set out with the intention of calling this method of updating the “Soft Fork”, but the Darkcoin community quickly dubbed it the “Spork” and the name seems to have stuck.

Thanks for the answer.  

With other coins, should the community (read miners and masternodes) choose not to accept whatever new aspect the developer(s) are trying to implement in the existing coins code they could simply not upgrade to the latest version put out by developers and run the current version of the code as they have done since the last update they agreed to apply.  This would allow the network to continue to operate normally although perhaps temporarily without the support of the developers since they could not reach a consensus with the miners.

I am understanding from your answer, if I understood correctly, that this Spork would in no way provide the DRK dev with the ability of subverting the miners ability to operate as is without accepting and applying the new code?

Basically if the DRK dev tried to implement a code change which was greatly unpopular among the community, miners, etc. this Sprok could not be used in any way to force everyone (miners, masternodes)  to accept these unpopular changes?

Thanks in advance.

Well, the same logic applies as in the Bitcoin example you made: If the miners don't like the new version, they won't install it, and thus there will be nothing for the key to activate

But this private key/backdoor/troubleshooting tool is already imbeded in the DRK architecture.  I'm trying to understand this.  Could you please provide a binary answer to my last question?

[crowning]

Or if you're too lazy to compute this yourself, see last line here: http://178.254.18.153/~pub/Darkcoin/masternode_payments_stats.html

On the bottom is says: Payment fees are NOT included!
Average payment intervals computed for MY Masternodes only.

If I may, what are were your startup costs and how much do you cost to your nodes per month?

I'm not 100% sure if I understand your question correctly...startup costs for one Masternode are (obviously) 1000 DRK, and that costs are of course dependent on the exchange rate when they were bought.
I have some which were mined, but those were probably even more expensive due to electricity costs.

The payments fees (which are included in most transactions) are negligible, they are usually in the sub 0.001 DRK range and wouldn't make much of a difference.

The running costs per Masternode are about $3.5 per month.

[Otoh]

Current Number of Masternodes: 2,390 MN

http://178.254.18.153/~pub/Darkcoin/masternode_payments_stats.html

A new ATH

2,387 MN - count lagging a little on:

http://178.254.18.153/~pub/masternode_count.png

[larry12]

I'm a real darkcoin supporter but changing the name to Dash is a really stupid move......

[Minotaur26]

So the lead dev has a private key which lets him control all the MasterNodes? Why does he need to control all MasterNodes? In the future, will he be in control or is this just temporary and if so how long will this continue?

No, he does not. There is a private key for engaging the spork but that's it. This allows us to prevent forks for the time being while bugs are getting troubleshooted on mainnet when new features get rolled out.

If he chose to for whatever reason, could he crash/stop/impede the DRK network with this "masterkey"?  What exactly does this key allow him to do?

He is refering to the Spork, is a message that is send out to the network so that you can activate, deactivate a hard fork. It works similar to the way alerts work in BTC. Is probably one of the coolest things on DASH/DRK and he chooses to troll about it. It poses absolutely no risk and gives no power, it just allows a mature network to innovate and do hard fork after hard fork in the name of progress, like DRK has been doing to implement its features.

From the OP:

Multi-Phased Fork Implementation (aka the “Spork”)
In response to unforeseen issues with the rollout of RC3, the Darkcoin development team created a mechanism by which updated code is released to the network, but not immediately made active (or “enforced”).  Communication is sent out to users informing them of the change and the need for them to update their clients.  Those who update their clients run the new code, but in the event of errors occurring with that new code, the client’s blocks are not rejected by the network and unintended forks are avoided. Data about the error can then be collected and forwarded to the development team.
Once the development team is satisfied with the new code’s stability in the mainnet environment - and once acceptable network consensus is attained - enforcement of the updated code can be activated remotely.  Should problems arise, the code can be deactivated in the same manner, without the need for a network-wide rollback or client update.
This innovation allows for far smoother transitions than in the traditional hard fork paradigm, as well as the collection of test data in the live network environment.
We set out with the intention of calling this method of updating the “Soft Fork”, but the Darkcoin community quickly dubbed it the “Spork” and the name seems to have stuck.

Thanks for the answer.  

With other coins, should the community (read miners and masternodes) choose not to accept whatever new aspect the developer(s) are trying to implement in the existing coins code they could simply not upgrade to the latest version put out by developers and run the current version of the code as they have done since the last update they agreed to apply.  This would allow the network to continue to operate normally although perhaps temporarily without the support of the developers since they could not reach a consensus with the miners.

I am understanding from your answer, if I understood correctly, that this Spork would in no way provide the DRK dev with the ability of subverting the miners ability to operate as is without accepting and applying the new code?

Basically if the DRK dev tried to implement a code change which was greatly unpopular among the community, miners, etc. this Sprok could not be used in any way to force everyone (miners, masternodes)  to accept these unpopular changes?

Thanks in advance.

It is exactly the same here, I guess is a little confusing if it is the first time you hear about it.   The network needs consensus to have a chance of the fork being successful. So even with a Spork you need to wait for at least 80 - 90 % of the network to update, if they don't do this then the fork (hard or soft) has no chance of being successful. So if the community as a whole decides not to update then there is nothing the developers can do about it just like with any other coin.

The thing is hard forks are dangerous, so if after 90% of the community updates and we turn on the fork, things start going badly you can send the spork message out to deactivate the new code that is producing the problems and stabilize the network without having to release yet a new version to roll back the changes and wait for everyone to update. Which when a network gets large enough is just impossible thus why many older coins avoid hard forks.  I hope is more clear now.

[wpalczynski]

So the lead dev has a private key which lets him control all the MasterNodes? Why does he need to control all MasterNodes? In the future, will he be in control or is this just temporary and if so how long will this continue?

No, he does not. There is a private key for engaging the spork but that's it. This allows us to prevent forks for the time being while bugs are getting troubleshooted on mainnet when new features get rolled out.

If he chose to for whatever reason, could he crash/stop/impede the DRK network with this "masterkey"?  What exactly does this key allow him to do?

He is refering to the Spork, is a message that is send out to the network so that you can activate, deactivate a hard fork. It works similar to the way alerts work in BTC. Is probably one of the coolest things on DASH/DRK and he chooses to troll about it. It poses absolutely no risk and gives no power, it just allows a mature network to innovate and do hard fork after hard fork in the name of progress, like DRK has been doing to implement its features.

From the OP:

Multi-Phased Fork Implementation (aka the “Spork”)
In response to unforeseen issues with the rollout of RC3, the Darkcoin development team created a mechanism by which updated code is released to the network, but not immediately made active (or “enforced”).  Communication is sent out to users informing them of the change and the need for them to update their clients.  Those who update their clients run the new code, but in the event of errors occurring with that new code, the client’s blocks are not rejected by the network and unintended forks are avoided. Data about the error can then be collected and forwarded to the development team.
Once the development team is satisfied with the new code’s stability in the mainnet environment - and once acceptable network consensus is attained - enforcement of the updated code can be activated remotely.  Should problems arise, the code can be deactivated in the same manner, without the need for a network-wide rollback or client update.
This innovation allows for far smoother transitions than in the traditional hard fork paradigm, as well as the collection of test data in the live network environment.
We set out with the intention of calling this method of updating the “Soft Fork”, but the Darkcoin community quickly dubbed it the “Spork” and the name seems to have stuck.

Thanks for the answer.  

With other coins, should the community (read miners and masternodes) choose not to accept whatever new aspect the developer(s) are trying to implement in the existing coins code they could simply not upgrade to the latest version put out by developers and run the current version of the code as they have done since the last update they agreed to apply.  This would allow the network to continue to operate normally although perhaps temporarily without the support of the developers since they could not reach a consensus with the miners.

I am understanding from your answer, if I understood correctly, that this Spork would in no way provide the DRK dev with the ability of subverting the miners ability to operate as is without accepting and applying the new code?

Basically if the DRK dev tried to implement a code change which was greatly unpopular among the community, miners, etc. this Sprok could not be used in any way to force everyone (miners, masternodes)  to accept these unpopular changes?

Thanks in advance.

It is exactly the same here, I guess is a little confusing if it is the first time you hear about it.   The network needs consensus to have a chance of the fork being successful. So even with a Spork you need to wait for at least 80 - 90 % of the network to update, if they don't do this then the fork (hard or soft) has no chance of being successful. So if the community as a whole decides not to update then there is nothing the developers can do about it just like with any other coin.

The thing is hard forks are dangerous, so if after 90% of the community updates and we turn on the fork, things start going badly you can send the spork message out to deactivate the new code that is producing the problems and stabilize the network without having to release yet a new version to roll back the changes and wait for everyone to update. Which when a network gets large enough is just impossible thus why many older coins avoid hard forks.  I hope is more clear now.

Ok I think I got it now.  So the dev could not use the Spork to arbitrarily force an update but he could arbitrarily roll back the update should shit hit the fan.

[the-baker]

So the lead dev has a private key which lets him control all the MasterNodes? Why does he need to control all MasterNodes? In the future, will he be in control or is this just temporary and if so how long will this continue?

No, he does not. There is a private key for engaging the spork but that's it. This allows us to prevent forks for the time being while bugs are getting troubleshooted on mainnet when new features get rolled out.

If he chose to for whatever reason, could he crash/stop/impede the DRK network with this "masterkey"?  What exactly does this key allow him to do?

He is refering to the Spork, is a message that is send out to the network so that you can activate, deactivate a hard fork. It works similar to the way alerts work in BTC. Is probably one of the coolest things on DASH/DRK and he chooses to troll about it. It poses absolutely no risk and gives no power, it just allows a mature network to innovate and do hard fork after hard fork in the name of progress, like DRK has been doing to implement its features.

From the OP:

Multi-Phased Fork Implementation (aka the ?Spork?)
In response to unforeseen issues with the rollout of RC3, the Darkcoin development team created a mechanism by which updated code is released to the network, but not immediately made active (or ?enforced?).  Communication is sent out to users informing them of the change and the need for them to update their clients.  Those who update their clients run the new code, but in the event of errors occurring with that new code, the client?s blocks are not rejected by the network and unintended forks are avoided. Data about the error can then be collected and forwarded to the development team.
Once the development team is satisfied with the new code?s stability in the mainnet environment - and once acceptable network consensus is attained - enforcement of the updated code can be activated remotely.  Should problems arise, the code can be deactivated in the same manner, without the need for a network-wide rollback or client update.
This innovation allows for far smoother transitions than in the traditional hard fork paradigm, as well as the collection of test data in the live network environment.
We set out with the intention of calling this method of updating the ?Soft Fork?, but the Darkcoin community quickly dubbed it the ?Spork? and the name seems to have stuck.

Thanks for the answer.  

With other coins, should the community (read miners and masternodes) choose not to accept whatever new aspect the developer(s) are trying to implement in the existing coins code they could simply not upgrade to the latest version put out by developers and run the current version of the code as they have done since the last update they agreed to apply.  This would allow the network to continue to operate normally although perhaps temporarily without the support of the developers since they could not reach a consensus with the miners.

I am understanding from your answer, if I understood correctly, that this Spork would in no way provide the DRK dev with the ability of subverting the miners ability to operate as is without accepting and applying the new code?

Basically if the DRK dev tried to implement a code change which was greatly unpopular among the community, miners, etc. this Sprok could not be used in any way to force everyone (miners, masternodes)  to accept these unpopular changes?

Thanks in advance.

Well, the same logic applies as in the Bitcoin example you made: If the miners don't like the new version, they won't install it, and thus there will be nothing for the key to activate

But this key is already impeded in the DRK architecture.  I'm trying to understand this.  Could you please provide a binary answer to my last question?

Binary answer: No, there is no way

It works like this: New version is released, which contains a dormant feature. Once enough people have installed the new version, the key is used to activate the feature. If something goes wrong, the key can be used to deactivate it again.

There is no remote code injection or anything of the nature going on, so if miners don't install a new version with the new feature, there's nothing Evan can do about it.

[eduffield]

So the lead dev has a private key which lets him control all the MasterNodes? Why does he need to control all MasterNodes? In the future, will he be in control or is this just temporary and if so how long will this continue?

No, he does not. There is a private key for engaging the spork but that's it. This allows us to prevent forks for the time being while bugs are getting troubleshooted on mainnet when new features get rolled out.

If he chose to for whatever reason, could he crash/stop/impede the DRK network with this "masterkey"?  What exactly does this key allow him to do?

He is refering to the Spork, is a message that is send out to the network so that you can activate, deactivate a hard fork. It works similar to the way alerts work in BTC. Is probably one of the coolest things on DASH/DRK and he chooses to troll about it. It poses absolutely no risk and gives no power, it just allows a mature network to innovate and do hard fork after hard fork in the name of progress, like DRK has been doing to implement its features.

From the OP:

Multi-Phased Fork Implementation (aka the “Spork”)
In response to unforeseen issues with the rollout of RC3, the Darkcoin development team created a mechanism by which updated code is released to the network, but not immediately made active (or “enforced”).  Communication is sent out to users informing them of the change and the need for them to update their clients.  Those who update their clients run the new code, but in the event of errors occurring with that new code, the client’s blocks are not rejected by the network and unintended forks are avoided. Data about the error can then be collected and forwarded to the development team.
Once the development team is satisfied with the new code’s stability in the mainnet environment - and once acceptable network consensus is attained - enforcement of the updated code can be activated remotely.  Should problems arise, the code can be deactivated in the same manner, without the need for a network-wide rollback or client update.
This innovation allows for far smoother transitions than in the traditional hard fork paradigm, as well as the collection of test data in the live network environment.
We set out with the intention of calling this method of updating the “Soft Fork”, but the Darkcoin community quickly dubbed it the “Spork” and the name seems to have stuck.

Thanks for the answer.  

With other coins, should the community (read miners and masternodes) choose not to accept whatever new aspect the developer(s) are trying to implement in the existing coins code they could simply not upgrade to the latest version put out by developers and run the current version of the code as they have done since the last update they agreed to apply.  This would allow the network to continue to operate normally although perhaps temporarily without the support of the developers since they could not reach a consensus with the miners.

I am understanding from your answer, if I understood correctly, that this Spork would in no way provide the DRK dev with the ability of subverting the miners ability to operate as is without accepting and applying the new code?

Basically if the DRK dev tried to implement a code change which was greatly unpopular among the community, miners, etc. this Sprok could not be used in any way to force everyone (miners, masternodes)  to accept these unpopular changes?

Thanks in advance.

Well, the same logic applies as in the Bitcoin example you made: If the miners don't like the new version, they won't install it, and thus there will be nothing for the key to activate

But this private key/backdoor/troubleshooting tool is already imbeded in the DRK architecture.  I'm trying to understand this.  Could you please provide a binary answer to my last question?

It's exactly the same as the Bitcoin network, it's like the developers adding a hardfork, the miners must support it. The only difference is it can be reversed back to the prior way the code was before the hardfork without an update.

There's no magic key that allows debugging or anything like you're saying.

[busterzzz]

https://letstalkbitcoin.com/blog/post/lets-talk-bitcoin-196-distortions-towards-privacy-or-many-hands-makes-light-work

I'm Listening to this now and it's great. This clarifies a lot of the technical jargon that a lot of us don't understand, it's all normal speak!

[PoS]

CAUTION!  THE FOLLOWING USERS ARE KNOWN TROLLS AND FUDSTERS.

ADAM WHITE
ICEBREAKER
ARIELBIT

Please do not feed or reply to!

You are a disappointment, have i slipped so far in rank that i am not worth mentioning.
Get your act together scammer.

DigitalTrash

Unproven Privacy.  Autocratic.  Dev Killswitch.  Premined.  Trusted 2nd Tier.  Proof of Stake.  Completely Shitty.