Maybe Swongle owns the botnet.
Topic: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes) - page 648. (Read 243376 times)
February 08, 2018, 01:05:25 PM
February 08, 2018, 01:03:18 PM
i type it then have result in picture. you mean rsync or resync ? have any -option after that ?
https://www.reddit.com/r/BiblePay/comments/7nmvm8/how_to_update_clean_wallets/
Bottom half shows commands/steps to clean your wallet
but
Quote
"version": 1000808,
"protocolversion": 70716,
"walletversion": 61000,
"wallet_fullversion": "1.0.8.8",
"balance": 0.00000000,
"privatesend_balance": 0.00000000,
"retirement_balance": 0,
"blocks": 8534,
"timeoffset": 0,
"connections": 5,
"proxy": "",
"difficulty": 4467.178498806472,
"testnet": false,
"keypoololdest": 1518104077,
"keypoolsize": 1001,
"paytxfee": 0.00000000,
"relayfee": 0.00010000,
"errors": ""
"protocolversion": 70716,
"walletversion": 61000,
"wallet_fullversion": "1.0.8.8",
"balance": 0.00000000,
"privatesend_balance": 0.00000000,
"retirement_balance": 0,
"blocks": 8534,
"timeoffset": 0,
"connections": 5,
"proxy": "",
"difficulty": 4467.178498806472,
"testnet": false,
"keypoololdest": 1518104077,
"keypoolsize": 1001,
"paytxfee": 0.00000000,
"relayfee": 0.00010000,
"errors": ""
I lost all coin ?
Coins mined on a fork do not count towards your balance.
Please check your ~.biblepaycore\backups folder if you indeed lost your original wallet.
February 08, 2018, 01:02:30 PM
1.0.8.8q is out there for windows, its not a prod upgrade, but I thought I would mention it since I accidentally let that "POL Weight" slip in that inblue, discord and 616 noticed last week (into prod) and this is now fixed:
The release this morning had some type of problem with the "accountability" image. Its fixed in 1.0.8.8q.
As a summary:
- No more POL weight in 1088q, DC is disabled in Prod
- Allows testnet user to start/stop a 1088- Sanctuary
- In Testnet: Provides the new 'exec getboincinfo' command with the new more complete magnitude value
- In Testnet: Allows Rosetta re-association
The release this morning had some type of problem with the "accountability" image. Its fixed in 1.0.8.8q.
As a summary:
- No more POL weight in 1088q, DC is disabled in Prod
- Allows testnet user to start/stop a 1088- Sanctuary
- In Testnet: Provides the new 'exec getboincinfo' command with the new more complete magnitude value
- In Testnet: Allows Rosetta re-association
February 08, 2018, 12:59:12 PM
i type it then have result in picture. you mean rsync or resync ? have any -option after that ?
https://www.reddit.com/r/BiblePay/comments/7nmvm8/how_to_update_clean_wallets/
Bottom half shows commands/steps to clean your wallet
but
Quote
"version": 1000808,
"protocolversion": 70716,
"walletversion": 61000,
"wallet_fullversion": "1.0.8.8",
"balance": 0.00000000,
"privatesend_balance": 0.00000000,
"retirement_balance": 0,
"blocks": 8534,
"timeoffset": 0,
"connections": 5,
"proxy": "",
"difficulty": 4467.178498806472,
"testnet": false,
"keypoololdest": 1518104077,
"keypoolsize": 1001,
"paytxfee": 0.00000000,
"relayfee": 0.00010000,
"errors": ""
"protocolversion": 70716,
"walletversion": 61000,
"wallet_fullversion": "1.0.8.8",
"balance": 0.00000000,
"privatesend_balance": 0.00000000,
"retirement_balance": 0,
"blocks": 8534,
"timeoffset": 0,
"connections": 5,
"proxy": "",
"difficulty": 4467.178498806472,
"testnet": false,
"keypoololdest": 1518104077,
"keypoolsize": 1001,
"paytxfee": 0.00000000,
"relayfee": 0.00010000,
"errors": ""
I lost all coin ?
February 08, 2018, 12:49:17 PM
i type it then have result in picture. you mean rsync or resync ? have any -option after that ?
https://www.reddit.com/r/BiblePay/comments/7nmvm8/how_to_update_clean_wallets/
Bottom half shows commands/steps to clean your wallet
February 08, 2018, 12:43:55 PM
Hi Rob, everyone and christant,
My wallet today can not turn on, with effort help from bbp community on discord who help me to find solution to fix but nothing work (Tks you so much Tmike)
https://imgur.com/YTeXl6k
Please help me to recover my wallet.
Seem like newbie can not post a picture.Sorry
My wallet today can not turn on, with effort help from bbp community on discord who help me to find solution to fix but nothing work (Tks you so much Tmike)
https://imgur.com/YTeXl6k
Please help me to recover my wallet.
Seem like newbie can not post a picture.Sorry
Ensure you have 1.0.8.6+ first (most likely the problem), then rm chainstate -r, and rm blocks -r and resync.
Dear Rob
https://imgur.com/FG9NamT
i type it then have result in picture. you mean rsync or resync ? have any -option after that ?
Thanks.
February 08, 2018, 12:30:45 PM
Hi Rob, everyone and christant,
My wallet today can not turn on, with effort help from bbp community on discord who help me to find solution to fix but nothing work (Tks you so much Tmike)
https://imgur.com/YTeXl6k
Please help me to recover my wallet.
Seem like newbie can not post a picture.Sorry
My wallet today can not turn on, with effort help from bbp community on discord who help me to find solution to fix but nothing work (Tks you so much Tmike)
https://imgur.com/YTeXl6k
Please help me to recover my wallet.
Seem like newbie can not post a picture.Sorry
Ensure you have 1.0.8.6+ first (most likely the problem), then rm chainstate -r, and rm blocks -r and resync.
February 08, 2018, 12:19:18 PM
Please see inline:
FUD by Swongle:
- Bible pays can be used to set up Master Nodes effectifely granting voting rights to those who are able to mint coins.
-> The sanctuaries job is to vote on the authenticity of the distributed credit file(s) as a whole. Since the algorithm is ranked, no particular sanctuary could predetermine when it will be their job to perform the function. The chances as pointed out by Duffield for such attack are lower than .10%, because of the number required for a net yes. So the statement is misleading. The correct statement is "We as a network will trust 10% of the sanctuaries to verify the Distributed Computing files for authenticity". If one rogue actor fraudulently creates a file, 99% of the other sancs will vote it down. So in reality we are only going to assimilate the official file, created by the distributed boinc network. The users will be paid their fare share of cancer research based on this assimilated and voted file.
- Making BOINC a central authority for deciding who gets Bible pay subsidies making them a single point of failure and allowing for fraudulant non-verifiable transactions.
-> There will be no central point of failure in biblepay, because if the BOINC network or Rosetta goes down, Biblepay stays up while the heat-miners, the PoBH miners continue block checking. Next, there is a distributed web farm on the server side of Rosetta verifying the Cancer Solutions. (Not a single point of failure). We do not directly ask for your solution credit from those servers. Those servers have a backlog, and a proven 99.9% uptime, and simply approve work units in a queue. We actually ask the distributed network for the entire file so that those machines could be down and we could be UP on the DC side. The only way DC goes down is if 10% of our sanctuaries ALL fail to download the distributed computing credits, consecutively, once every 15 minutes for 23 hours. Then DC goes down. AND I Do Not have to send a Spork In to disable PODC. Its automatic. (More FUD).
- Depending on the developer to spork whenever something goes wrong makes the sole developer a single point of failure.
-> Actually for issues like complete network failure of Instant Send, Soft Forking, and Enabling the switch for PODC and Disabling PODC, I do have the right to Execute a SPORK, but that is because I am the sole github contributor. I started the github, and there is a certain inherent level of trust you must assume, that I will not insert a Virus into github, or do anything nefarious that will kill Biblepay. You have my word that I will never do anything to hurt biblepay, and this is an issue in all baby cryptos that have just been birthed: How many years did it take Sunny King to turn control over to "the community", or BlackCoin? A few years. I am in the process of interviewing devs right now. I promise that eventually, we will have 7 devs with spork signing rights (the good ones who know what they are doing).
- Giving the power to mint money to BOINC, an organisation which did not ask nor accepted this responsibility will automatically a target for hackers looking to earn crypto currency by hacking.
-> We will write reports in the RPC that we can export to the web to show the relationship between biblepay user, RAC, Magnitude, and ensure everything rolls up. There is a difference between blockchain coinbase minting and Distributed-Computing Rewards. The difference here is in the name of Cancer Research, I believe it is a Huge advantage for biblepay to reward DC users with blockchain rewards, in the form of our daily superblock. This question was posed as Risky and is also FUD. The answer paints a clearer picture of the intent of Biblepay.
- Reducing block chain securing mining subsidies by 90% will effecitvely make the resources required to launch a 51% attack 90% less.
-> Pure FUD. We use DGW, it was carefully designed to not include POL into the mix while reducing the reward, you cannot buy your way into a 51% attack in this scenario. You would certainly drive up the diff within 5 blocks of high hashpower, and you cannot take over biblepay with POW mining with our low nonce rule. It is a true and certain statement, that One Nefarious high hash individual who just hit us with 4 consecutive blocks, would NOT be able to solve block 5 because we only allow 200 hashes per second in the solution. Take a look at the code before making this heinously arrogant statement, and misleading everyone. The 51% attack liklihood on the POW side is more like : 80%, 33%, 11%, 1%, 0.10, .05, .001% for an individual with 75,000 PCs left dormant. Our diff would be : .50, 150, 2500, 8500, 65535, 256000, 1 million. They would not reach level 5 without failing in the attack.
Lastly I make a very important argument that Currently our Botnet has 93% of our hashpower, and they are in a stronger position of controlling our chains future now than they would be with a consensus change. The current "status quo" is what is broken - and its a carryover of the problem existing in bitcoin supermajority pools and ASICs. DC is part of the solution.
FUD by Swongle:
- Bible pays can be used to set up Master Nodes effectifely granting voting rights to those who are able to mint coins.
-> The sanctuaries job is to vote on the authenticity of the distributed credit file(s) as a whole. Since the algorithm is ranked, no particular sanctuary could predetermine when it will be their job to perform the function. The chances as pointed out by Duffield for such attack are lower than .10%, because of the number required for a net yes. So the statement is misleading. The correct statement is "We as a network will trust 10% of the sanctuaries to verify the Distributed Computing files for authenticity". If one rogue actor fraudulently creates a file, 99% of the other sancs will vote it down. So in reality we are only going to assimilate the official file, created by the distributed boinc network. The users will be paid their fare share of cancer research based on this assimilated and voted file.
- Making BOINC a central authority for deciding who gets Bible pay subsidies making them a single point of failure and allowing for fraudulant non-verifiable transactions.
-> There will be no central point of failure in biblepay, because if the BOINC network or Rosetta goes down, Biblepay stays up while the heat-miners, the PoBH miners continue block checking. Next, there is a distributed web farm on the server side of Rosetta verifying the Cancer Solutions. (Not a single point of failure). We do not directly ask for your solution credit from those servers. Those servers have a backlog, and a proven 99.9% uptime, and simply approve work units in a queue. We actually ask the distributed network for the entire file so that those machines could be down and we could be UP on the DC side. The only way DC goes down is if 10% of our sanctuaries ALL fail to download the distributed computing credits, consecutively, once every 15 minutes for 23 hours. Then DC goes down. AND I Do Not have to send a Spork In to disable PODC. Its automatic. (More FUD).
- Depending on the developer to spork whenever something goes wrong makes the sole developer a single point of failure.
-> Actually for issues like complete network failure of Instant Send, Soft Forking, and Enabling the switch for PODC and Disabling PODC, I do have the right to Execute a SPORK, but that is because I am the sole github contributor. I started the github, and there is a certain inherent level of trust you must assume, that I will not insert a Virus into github, or do anything nefarious that will kill Biblepay. You have my word that I will never do anything to hurt biblepay, and this is an issue in all baby cryptos that have just been birthed: How many years did it take Sunny King to turn control over to "the community", or BlackCoin? A few years. I am in the process of interviewing devs right now. I promise that eventually, we will have 7 devs with spork signing rights (the good ones who know what they are doing).
- Giving the power to mint money to BOINC, an organisation which did not ask nor accepted this responsibility will automatically a target for hackers looking to earn crypto currency by hacking.
-> We will write reports in the RPC that we can export to the web to show the relationship between biblepay user, RAC, Magnitude, and ensure everything rolls up. There is a difference between blockchain coinbase minting and Distributed-Computing Rewards. The difference here is in the name of Cancer Research, I believe it is a Huge advantage for biblepay to reward DC users with blockchain rewards, in the form of our daily superblock. This question was posed as Risky and is also FUD. The answer paints a clearer picture of the intent of Biblepay.
- Reducing block chain securing mining subsidies by 90% will effecitvely make the resources required to launch a 51% attack 90% less.
-> Pure FUD. We use DGW, it was carefully designed to not include POL into the mix while reducing the reward, you cannot buy your way into a 51% attack in this scenario. You would certainly drive up the diff within 5 blocks of high hashpower, and you cannot take over biblepay with POW mining with our low nonce rule. It is a true and certain statement, that One Nefarious high hash individual who just hit us with 4 consecutive blocks, would NOT be able to solve block 5 because we only allow 200 hashes per second in the solution. Take a look at the code before making this heinously arrogant statement, and misleading everyone. The 51% attack liklihood on the POW side is more like : 80%, 33%, 11%, 1%, 0.10, .05, .001% for an individual with 75,000 PCs left dormant. Our diff would be : .50, 150, 2500, 8500, 65535, 256000, 1 million. They would not reach level 5 without failing in the attack.
Lastly I make a very important argument that Currently our Botnet has 93% of our hashpower, and they are in a stronger position of controlling our chains future now than they would be with a consensus change. The current "status quo" is what is broken - and its a carryover of the problem existing in bitcoin supermajority pools and ASICs. DC is part of the solution.
February 08, 2018, 12:12:46 PM
Hi Rob, everyone and christant,
My wallet today can not turn on, with effort help from bbp community on discord who help me to find solution to fix but nothing work (Tks you so much Tmike)
https://imgur.com/YTeXl6k
Please help me to recover my wallet.
Seem like newbie can not post a picture.Sorry
The wallet.dat backed up
My wallet today can not turn on, with effort help from bbp community on discord who help me to find solution to fix but nothing work (Tks you so much Tmike)
https://imgur.com/YTeXl6k
Please help me to recover my wallet.
Seem like newbie can not post a picture.Sorry
The wallet.dat backed up
February 08, 2018, 11:56:46 AM
...
I believe Proof of Distributed Computing to be harmful to the Bible Pay network, making it 10x easier to launch a 51% attack and centralising the ability to mint new Bible Pays to the BOINC network.
This is harmful because of the following reasons:
- Bible pays can be used to set up Master Nodes effectifely granting voting rights to those who are able to mint coins.
- Making BOINC a central authority for deciding who gets Bible pay subsidies making them a single point of failure and allowing for fraudulant non-verifiable transactions.
- Depending on the developer to spork whenever something goes wrong makes the sole developer a single point of failure.
- Giving the power to mint money to BOINC, an organisation which did not ask nor accepted this responsibility will automatically a target for hackers looking to earn crypto currency by hacking.
- Reducing block chain securing mining subsidies by 90% will effecitvely make the resources required to launch a 51% attack 90% less.
I believe Proof of Distributed Computing to be harmful to the Bible Pay network, making it 10x easier to launch a 51% attack and centralising the ability to mint new Bible Pays to the BOINC network.
This is harmful because of the following reasons:
- Bible pays can be used to set up Master Nodes effectifely granting voting rights to those who are able to mint coins.
- Making BOINC a central authority for deciding who gets Bible pay subsidies making them a single point of failure and allowing for fraudulant non-verifiable transactions.
- Depending on the developer to spork whenever something goes wrong makes the sole developer a single point of failure.
- Giving the power to mint money to BOINC, an organisation which did not ask nor accepted this responsibility will automatically a target for hackers looking to earn crypto currency by hacking.
- Reducing block chain securing mining subsidies by 90% will effecitvely make the resources required to launch a 51% attack 90% less.
Alright, here are the FUD rules, for the FUD smell test.
I have a responsibility to give our investors the truth so they can make investing decisions on the truth.
If your post contains a biased LIE, its going to be deleted.
Here is an example of an unbiased statement:
"I believe the Biblepay Proof-of-dc implementation will centralize blockchain consensus by relying on a central authority - boinc- Rob how is that not true?"
vs.
FUD:
We are Making BOINC the central authority for deciding who gets Biblepay subsidies.
The second is a LIE because we are not.
One more requirement: Before posting about BOINC or Rosetta, please study the implementation. You cant be taken seriously if you do not understand what you are talking about.
I will respond to this FUD separately.
February 08, 2018, 11:16:36 AM
Swongel:
Please wait before posting FUD. I will edit this message with FUD rules in a minute.
Please wait before posting FUD. I will edit this message with FUD rules in a minute.
It's not FUD, these are real issues about the development which should be addressed.
Please stop removing my posts and rather reply to the critique so that people may decide for themselves if the critique is valid.
February 08, 2018, 11:11:14 AM
...
I believe Proof of Distributed Computing to be harmful to the Bible Pay network, making it 10x easier to launch a 51% attack and centralising the ability to mint new Bible Pays to the BOINC network.
This is harmful because of the following reasons:
- Bible pays can be used to set up Master Nodes effectifely granting voting rights to those who are able to mint coins.
- Making BOINC a central authority for deciding who gets Bible pay subsidies making them a single point of failure and allowing for fraudulant non-verifiable transactions.
- Depending on the developer to spork whenever something goes wrong makes the sole developer a single point of failure.
- Giving the power to mint money to BOINC, an organisation which did not ask nor accepted this responsibility will automatically a target for hackers looking to earn crypto currency by hacking.
- Reducing block chain securing mining subsidies by 90% will effecitvely make the resources required to launch a 51% attack 90% less.
I believe Proof of Distributed Computing to be harmful to the Bible Pay network, making it 10x easier to launch a 51% attack and centralising the ability to mint new Bible Pays to the BOINC network.
This is harmful because of the following reasons:
- Bible pays can be used to set up Master Nodes effectifely granting voting rights to those who are able to mint coins.
- Making BOINC a central authority for deciding who gets Bible pay subsidies making them a single point of failure and allowing for fraudulant non-verifiable transactions.
- Depending on the developer to spork whenever something goes wrong makes the sole developer a single point of failure.
- Giving the power to mint money to BOINC, an organisation which did not ask nor accepted this responsibility will automatically a target for hackers looking to earn crypto currency by hacking.
- Reducing block chain securing mining subsidies by 90% will effecitvely make the resources required to launch a 51% attack 90% less.
As far as I understood, PoDC subsidy calculation is uncoupled to transaction verification, which will continue using PoBh. I agree on the single-developer risk.
In any case, we can peek at how other PoDC projects like GridCoin have tackled these challenges.
February 08, 2018, 11:09:31 AM
Swongel:
Please wait before posting FUD. I will edit this message with FUD rules in a minute.
Please wait before posting FUD. I will edit this message with FUD rules in a minute.
February 08, 2018, 10:03:59 AM
by me, cancer mining looks like a fake...no tutorial,no proofs,no in road map,no answers....more ppl on dicords starts talkin about it 
And your comments looks like FUD! Please do a little bit of homework first. There is a site called Google, ever heard of it? You can search and find much about the Rosetta project, e.g. recent publications in New York Times, Science, Nature.
Unfortunately the Rosetta@Home project is far from perfect. While Slovak's point is poorly made, the truth is that it is also known as a massive heat-generating project. It has come under fire whether or not the benefit outweighs the risk. Again it is not proper to ask "Who has a problem with mining for cancer?" I would think no one does. However, the Rosetta@Home project can be linked to energy consequences that despite its good intention is also an environmental offender. I am not sure why BiblePay is uniting with them in an all-or-nothing fashion. Presumably it is being designed as a "shield" to the botnet mining currently underway on the BBP network.
Securing the BBP network and its integrity should be the priority, not "mining for cancer" using an environmentally dubious project like Rosetta@home
I cannot think of a University that has more anti-Christian values than the Cal Berkeley system. BiblePay and Berkeley.edu are not just antithetical but it is a questionable decision to partner with them, in light of everything else Berkeley stands for (no matter how well-intentioned cancer mining can be portrayed as)
I am at a loss here but I hope these thoughts do not get shoved under the "FUD" carpet because these are actual legitimate issues to be weighed in the discussion.
Furthermore, I have personally spent time living in Berkeley, CA so I am not speaking from anything other than first-hand experience. There are spiritual implications of donating BBP cpu cycles to the project. We don't know to what extent those cycles are being used for cancer detection & modeling, vs. how much of that research is ported to Eugenics and epigenetic research. It is a very uncomfortable partnership the more you peel back the layers.
SVK NOKO total useless
ROBERTOS: why we are still on 150 blocks daily?... your information is still contradictory
SPARSK1956: this rosettaproject.com? < 200 visitors per day
that web is dead ofc@bible_pay any information about cancer mining? in roadmap missing all infos
Its not in the roadmap til its voted in. The Sanctuary vote will be in before tomorrow evening.
Roadmap changes after community approves Distributed Computing.
If we go with DC, DC will be in roadmap for June and Stratis in roadmap for September.
February 08, 2018, 09:31:35 AM
what about bittrex, binance or at least cyryptopia Is it really hard to join that exchanges. What are they needed to add any coin?
Is it really hard to join that exchanges. What are they needed to add any coin?Today morning binance has suspended all deposit and withdrawal operations. Now the status is: Due to an unforeseen slowdown in the speed of our data sync, we now estimate for all trading activity to resume at 2018/02/09 4AM (UTC).
Something is going wrong there :-) :-)
UPDATE :
很抱歉！服务器出错了。
We’re sorry, but something went wrong.
Bye Bye Binance :-)
February 08, 2018, 09:25:03 AM
what about bittrex, binance or at least cyryptopia Is it really hard to join that exchanges. What are they needed to add any coin?
Is it really hard to join that exchanges. What are they needed to add any coin?Today morning binance has suspended all deposit and withdrawal operations. Now the status is: Due to an unforeseen slowdown in the speed of our data sync, we now estimate for all trading activity to resume at 2018/02/09 4AM (UTC).
Something is going wrong there :-) :-)
February 08, 2018, 08:59:51 AM
by me, cancer mining looks like a fake...no tutorial,no proofs,no in road map,no answers....more ppl on dicords starts talkin about it
And your comments looks like FUD! Please do a little bit of homework first. There is a site called Google, ever heard of it? You can search and find much about the Rosetta project, e.g. recent publications in New York Times, Science, Nature.
Unfortunately the Rosetta@Home project is far from perfect. While Slovak's point is poorly made, the truth is that it is also known as a massive heat-generating project. It has come under fire whether or not the benefit outweighs the risk. Again it is not proper to ask "Who has a problem with mining for cancer?" I would think no one does. However, the Rosetta@Home project can be linked to energy consequences that despite its good intention is also an environmental offender. I am not sure why BiblePay is uniting with them in an all-or-nothing fashion. Presumably it is being designed as a "shield" to the botnet mining currently underway on the BBP network.
Securing the BBP network and its integrity should be the priority, not "mining for cancer" using an environmentally dubious project like Rosetta@home
I cannot think of a University that has more anti-Christian values than the Cal Berkeley system. BiblePay and Berkeley.edu are not just antithetical but it is a questionable decision to partner with them, in light of everything else Berkeley stands for (no matter how well-intentioned cancer mining can be portrayed as)
I am at a loss here but I hope these thoughts do not get shoved under the "FUD" carpet because these are actual legitimate issues to be weighed in the discussion.
Furthermore, I have personally spent time living in Berkeley, CA so I am not speaking from anything other than first-hand experience. There are spiritual implications of donating BBP cpu cycles to the project. We don't know to what extent those cycles are being used for cancer detection & modeling, vs. how much of that research is ported to Eugenics and epigenetic research. It is a very uncomfortable partnership the more you peel back the layers.
SVK NOKO total useless
ROBERTOS: why we are still on 150 blocks daily?... your information is still contradictory
SPARSK1956: this rosettaproject.com? < 200 visitors per day
that web is dead ofc@bible_pay any information about cancer mining? in roadmap missing all infos
February 08, 2018, 08:30:42 AM
This message is primarily for Testnet:
Those testing proof-of-dc in testnet have been waiting for the windows build.
Windows 1.0.8.8 has been released. This build not for Prod, so please dont upgrade in Prod unless you have a Sanctuary on 1088.
If you have already upgraded a sanctuary to 1.0.8.8, you will then need the windows 1.0.8.8 to start it (hence the reason I mention it), as 1.0.8.8 has an incremented Sanctuary protocol version (70716).
Those testing proof-of-dc in testnet have been waiting for the windows build.
Windows 1.0.8.8 has been released. This build not for Prod, so please dont upgrade in Prod unless you have a Sanctuary on 1088.
If you have already upgraded a sanctuary to 1.0.8.8, you will then need the windows 1.0.8.8 to start it (hence the reason I mention it), as 1.0.8.8 has an incremented Sanctuary protocol version (70716).
February 08, 2018, 08:27:35 AM
what about bittrex, binance or at least cyryptopia Is it really hard to join that exchanges. What are they needed to add any coin?
$50,000 down plus 350 coin waiting list, plus no return emails even if you have the $50k Is it really hard to join that exchanges. What are they needed to add any coin? February 08, 2018, 08:09:51 AM
what about bittrex, binance or at least cyryptopia Is it really hard to join that exchanges. What are they needed to add any coin?
I think 10-15btc listing fee Is it really hard to join that exchanges. What are they needed to add any coin?Jump to: