Hackers Start Using Ngrok Reverse Proxy Technique in ...
Hackers Start Using Ngrok Reverse Proxy Technique in ...
Bitcoin Mining Pool Bitcoin.com
Stantinko botnet caught using YouTube to mine Monero ...
This Bitcoin Botnet is Vying to Be Future of Secure IoT ...
Was ist ein Botnet? Die Definition und 5 Hauptarten
The LIES of Chris Rabalais and AllSportsMarket
https://i.imgur.com/oucavJo.jpg A) This is a work in progress. (trying to make this neater and add things that people post) These things have been collected from forums / posts in various places (official forums, reddit groups etc)..and are here to be sifted through and examined to see which are true and which are not. Anyone is welcome to comment both agreement or disagreement. B) ANY CORRECTIONS please send a message and reference the lie number *** I want to remove false info ASAP*** Or make a post in this thread. If there is anything in this list that shouldn't be here, it will be removed. C) If you'd like me to add a lie, PLEASE make a post in this thread! Include something like ADD THIS LIE and make a short description d) ASM /Allsportsmarket / the company means any or all of the proxies and identities of CWH , NSEI, Sportshares.net etc ------------------------------------ A while back, Chris claimed people on reddit were "lying" and that he would respond "point by point" to any "lies" told by redditors. I have begun to compile a list of all of Chris' lies from various sources.
To Chris Rabalais / Allsportsmarket.com : You are more than welcome to respond "point by point". Please include a lie number...and respond and explain how it isn't a lie....
Lies of Chris Rabalais
1)This is and was an investment He has always claimed this was an investment, and still does. He claims you will get a return...yet from the other side of his mouth, he makes sure to mention that this is a "donation." Not one of us would have donated to him without the chance of a return / profit. None of us. This was a donation....to Chris Rabalais...NOT an investment. Still to this day when askign for money he makes suree to put in DONATION but then out of the other side of his mouth he claims you will get a return..or profit..and says you are an investor / insider etc.....This is NOT an investment. This is a DONATION to a very inefficient "charity" claiming you will someday see a "return" on it. 2) Investors into ASM would get a return on their investment -- profit from it He is still promising people a return...many people show a 'profit' on their account statement but are unable to cash out. Unable to withdraw etc...Chances are, If you have made a "profit" from this on paper, you cannot withdraw it. 3) He was in the process of registering the company shares with the SEC The SEC has stated point blank he has taken NO STEPS to register the company shares. It is in the complaint. 4) The company shares were ABOUT to be registered, and once they did...they would have even more value and we would miss out unless we bought in Not only did he say it was in process, he claimed many times they were very close to getting the shares registered and when they did, they would have more value..and investors would be sorry if we didn't jump in on this "rocketship". 5) Chris knows how to get the shares registered with the SEC or has any clue what he is doing in terms of registering the shares According to the SEC , Chris Rabalais has no idea HOW to even get the shares registered...and that is in their complaint as well. Meanwhile for years Chris was claiming he knew what do do to get the shares registered. 6) "This may be the last chance to jump on this great opportunity" How many times have we all heard this lie? This or that program is ending....you'll never get another chance at giving money to Chris Rabalais again...but then shockingly...there's another even better offer in a couple days/weeks... 7) If you don't give X amount of money right now , the lights might suddenly go out on ASM..and you'll lose your "investment" Another lie they tell is that if you don't give money, they will go out of business and you will "lose your investment". Bullcrap , they're not shutting off their free money machine....until someone MAKES them. Oh and you have no investment. Two lies for the price of one. 8) This is not a ponzi scheme Chris has addressed the ponzi issue only VERY briefly over the years. He recently claimed it isn't a ponzi because the "last guy in can still make money" but that would require MONEY coming in from others...so he gets around the truth by omitting that its not the "guy" its the "last money in " which is nearly the same thing... the people who put their money in last will lose....that is a ponzi. The Judge in the Seth Leon case said so...and I hope another judge says so soon. (See here: https://www.reddit.com/ASMEunfiltered/comments/e61nya/summary_of_the_seth_leon_case_with_update/ ) 9) The sports shares have value Chris claims they have value because they area "claim on future dividends" which is a lie. That is not any definition of real or intrinsic value...and even if it was (it isn't, IMO) the claim on future dividends is a LIE because every penny of that future dividend money relies on new money coming into the market...which is a ponzi...which is valueless 10) You would be able to cash out (sell your holdings, pay off your bonus margin and keep your profits) He changed the rules when the market started imploding. For years he promised investors they could sell their shares, pay off our margin and take our profits. No one would've bought in if they thought they could never do this. Even after he froze people's ability to cash out...he kept claiming that we would be able to soon...and urged people to buy more margin because all of the profits would be able to be kept. 11) Chris would stop selling margin Recently, there was a conference call where key members of the team called for an end to the margin offers..NOT because they were a scam (they are) but because it was no longer possible to ignore the implosion of the pilot market and the collapse was being blamed on margin....Chris agreed to end margin and made announcements to this end. In a short time, he realized that promising people money on margin profit was his only revenue...so he HAD to start selling margin again...He knows it is worthless, promised to stop selling it....and lied. 12) Different celebrities, politicians, business people were about to come on board and help us XFL (paul has contacts with them!!), PHIL COLLINS' WIFE!, Mark Cuban, Jon Bon FUCKING Jovi, Roger Goddell, Snoop Dogg, Brian Austin Green, Trump (speaker at zero club), Labron James, meetings with MLB people, Jack MA / Alibaba.......god knows how many other names this guy drops as potential people who are going to help or who we are 'reaching out' to in order to get them to help us. (help me add to this list) 13) ASM would have a "liquidity event" and be able to make money off of our company shares There was going to be some liquidity event where we could sell our company shares to other investors...of course it never happened. 14) The new york times ad was going to be about ASM or helping our investment There was NO MENTION of ASM or AllSportsMarket in the new york times ad and it didn't do a single thing to help ASM become a legitimate company. The only thing it did (from memory) was bash gambling. 15) The trips to Israel, funded by the investors, were something worthy of doing with the money... Chris bragged and posted pictures of his trips to Israel...but what did they have to do with ASM? How was spending "donations" (investments) for him to go to Israel supposed to help the company? Clearly this was a waste. 16) the Hero club events he goes to (more travel) help ASM in any way whatsoever I have never seen any evidence that spending who knows how much of the investors' money has been wasted on this,yet chris continues to act as if his membership in the Hero Club is a wise way to spend money...I have seen no evidence that the Hero club has done anything bust waste money. 17) donating to ASM is helping anyone or doing anything other than putting money in HIS pocket... Quite simply, Chris "donates" 10% of the money given him, if we are to believe that. So He has given (according to him) 150k+ to a hunger charity. They have (according to Chris) matched this 7x, so the 150k donation has turned into a millionish dollars worth of charity. Sounds good right? Well in doing so, Chris has just wasted 90% of the money. Instead of 150k, had we all simply given our 1.5 million to this same charity....and they matched it 7x...we would have turned our money into 10+ million dollars for charity. So essentially, even by Chris' own numbers...we have wasted 9 million dollars of potential charity....by paying Chris's rent..cars etc.. all so that he can take 90% and give 10% to charity....to me, this is wasteful and we would be better donationg directly to the 7x charity the entire 100% rather than wasting the 90%. 18) The ASM 'real market' was a real money market Chris started the real market to fool us into thinking it was actual money. He later then changed the name to "pilot market" after taking people's REAL money..so he could have the excuse "HEY this is a PILOT market!!!" when you cant withdraw...otherwise why call this a "real" market then suddenly change the name to "pilot"? 19) the ASM pilot market was going to transition with your holdings to a 'regulated' or 'exempt market' and you would be able to keep your profit from the pilot market So it has been promised to us that the pilot (which was the real market) market will transition to another market..where.....where you'll STILL be able to keep your profits...so..guys..KEEP BUYING BONUS MARGIN lol.... 20) If there is a good enough plan, Chris will happily step down in January 2020 and let someone else change the direction of the "company" Chris claims "give him till December" and if no one is happy he will step aside if that's what everyone wants...IF there is a plan he likes..LOL..we will see...but I am guessing he will not. 21) The pilot market is working He has claimed the pilot market is working and proves that ASM is functional...yet the market has collapsed and he has frozen everyone's accounts from withdrawing..or paying off margin..etc...but the real/pilot market has been a disaster. Here is him contradicting himself and admitting that the pilot market does NOT work : https://vocaroo.com/bsbcnHWDF8z . This is an admission thatthe pilot market as it is now is busted and will never work without being completely re-designed (revenue sharing etc). The worst part of this is he KNOWS the pilot market is not working yet he is still selling margin to buy stocks on this market.....that to me is criminal. How can he do this? 22) The learning market is working and proves that the math and numbers are correct and functional Claims have been made the learning market is working..LOL...anyone who has touched the learning market knows it is completely dysfunctional...and not any kind of advertisement or positive experience... 23) Bonus margin has some sort of value other than to put money in his pocket He claims bonus margin has value. It doesn't. Its worthless. If he tries to deny this..ask him why he is selling it if it has no value? Ask him how he plans on turning something with 0 value into something with value. This is the core of his scam right now..selling WORTHLESS bonus margin with no value for real money...which he donates 10% of and the rest goes to expenses...and his salary & rent etc... 24) Chris "had alper" double check the math in 2009 , and the market math is fine.. Oh god...so in one of the videos, Chris claims he had Alper check the math in 2009 and alper told him the numbers work. This is such utter horseshit, and mainly designed to deflect responsibility for the failure of the market..so he can blame it on Alper. Chris knows the math doesn't work. Alper knows the math doesn't work..and Alper & Chris know that margin is worthless...and they know the market is a failure...they have to know this... 25) special clubs like "ASM Black", "Insider programs", "Advisory Councils" etc etc are anything other than him trying to get even more money out of your pocket All of these programs are just designed to get you to give them more money..there is no real benefit to being a member in them. The insider program just basically stopped people from being able to withdraw sooner....who knows what ASM black was..and this advisory council...what was that? Give Chris 100$ to listen to more youtube rants? Ok...whatever new club or council they will come up with next is a bunch of crap designed to make you feel special as you give them your hard earned money. 26) The NDA he sent via email before spamming you with more ads is legally binding We all know the NDA he sent via e-mail was worthless..it was hilarious.....and unenforceable.... 27) They would provide investors with financial documents / audit / detailed information at the end of October 2019 Yeah so will we ever get to see the "audit" ? Doubt it...they are not transparent with any pertinent info. Who is paid what? Who holds what shares? What shares have been granted to who? What money was paid by NSEI to who , and for what? "Seal of transparency" my ass. 28) The SEC filing suit against him could be viewed as a positive in some ways I forget how he worded it but he basically claimed the SEC suit was some sort of opportunity for something positive for him. The one positive thing I can think of is it stopped him from getting more money from suckers... 29) He didn't "really" lose the case against Seth Leon He made all kinds of excuses and claims the only reason he lost against Seth Leon is because Seth Leon sent the papers to an old address....LOL (see here: https://www.reddit.com/ASMEunfiltered/comments/e61nya/summary_of_the_seth_leon_case_with_update/ ) Make NO mistake..Chris LOST the case. The court found "AMPLE EVIDENCE" of fraud by Chris Rabalais. 30) It was Trump's fault (Govt shutdown) that he didn't get paperwork done with the SEC LOL...I hope this is what he tells the Judge 31) It was Jason's fault that "a letter" wasn't sent to the SEC regarding the NRHL Blame it on a guy who doesn't work for the company any more... 32) It is alper's fault the math/numbers don't work because Chris asked alper to "check the numbers" in 2009 Blame this on Alper.....when he has known for YEARS the numbers do not work 33) there were "saboteurs" who tried to wreck the "deal" with NRHL, who came from reddit..*but luckily they saved the deal! Remember the saboteurs? remember how they "saved" the deal with the NRHL? Remember how the NRHL was going to be huge for ASM? Yeah none of these things were true....MAYBE a guy (gregson?) tried to contact the NRHL to find out if they were even real.. but NO ONE thought the NRHL was going to be a good thing..and NO ONE wanted to transition their money to a market led by roller derby..because it was and is a stupid idea. 34) There were lawyers (zero club? friends?) who were going to help with the SEC defense for free Chris had an army of lawyers, some of the best in the country and who had never lost...but yet he had to beg the court for a free lawyer because he can't get a lawyer to represent him...LOL 35) "secured by blockchain" - Chris claims this tech is in use now but what is it exactly other than bullshit? On one of his latest videos he claims the blockchain technology is protecting the ASM market right now...BS. There is no technology that I have seen. There hasn't been anything said about what this even is or does. Ace hasn't even been heard from since around August has he? They can't even get an android app...the blockchain bullshit is just more jargon and buzzwords...trying to get you to give them money...there is nothing behind this "secured by blockchain" trademark...other than words...otherwise why not explain exactly what it is, and how it works ..etc... 36) Chris is going to counter sue the SEC and prove that he is a legitimate business LOL.. with his free lawyer? 37) All cryptocurrencies are a SCAM Notice he screams and cries FRAUD at many things, but he is a fraud himself. Typical tactic...accuse others of what you are doing. Also, there is some real value in some cryptos, like bitcoin...unlike a sports share on ASM. Its called 'proof of work' ...that has real value that can even be measured..by electricity use, processing power etc...I am not arguing it has a lot of value, or even that it is as valuable as the price....but it is above zero, unlike a share in a sports team on ASM. I'm also not an expert nor to I condone investing in crypto... 38) Gambling is more of a problem than ASM / NSEI Again, he screams and cries about how dirty Gambling is...but at least legal gambling is regulated, and you have a chance to win. Unlike ASM... 39) They were working on an Android app , and needed donations for it One of the reasons I donated early on was because of seeing the IOS app, and the promises of making an android app.In fairness this might not have been a lie....but if theyre not going to make an android app , then say so. 41) They lied by omission and did not tell investors about the SEC suit until August 2019 So someone else came and announced the SEC lawsuit on the reddit forum in August 2019. There is some strong evidence that Chris knew about this in April 2019 or even earlier like maybe Oct 2018...and if he knew about it before it was announced , then he witheld this information from all of us.. 42) The NFL / MLS "Deals" We very nearly had a deal with the NFL and MLS...or have / had a chance to make deals with them...its all bullshit. The guy cant even make a deal with roller derby leagues...and we are expected to believe he is making deals with major leagues? 43) Wefunder / Crowd Funding We started the process to sell shares through we-funder....but they turned us down. Guess what Chris "forgot" to tell us all? THE REASON they turned us down...because ASM / CWH doesn't pass the "smell test"? What was the reason? It seems like maybe the reason was the UNREGISTERED SECURITIES? I mean there had to be a reason..what was it? 44) Share Buyback They were going to buy back company shares from investors....and at times stated the shares were so valuable they would gladly buy them back for X amount because they were sure to go up in price...but when push comes to shove they NEVER will buy this worthless junk back......even for 1 penny. A lot of the 'tyes men' have stated they would also buy shares back from unhappy investors but of course they never do this in reality. 45) Telling the truth, even if it is harmful to Chris / ASM is some type of Slander or Libel Chris would like you to think that calling him out on fraud and lies is some type of "libel" or "slander" but as anyone knows...telling the truth is not slander or libel. He is trying to scare people from telling the truth. Blowing the whistle on his fraud is NOT slander or libel. Period. He is the CEO of a company that he sold shares of stock in, fraudulently. He must and will be held accountable. 46) The market cap number is a legitimate indicator of the validity of ASM Chris love to throw around market capitalization numbers (4 Billion LOL) as if they mean anything at all or indicate that this market is healthy. They include the learning market (fake money) and the margin (also fake money). If you subtract the learning market, the bonus margin, and the money "used" by chris for data, rent, cars etc...you have pretty much zero market cap in reality. 47) ASM has a way of checking if an investor is accredited: See here: https://www.reddit.com/ASMEunfiltered/comments/eacs69/new_lies_regarding_searching_for_for_accredited/ . In my understanding , one of the ways (in some cases) un-registered securities can be sold is if it is to an "accredited" investor. The SEC has said Chris has no means of checking this. I would personally believe the SEC at this point....and I will count this as a lie until it is proven that Chris / ASM actually does have a way of legitimately checking accreditation. 48) The reason Chris withheld the fact the SEC was investigating him and suing him was because the SEC told him he couldnt tell us. BULLSHIT. In the audio Chris makes absurd claims that he couldnt tell "investors" of his problems with the SEC because they told him not to talk about it. Yet meanwhile he kept taking money from investors as if everything was fine..KNOWING that trouble was brewing and KNOWING that the shit was going to hit the fan. Show me a letter by the SEC that says he can't warn his investors of an impending action by them SHOW IT TO US. If you show this to us, I'll remove this lie. It doesnt make any sense because the SEC exists to protect us from predators like Chris , so why would they tell him he cannot warn us of problems with the SEC????? MAKES ZERO SENSE. Does not pass the smell test. This is a lie by omission..taking our money , pretending things are fine....but KNOWING problems are coming. The bottom line: Chris didnt say SHIT about this anywhere that I know of until AFTER it was posted publicly that the lawsuit was filed...I heard about this online before it was ever mentioned by chris in any conference call or statement by him. 49) Not sure if this is technically a "lie" or not but the guy / ASM has at least 10 twitter accounts...here are a few of them: 1) https://twitter.com/AllSportsMarket 2) https://twitter.com/rabalais_cva 3) https://twitter.com/asmclients 4) https://twitter.com/thesportsvote 5) https://twitter.com/SportsFolios 6) https://twitter.com/MySportsWiki 7) https://twitter.com/chrisrabalais 8) https://twitter.com/NuSportsEconomy 9) https://twitter.com/ASMFreeApp 10) https://twitter.com/ASM_Advisor (not 100% on this one but it looks fake) ..etc..... It looks as if this one: https://twitter.com/ASMFreeApp has a bunch of bots or paid 'farm' followers. So, while not a 'lie' exactly...very odd and shady behavior. 50) In the "Investors Q& A" found here: https://tinyurl.com/spbznmf They failed to disclose the Seth Leon case, the failed attempt at bankruptcy discharge of the fraud debt, and failed to disclose the debt owed to Seth Leon. So they lied in the sections about Legal Problems and they Lied in the sections about Debt. This is in a Q&A involving potential ionvestors so they are lying to potential investors about the risks. 51) Chris will "fact check" and respond to every accusation made against him and prove that these things are lies told by "known liars" https://i.imgur.com/HaGfekN.jpg So a couple of weeks ago, Chris said he would fact check all of the "lies" told about him...so I thought I would do him a big favor and make a huge list. His claim was that everyone saying all of these things are "known liars" and none of these things is true. He says they are all bogus "claims" made by "liars." He said he would refute these"claims." Well guess what asshole? Every songle person reading this is probably a victim of yours, and they KNOW all of these things aren't "claims" ... they are facts. I have done my best here to stick to things that are universal..that we have all witnessed as investors. Now (shockingly) chris refuses to "fact check" any of these "lies." He says he will respond only if you sign your name and send him a private e-mail or make a post on his censored and controlled website where he has to approve any post before it is seen by the public... So I will add this as yet another lie. He will never refute SHIT. He is a thief and a liar. and a con man....and CAN"T refute anything said above. Period. More than likely if anyone posted this list on his forums, he would NEVER allow it to stand....so how is anyone supposed to get this list "fact checked"? The only Known liar here..well..I think we all know who that is... You would think he might want to address these things publicly instead of making people ask via e-mail and leaving a cloud of suspicion for potential investors to see..and maybe he would rather answer one time,rather than a bunch of separate e-mails......but I guess when there are literally no answers to any of these things, the only solution is to try and hide it more...
Dear Groestlers, it goes without saying that 2020 has been a difficult time for millions of people worldwide. The groestlcoin team would like to take this opportunity to wish everyone our best to everyone coping with the direct and indirect effects of COVID-19. Let it bring out the best in us all and show that collectively, we can conquer anything. The centralised banks and our national governments are facing unprecedented times with interest rates worldwide dropping to record lows in places. Rest assured that this can only strengthen the fundamentals of all decentralised cryptocurrencies and the vision that was seeded with Satoshi's Bitcoin whitepaper over 10 years ago. Despite everything that has been thrown at us this year, the show must go on and the team will still progress and advance to continue the momentum that we have developed over the past 6 years. In addition to this, we'd like to remind you all that this is Groestlcoin's 6th Birthday release! In terms of price there have been some crazy highs and lows over the years (with highs of around $2.60 and lows of $0.000077!), but in terms of value– Groestlcoin just keeps getting more valuable! In these uncertain times, one thing remains clear – Groestlcoin will keep going and keep innovating regardless. On with what has been worked on and completed over the past few months.
UPDATED - Groestlcoin Core 2.18.2
This is a major release of Groestlcoin Core with many protocol level improvements and code optimizations, featuring the technical equivalent of Bitcoin v0.18.2 but with Groestlcoin-specific patches. On a general level, most of what is new is a new 'Groestlcoin-wallet' tool which is now distributed alongside Groestlcoin Core's other executables. NOTE: The 'Account' API has been removed from this version which was typically used in some tip bots. Please ensure you check the release notes from 2.17.2 for details on replacing this functionality.
Builds are now done through Gitian
Calls to getblocktemplate will fail if the segwit rule is not specified. Calling getblocktemplate without segwit specified is almost certainly a misconfiguration since doing so results in lower rewards for the miner. Failed calls will produce an error message describing how to enable the segwit rule.
A warning is printed if an unrecognized section name is used in the configuration file. Recognized sections are [test], [main], and [regtest].
Four new options are available for configuring the maximum number of messages that ZMQ will queue in memory (the "high water mark") before dropping additional messages. The default value is 1,000, the same as was used for previous releases.
The rpcallowip option can no longer be used to automatically listen on all network interfaces. Instead, the rpcbind parameter must be used to specify the IP addresses to listen on. Listening for RPC commands over a public network connection is insecure and should be disabled, so a warning is now printed if a user selects such a configuration. If you need to expose RPC in order to use a tool like Docker, ensure you only bind RPC to your localhost, e.g. docker run [...] -p 127.0.0.1:1441:1441 (this is an extra :1441 over the normal Docker port specification).
The rpcpassword option now causes a startup error if the password set in the configuration file contains a hash character (#), as it's ambiguous whether the hash character is meant for the password or as a comment.
The whitelistforcerelay option is used to relay transactions from whitelisted peers even when not accepted to the mempool. This option now defaults to being off, so that changes in policy and disconnect/ban behavior will not cause a node that is whitelisting another to be dropped by peers.
A new short about the JSON-RPC interface describes cases where the results of anRPC might contain inconsistencies between data sourced from differentsubsystems, such as wallet state and mempool state.
A new document introduces Groestlcoin Core's BIP174 interface, which is used to allow multiple programs to collaboratively work to create, sign, and broadcast new transactions. This is useful for offline (cold storage) wallets, multisig wallets, coinjoin implementations, and many other cases where two or more programs need to interact to generate a complete transaction.
The output script descriptor (https://github.com/groestlcoin/groestlcoin/blob/mastedoc/descriptors.md) documentation has been updated with information about new features in this still-developing language for describing the output scripts that a wallet or other program wants to receive notifications for, such as which addresses it wants to know received payments. The language is currently used in multiple new and updated RPCs described in these release notes and is expected to be adapted to other RPCs and to the underlying wallet structure.
A new --disable-bip70 option may be passed to ./configure to prevent Groestlcoin-Qt from being built with support for the BIP70 payment protocol or from linking libssl. As the payment protocol has exposed Groestlcoin Core to libssl vulnerabilities in the past, builders who don't need BIP70 support are encouraged to use this option to reduce their exposure to future vulnerabilities.
The minimum required version of Qt (when building the GUI) has been increased from 5.2 to 5.5.1 (the depends system provides 5.9.7)
getnodeaddresses returns peer addresses known to this node. It may be used to find nodes to connect to without using a DNS seeder.
listwalletdir returns a list of wallets in the wallet directory (either the default wallet directory or the directory configured bythe -walletdir parameter).
getrpcinfo returns runtime details of the RPC server. Currently, it returns an array of the currently active commands and how long they've been running.
deriveaddresses returns one or more addresses corresponding to an output descriptor.
getdescriptorinfo accepts a descriptor and returns information aboutit, including its computed checksum.
joinpsbts merges multiple distinct PSBTs into a single PSBT. The multiple PSBTs must have different inputs. The resulting PSBT will contain every input and output from all the PSBTs. Any signatures provided in any of the PSBTs will be dropped.
analyzepsbt examines a PSBT and provides information about what the PSBT contains and the next steps that need to be taken in order to complete the transaction. For each input of a PSBT, analyze psbt provides information about what information is missing for that input, including whether a UTXO needs to be provided, what pubkeys still need to be provided, which scripts need to be provided, and what signatures are still needed. Every input will also list which role is needed to complete that input, and analyzepsbt will also list the next role in general needed to complete the PSBT. analyzepsbt will also provide the estimated fee rate and estimated virtual size of the completed transaction if it has enough information to do so.
utxoupdatepsbt searches the set of Unspent Transaction Outputs (UTXOs) to find the outputs being spent by the partial transaction. PSBTs need to have the UTXOs being spent to be provided because the signing algorithm requires information from the UTXO being spent. For segwit inputs, only the UTXO itself is necessary. For non-segwit outputs, the entire previous transaction is needed so that signers can be sure that they are signing the correct thing. Unfortunately, because the UTXO set only contains UTXOs and not full transactions, utxoupdatepsbt will only add the UTXO for segwit inputs.
getpeerinfo now returns an additional minfeefilter field set to the peer's BIP133 fee filter. You can use this to detect that you have peers that are willing to accept transactions below the default minimum relay fee.
The mempool RPCs, such as getrawmempool with verbose=true, now return an additional "bip125-replaceable" value indicating whether thetransaction (or its unconfirmed ancestors) opts-in to asking nodes and miners to replace it with a higher-feerate transaction spending any of the same inputs.
settxfee previously silently ignored attempts to set the fee below the allowed minimums. It now prints a warning. The special value of"0" may still be used to request the minimum value.
getaddressinfo now provides an ischange field indicating whether the wallet used the address in a change output.
importmulti has been updated to support P2WSH, P2WPKH, P2SH-P2WPKH, and P2SH-P2WSH. Requests for P2WSH and P2SH-P2WSH accept an additional witnessscript parameter.
importmulti now returns an additional warnings field for each request with an array of strings explaining when fields are being ignored or are inconsistent, if there are any.
getaddressinfo now returns an additional solvable Boolean field when Groestlcoin Core knows enough about the address's scriptPubKey, optional redeemScript, and optional witnessScript for the wallet to be able to generate an unsigned input spending funds sent to that address.
The getaddressinfo, listunspent, and scantxoutset RPCs now return an additional desc field that contains an output descriptor containing all key paths and signing information for the address (except for the private key). The desc field is only returned for getaddressinfo and listunspent when the address is solvable.
importprivkey will preserve previously-set labels for addresses or public keys corresponding to the private key being imported. For example, if you imported a watch-only address with the label "coldwallet" in earlier releases of Groestlcoin Core, subsequently importing the private key would default to resetting the address's label to the default empty-string label (""). In this release, the previous label of "cold wallet" will be retained. If you optionally specify any label besides the default when calling importprivkey, the new label will be applied to the address.
getmininginfo now omits currentblockweight and currentblocktx when a block was never assembled via RPC on this node.
The getrawtransaction RPC & REST endpoints no longer check the unspent UTXO set for a transaction. The remaining behaviors are as follows:
If a blockhash is provided, check the corresponding block.
If no blockhash is provided, check the mempool.
If no blockhash is provided but txindex is enabled, also check txindex.
unloadwallet is now synchronous, meaning it will not return until the wallet is fully unloaded.
importmulti now supports importing of addresses from descriptors. A desc parameter can be provided instead of the "scriptPubKey" in are quest, as well as an optional range for ranged descriptors to specify the start and end of the range to import. Descriptors with key origin information imported through importmulti will have their key origin information stored in the wallet for use with creating PSBTs.
listunspent has been modified so that it also returns witnessScript, the witness script in the case of a P2WSH orP2SH-P2WSH output.
createwallet now has an optional blank argument that can be used to create a blank wallet. Blank wallets do not have any keys or HDseed. They cannot be opened in software older than 2.18.2. Once a blank wallet has a HD seed set (by using sethdseed) or private keys, scripts, addresses, and other watch only things have been imported, the wallet is no longer blank and can be opened in 2.17.2. Encrypting a blank wallet will also set a HD seed for it.
signrawtransaction is removed after being deprecated and hidden behind a special configuration option in version 2.17.2.
The 'account' API is removed after being deprecated in v2.17.2 The 'label' API was introduced in v2.17.2 as a replacement for accounts. See the release notes from v2.17.2 for a full description of the changes from the 'account' API to the 'label' API.
addwitnessaddress is removed after being deprecated in version 2.16.0.
generate is deprecated and will be fully removed in a subsequent major version. This RPC is only used for testing, but its implementation reached across multiple subsystems (wallet and mining), so it is being deprecated to simplify the wallet-node interface. Projects that are using generate for testing purposes should transition to using the generatetoaddress RPC, which does not require or use the wallet component. Calling generatetoaddress with an address returned by the getnewaddress RPC gives the same functionality as the old generate RPC. To continue using generate in this version, restart groestlcoind with the -deprecatedrpc=generate configuration option.
Be reminded that parts of the validateaddress command have been deprecated and moved to getaddressinfo. The following deprecated fields have moved to getaddressinfo: ismine, iswatchonly,script, hex, pubkeys, sigsrequired, pubkey, embedded,iscompressed, label, timestamp, hdkeypath, hdmasterkeyid.
The addresses field has been removed from the validateaddressand getaddressinfo RPC methods. This field was confusing since it referred to public keys using their P2PKH address. Clients should use the embedded.address field for P2SH or P2WSH wrapped addresses, and pubkeys for inspecting multisig participants.
A new /rest/blockhashbyheight/ endpoint is added for fetching the hash of the block in the current best blockchain based on its height (how many blocks it is after the Genesis Block).
A new Window menu is added alongside the existing File, Settings, and Help menus. Several items from the other menus that opened new windows have been moved to this new Window menu.
In the Send tab, the checkbox for "pay only the required fee" has been removed. Instead, the user can simply decrease the value in the Custom Fee rate field all the way down to the node's configured minimumrelay fee.
In the Overview tab, the watch-only balance will be the only balance shown if the wallet was created using the createwallet RPC and thedisable_private_keys parameter was set to true.
The launch-on-startup option is no longer available on macOS if compiled with macosx min version greater than 10.11 (useCXXFLAGS="-mmacosx-version-min=10.11" CFLAGS="-mmacosx-version-min=10.11" for setting the deployment sdkversion)
A new groestlcoin-wallet tool is now distributed alongside Groestlcoin Core's other executables. Without needing to use any RPCs, this tool can currently create a new wallet file or display some basic information about an existing wallet, such as whether the wallet is encrypted, whether it uses an HD seed, how many transactions it contains, and how many address book entries it has.
Since version 2.16.0, Groestlcoin Core's built-in wallet has defaulted to generating P2SH-wrapped segwit addresses when users want to receive payments. These addresses are backwards compatible with all widely used software. Starting with Groestlcoin Core 2.20.1 (expected about a year after 2.18.2), Groestlcoin Core will default to native segwitaddresses (bech32) that provide additional fee savings and other benefits. Currently, many wallets and services already support sending to bech32 addresses, and if the Groestlcoin Core project sees enough additional adoption, it will instead default to bech32 receiving addresses in Groestlcoin Core 2.19.1. P2SH-wrapped segwit addresses will continue to be provided if the user requests them in the GUI or by RPC, and anyone who doesn't want the update will be able to configure their default address type. (Similarly, pioneering users who want to change their default now may set the addresstype=bech32 configuration option in any Groestlcoin Core release from 2.16.0 up.)
BIP 61 reject messages are now deprecated. Reject messages have no use case on the P2P network and are only logged for debugging by most network nodes. Furthermore, they increase bandwidth and can be harmful for privacy and security. It has been possible to disable BIP 61 messages since v2.17.2 with the -enablebip61=0 option. BIP 61 messages will be disabled by default in a future version, before being removed entirely.
The submitblock RPC previously returned the reason a rejected block was invalid the first time it processed that block but returned a generic "duplicate" rejection message on subsequent occasions it processed the same block. It now always returns the fundamental reason for rejecting an invalid block and only returns "duplicate" for valid blocks it has already accepted.
A new submitheader RPC allows submitting block headers independently from their block. This is likely only useful for testing.
The signrawtransactionwithkey and signrawtransactionwithwallet RPCs have been modified so that they also optionally accept a witnessScript, the witness script in the case of a P2WSH orP2SH-P2WSH output. This is compatible with the change to listunspent.
For the walletprocesspsbt and walletcreatefundedpsbt RPCs, if thebip32derivs parameter is set to true but the key metadata for a public key has not been updated yet, then that key will have a derivation path as if it were just an independent key (i.e. no derivation path and its master fingerprint is itself).
The -usehd configuration option was removed in version 2.16.0 From that version onwards, all new wallets created are hierarchical deterministic wallets. This release makes specifying -usehd an invalid configuration option.
This release allows peers that your node automatically disconnected for misbehaviour (e.g. sending invalid data) to reconnect to your node if you have unused incoming connection slots. If your slots fill up, a misbehaving node will be disconnected to make room for nodes without a history of problems (unless the misbehaving node helps your node in some other way, such as by connecting to a part of the Internet from which you don't have many other peers). Previously, Groestlcoin Core banned the IP addresses of misbehaving peers for a period (default of 1 day); this was easily circumvented by attackers with multiple IP addresses. If you manually ban a peer, such as by using the setban RPC, all connections from that peer will still be rejected.
The key metadata will need to be upgraded the first time that the HDseed is available. For unencrypted wallets this will occur on wallet loading. For encrypted wallets this will occur the first time the wallet is unlocked.
Newly encrypted wallets will no longer require restarting the software. Instead such wallets will be completely unloaded and reloaded to achieve the same effect.
A sub-project of Bitcoin Core now provides Hardware Wallet Interaction (HWI) scripts that allow command-line users to use several popular hardware key management devices with Groestlcoin Core. See their project page for details.
This release changes the Random Number Generator (RNG) used from OpenSSL to Groestlcoin Core's own implementation, although entropy gathered by Groestlcoin Core is fed out to OpenSSL and then read back in when the program needs strong randomness. This moves Groestlcoin Core a little closer to no longer needing to depend on OpenSSL, a dependency that has caused security issues in the past. The new implementation gathers entropy from multiple sources, including from hardware supporting the rdseed CPU instruction.
On macOS, Groestlcoin Core now opts out of application CPU throttling ("app nap") during initial blockchain download, when catching up from over 100 blocks behind the current chain tip, or when reindexing chain data. This helps prevent these operations from taking an excessively long time because the operating system is attempting to conserve power.
How to Upgrade?
Windows If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), then run the installer. OSX If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), run the dmg and drag Groestlcoin Core to Applications. Ubuntu http://groestlcoin.org/forum/index.php?topic=441.0
ALL NEW - Groestlcoin Moonshine iOS/Android Wallet
Built with React Native, Moonshine utilizes Electrum-GRS's JSON-RPC methods to interact with the Groestlcoin network. GRS Moonshine's intended use is as a hot wallet. Meaning, your keys are only as safe as the device you install this wallet on. As with any hot wallet, please ensure that you keep only a small, responsible amount of Groestlcoin on it at any given time.
Groestlcoin Mainnet & Testnet supported
Multiple wallet support
Electrum - Support for both random and custom peers
Biometric + Pin authentication
Custom fee selection
Import mnemonic phrases via manual entry or scanning
BIP39 Passphrase functionality
Support for Segwit-compatible & legacy addresses in settings
Support individual private key sweeping
UTXO blacklisting - Accessible via the Transaction Detail view, this allows users to blacklist any utxo that they do not wish to include in their list of available utxo's when sending transactions. Blacklisting a utxo excludes its amount from the wallet's total balance.
Ability to Sign & Verify Messages
Support BitID for password-free authentication
Coin Control - This can be accessed from the Send Transaction view and basically allows users to select from a list of available UTXO's to include in their transaction.
HODL GRS connects directly to the Groestlcoin network using SPV mode and doesn't rely on servers that can be hacked or disabled. HODL GRS utilizes AES hardware encryption, app sandboxing, and the latest security features to protect users from malware, browser security holes, and even physical theft. Private keys are stored only in the secure enclave of the user's phone, inaccessible to anyone other than the user. Simplicity and ease-of-use is the core design principle of HODL GRS. A simple recovery phrase (which we call a Backup Recovery Key) is all that is needed to restore the user's wallet if they ever lose or replace their device. HODL GRS is deterministic, which means the user's balance and transaction history can be recovered just from the backup recovery key.
Simplified payment verification for fast mobile performance
Groestlcoin Seed Savior is a tool for recovering BIP39 seed phrases. This tool is meant to help users with recovering a slightly incorrect Groestlcoin mnemonic phrase (AKA backup or seed). You can enter an existing BIP39 mnemonic and get derived addresses in various formats. To find out if one of the suggested addresses is the right one, you can click on the suggested address to check the address' transaction history on a block explorer.
If a word is wrong, the tool will try to suggest the closest option.
If a word is missing or unknown, please type "?" instead and the tool will find all relevant options.
NOTE: NVidia GPU or any CPU only. AMD graphics cards will not work with this address generator. VanitySearch is a command-line Segwit-capable vanity Groestlcoin address generator. Add unique flair when you tell people to send Groestlcoin. Alternatively, VanitySearch can be used to generate random addresses offline. If you're tired of the random, cryptic addresses generated by regular groestlcoin clients, then VanitySearch is the right choice for you to create a more personalized address. VanitySearch is a groestlcoin address prefix finder. If you want to generate safe private keys, use the -s option to enter your passphrase which will be used for generating a base key as for BIP38 standard (VanitySearch.exe -s "My PassPhrase" FXPref). You can also use VanitySearch.exe -ps "My PassPhrase" which will add a crypto secure seed to your passphrase. VanitySearch may not compute a good grid size for your GPU, so try different values using -g option in order to get the best performances. If you want to use GPUs and CPUs together, you may have best performances by keeping one CPU core for handling GPU(s)/CPU exchanges (use -t option to set the number of CPU threads).
Fixed size arithmetic
Fast Modular Inversion (Delayed Right Shift 62 bits)
SecpK1 Fast modular multiplication (2 steps folding 512bits to 256bits using 64 bits digits)
Use some properties of elliptic curve to generate more keys
SSE Secure Hash Algorithm SHA256 and RIPEMD160 (CPU)
Groestlcoin EasyVanity 2020 is a windows app built from the ground-up and makes it easier than ever before to create your very own bespoke bech32 address(es) when whilst not connected to the internet. If you're tired of the random, cryptic bech32 addresses generated by regular Groestlcoin clients, then Groestlcoin EasyVanity2020 is the right choice for you to create a more personalised bech32 address. This 2020 version uses the new VanitySearch to generate not only legacy addresses (F prefix) but also Bech32 addresses (grs1 prefix).
Ability to continue finding keys after first one is found
Includes warning on start-up if connected to the internet
Ability to output keys to a text file (And shows button to open that directory)
Show and hide the private key with a simple toggle switch
Show full output of commands
Ability to choose between Processor (CPU) and Graphics Card (GPU) ( NVidia ONLY! )
Features both a Light and Dark Material Design-Style Themes
Free software - MIT. Anyone can audit the code.
Written in C# - The code is short, and easy to review.
Groestlcoin WPF is an alternative full node client with optional lightweight 'thin-client' mode based on WPF. Windows Presentation Foundation (WPF) is one of Microsoft's latest approaches to a GUI framework, used with the .NET framework. Its main advantages over the original Groestlcoin client include support for exporting blockchain.dat and including a lite wallet mode. This wallet was previously deprecated but has been brought back to life with modern standards.
Works via TOR or SOCKS5 proxy
Can use bootstrap.dat format as blockchain database
Import/Export blockchain to/from bootstrap.dat
Import wallet.dat from Groestlcoin-qt wallet
Export wallet to wallet.dat
Use both groestlcoin-wpf and groestlcoin-qt with the same addresses in parallel. When you send money from one program, the transaction will automatically be visible on the other wallet.
Rescan blockchain with a simple mouse click
Works as a full node and listens to port 1331 (listening port can be changed)
Fast Block verifying, parallel processing on multi-core CPUs
Mine Groestlcoins with your CPU by a simple mouse click
All private keys are kept encrypted on your local machine (or on a USB stick)
Lite - Has a lightweight "thin client" mode which does not require a new user to download the entire Groestlcoin chain and store it
Free and decentralised - Open Source under GNU license
Fixed Import/Export to wallet.dat
Rescan wallet option
Change wallet password option
Address type and Change type options through *.conf file
Import from bootstrap.dat - It is a flat, binary file containing Groestlcoin blockchain data, from the genesis block through a recent height. All versions automatically validate and import the file "grs.bootstrap.dat" in the GRS directory. Grs.bootstrap.dat is compatible with Qt wallet. GroestlCoin-Qt can load from it.
In Full mode file %APPDATA%\Groestlcoin-WPF\GRS\GRS.bootstrap.dat is full blockchain in standard bootstrap.dat format and can be used with other clients.
Groestlcoin Electrum Personal Server aims to make using Electrum Groestlcoin wallet more secure and more private. It makes it easy to connect your Electrum-GRS wallet to your own full node. It is an implementation of the Electrum-grs server protocol which fulfils the specific need of using the Electrum-grs wallet backed by a full node, but without the heavyweight server backend, for a single user. It allows the user to benefit from all Groestlcoin Core's resource-saving features like pruning, blocks only and disabled txindex. All Electrum-GRS's feature-richness like hardware wallet integration, multi-signature wallets, offline signing, seed recovery phrases, coin control and so on can still be used, but connected only to the user's own full node. Full node wallets are important in Groestlcoin because they are a big part of what makes the system be trust-less. No longer do people have to trust a financial institution like a bank or PayPal, they can run software on their own computers. If Groestlcoin is digital gold, then a full node wallet is your own personal goldsmith who checks for you that received payments are genuine. Full node wallets are also important for privacy. Using Electrum-GRS under default configuration requires it to send (hashes of) all your Groestlcoin addresses to some server. That server can then easily spy on your transactions. Full node wallets like Groestlcoin Electrum Personal Server would download the entire blockchain and scan it for the user's own addresses, and therefore don't reveal to anyone else which Groestlcoin addresses they are interested in. Groestlcoin Electrum Personal Server can also broadcast transactions through Tor which improves privacy by resisting traffic analysis for broadcasted transactions which can link the IP address of the user to the transaction. If enabled this would happen transparently whenever the user simply clicks "Send" on a transaction in Electrum-grs wallet. Note: Currently Groestlcoin Electrum Personal Server can only accept one connection at a time.
Use your own node
Uses less CPU and RAM than ElectrumX
Used intermittently rather than needing to be always-on
Doesn't require an index of every Groestlcoin address ever used like on ElectrumX
UPDATED – Android Wallet 7.38.1 - Main Net + Test Net
The app allows you to send and receive Groestlcoin on your device using QR codes and URI links. When using this app, please back up your wallet and email them to yourself! This will save your wallet in a password protected file. Then your coins can be retrieved even if you lose your phone.
Add confidence messages, helping users to understand the confidence state of their payments.
Handle edge case when restoring via an external app.
Count devices with a memory class of 128 MB as low ram.
Introduce dark mode on Android 10 devices.
Reduce memory usage of PIN-protected wallets.
Tapping on the app's version will reveal a checksum of the APK that was installed.
Fix issue with confirmation of transactions that empty your wallet.
Groestlcoin Sentinel is a great solution for anyone who wants the convenience and utility of a hot wallet for receiving payments directly into their cold storage (or hardware wallets). Sentinel accepts XPUB's, YPUB'S, ZPUB's and individual Groestlcoin address. Once added you will be able to view balances, view transactions, and (in the case of XPUB's, YPUB's and ZPUB's) deterministically generate addresses for that wallet. Groestlcoin Sentinel is a fork of Groestlcoin Samourai Wallet with all spending and transaction building code removed.
I keep reading people say bitcoin development is stalled
But in practice there's more going on right now than there's ever been in the last few years. You just have to look in the right places. Here's a few days of documented github activity from the bitcoin slack and I've a feeling there are hundreds more people working on Bitcoin projects outside of the work being done by core: github BOT [6:28 PM] [bitcoin:master] 2 new commits by Daniel Kraft and 1 other: f93c2a1 net: Avoid duplicate getheaders requests. - Daniel Kraft 8e8bebc Merge #8054: net: Avoid duplicate getheaders requests. - Wladimir J. van der Laan [6:28] [bitcoin/bitcoin] Pull request closed: #8054 net: Avoid duplicate getheaders requests. by laanwj [6:31] [bitcoin:master] 6 new commits by Pieter Wuille and 1 other: d253ec4 Make ProcessNewBlock dbp const and update comment - Pieter Wuille 316623f Switch reindexing to AcceptBlock in-loop and ActivateBestChain afterwards - Pieter Wuille fb8fad1 Optimize ActivateBestChain for long chains - Pieter Wuille d3d7547 Add -reindex-chainstate that does not rebuild block index - Pieter Wuille b4d24e1 Report reindexing progress in GUI - Pieter Wuille Show more... [6:31] [bitcoin/bitcoin] Pull request closed: #7917 Optimize reindex by laanwj Joshua Unseth [9:55 PM] joined #commit-activity. Also, @sjors joined and left. ----- May 19th ----- github BOT [12:08 AM] [bitcoin/bitcoin] Pull request submitted by EthanHeilman
8070 Remove non-determinism which is breaking net_tests #8069
If addrmanUncorrupted does not have the same nKey every time it will map addrs to different bucket positions and occasionally cause a collision between two addrs, breaking the test. github BOT [1:00 AM] [bitcoin/bitcoin] Pull request closed: #7716 [0.11] Backport BIP9 and softfork for BIP's 68,112,113 by morcos Eragmus You Should Probably Stop Modding [1:12 AM] joined #commit-activity. Also, @buttmunch joined, @icandothisallday joined, @misnomer joined, @coreneedstostop joined, @xchins joined, @jbeener joined, @jbleeks joined, @whalepanda joined, @grinny joined, @alex_may joined, @mr_e joined. github BOT [2:46 PM] [bitcoin:master] 5 new commits by Warren Togami and 1 other: 00678bd Make failures to connect via Socks5() more informative and less unnecessarily scary. - Warren Togami 0d9af79 SOCKS5 connecting and connected messages with -debug=net. - Warren Togami 94fd1d8 Make Socks5() InterruptibleRecv() timeout/failures informative. - Warren Togami bf9266e Use Socks5ErrorString() to decode error responses from socks proxy. - Warren Togami 18436d8 Merge #8033: Fix Socks5() connect failures to be less noisy and less unnecessarily scary - Wladimir J. Show more... [2:46] [bitcoin/bitcoin] Pull request closed: #8033 Fix Socks5() connect failures to be less noisy and less unnecessarily scary by laanwj github BOT [3:56 PM] [bitcoin:master] 3 new commits by EthanHeilman and 2 others: f4119c6 Remove non-determinism which is breaking net_tests #8069 - EthanHeilman 2a8b358 Fix typo adddrman to addrman as requested in #8070 - Ethan Heilman 7771aa5 Merge #8070: Remove non-determinism which is breaking net_tests #8069 - Wladimir J. van der Laan [3:56] [bitcoin/bitcoin] Pull request closed: #8070 Remove non-determinism which is breaking net_tests #8069 by laanwj github BOT [5:18 PM] [bitcoin/bitcoin] Pull request submitted by MarcoFalke
8072 travis: 'make check' in parallel and verbose
• 'make check' in parallel, since the log will take care of clean output • 'make check' verbose, so that test failure causes aren't hidden Fixes: #8071 github BOT [7:56 PM] [bitcoin/bitcoin] Pull request submitted by rat4
8073 qt: askpassphrasedialog: Clear pass fields on accept
This is usability improvement in a case if user gets re-asked passphrase. (e.g. made a typo) Victor Broman [8:01 PM] joined #commit-activity. Also, @bb joined, @ziiip joined. ----- May 20th ----- github BOT [12:34 PM] [bitcoin/bitcoin] Pull request submitted by jsantos4you
debug.data.txt [12:37] [bitcoin/bitcoin] Pull request closed: #8075 0.12 by sipa github BOT [3:37 PM] [bitcoin/bitcoin] Pull request closed: #7082 Do not absolutely protect local peers and make eviction more aggressive. by gmaxwell github BOT [3:44 PM] [bitcoin:master] 2 new commits by Cory Fields and 1 other: 401ae65 travis: 'make check' in parallel and verbose - Cory Fields 1b87e5b Merge #8072: travis: 'make check' in parallel and verbose - MarcoFalke [3:44] [bitcoin/bitcoin] Pull request closed: #8072 travis: 'make check' in parallel and verbose by MarcoFalke github BOT [3:58 PM] [bitcoin/bitcoin] Pull request closed: #7093 Address mempool information leak and resource wasting attacks. by gmaxwell github BOT [6:11 PM] [bitcoin/bitcoin] Pull request submitted by sdaftuar
8076 VerifyDB: don't check blocks that have been pruned
If a pruning node ends up in a state where it has very few blocks on disk, then a node could fail to start up in VerifyDB. This pull changes the behavior for pruning nodes, so that we will just not bother trying to check blocks that have been pruned. I don't expect this edge case to be triggered much in practice currently; this is a preparatory commit for segwit (to deal with the case of pruning nodes that upgrade after segwit activation). @sipa Erik Hedman [6:20 PM] joined #commit-activity github BOT [8:46 PM] [bitcoin/bitcoin] Pull request submitted by jtimon
8077 Consensus: Decouple from chainparams.o and timedata.o
Do it for the consensus-critical functions: • CheckBlockHeader • CheckBlock • ContextualCheckBlockHeader Show more... github BOT [9:26 PM] [bitcoin:master] 3 new commits by MarcoFalke: fac9349 [qa] Remove hardcoded "4 nodes" from test_framework - MarcoFalke fad68f7 [qa] Reduce node count for some tests - MarcoFalke 8844ef1 Merge #8056: [qa] Remove hardcoded "4 nodes" from test_framework - MarcoFalke [9:27] [bitcoin/bitcoin] Pull request closed: #8056 [qa] Remove hardcoded "4 nodes" from test_framework by MarcoFalke github BOT [9:48 PM] [bitcoin/bitcoin] Pull request submitted by petertodd
8078 Disable the mempool P2P command when bloom filters disabled
Only useful to SPV peers, and attackers... like bloom is a DoS vector as far more data is sent than received. null radix [10:15 PM] joined #commit-activity github BOT [11:34 PM] [bitcoin:master] 2 new commits by MarcoFalke: fab5233 [qa] test_framework: Set wait-timeout for bitcoind procs - MarcoFalke 37f9a1f Merge #8047: [qa] test_framework: Set wait-timeout for bitcoind procs - MarcoFalke [11:34] [bitcoin/bitcoin] Pull request closed: #8047 [qa] test_framework: Set wait-timeout for bitcoind procs by MarcoFalke github BOT [11:48 PM] [bitcoin/bitcoin] Pull request closed: #7826 [Qt] show conflicts of unconfirmed transactions in the UI by jonasschnelli [11:50] [bitcoin/bitcoin] Pull request re-opened: #7826 [Qt] show conflicts of unconfirmed transactions in the UI by jonasschnelli ----- May 21st ----- Rentaro Matsukata [1:56 AM] joined #commit-activity. Also, @evilone joined, @cryptop joined, @thomas5 joined. github BOT [1:54 PM] [bitcoin/bitcoin] Pull request submitted by gmaxwell
8080 Do not use mempool for GETDATA for tx accepted after the last mempool req.
The ability to GETDATA a transaction which has not (yet) been relayed is a privacy loss vector. The use of the mempool for this was added as part of the mempool p2p message and is only needed to fetch transactions returned by it. github BOT [5:48 PM] [bitcoin/bitcoin] Pull request submitted by gmaxwell
8082 Defer inserting into maprelay until just before relaying.
Also extend the relaypool lifetime by 1 minute (6%) to 16 minutes. This reduces the rate of not founds by better matching the far end expectations, it also improves privacy by removing the ability to use getdata to probe for a node having a txn before Show more... Sergey Ukustov [9:17 PM] joined #commit-activity. Also, @stoicism joined. ----- Yesterday May 22nd, 2016 ----- github BOT [5:59 AM] [bitcoin/bitcoin] Pull request submitted by jonasschnelli
8083 Add support for dnsseeds with option to filter by servicebits
Opposite part of https://github.com/sipa/bitcoin-seedepull/36. Including new testnet seed that supports filtering. Required for SW #7910. Junseth Sock Puppet Account [6:13 AM] joined #commit-activity github BOT [1:59 PM] [bitcoin/bitcoin] Pull request submitted by gmaxwell
8084 Add recently accepted blocks and txn to AttemptToEvictConnection.
This protect any not-already-protected peers who were the most recent to relay transactions and blocks to us. This also takes increases the eviction agressiveness by making it willing to disconnect a netgroup with only one member. github BOT [5:04 PM] [bitcoin/bitcoin] Pull request submitted by theuni
8085 p2p: Begin encapsulation
This work creates CConnman. The idea is to begin moving data structures and functionality out of globals in net.h and into an instanced class, in order to avoid side-effects in networking code. Eventually, an (internal) api begins to emerge, and as long as the conditions of that api are met, the inner-workings may be a black box. For now (for ease), a single global CConnman is created. Down the road, the instance could be passed around instead. Also, CConnman should be moved out of net.h/net.cpp, Show more... github BOT [5:14 PM] [bitcoin/bitcoin] Pull request submitted by sipa
8086 Use SipHash for node eviction
github BOT [5:50 PM] [bitcoin/bitcoin] Pull request closed: #6844 [REST] Add send raw transaction by lclc ----- Today May 23rd, 2016 ----- yannie888 [5:21 AM] joined #commit-activity. Also, @myco joined, @er_sham joined, @ethdealer joined. github BOT [3:23 PM] [bitcoin/bitcoin] Pull request submitted by pstratem
8087 Introduce CBlockchain and move CheckBlockHeader
[3:23] [bitcoin/bitcoin] Pull request submitted by pstratem
8088 Avoid recalculating vchKeyedNetGroup in eviction logic.
Lazy calculate vchKeyedNetGroup in CNode::GetKeyedNetGroup.
What is Skywire? Where does it fit in with Skycoin?
Skycoin is a blockchain application platform. We have multiple coins in the platform (Metallicoin, mdl.life, solarbankers.com, etc). We let people launch their own blockchain applications (including coins). There are two parts to Skywire. The first part is the Skywire node. The second part is the hardware. Skywire is one of the first applications we are launching on the Skycoin platform. It is one of our flagship applications that has been in development for several years. Skywire is basically a decentralized ISP on blockchain. It is like Tor, but you are paid to run it. You forward packets for your neighbors and you receive coins You pay coins to other people for forwarding your packets. So it is like Tor but on blockchain and you are paid for running the network. Also, while Tor is slow, Skywire was designed to be faster than the current internet, instead of slower. Skywire is a test application for monetizing excess bandwidth. Eventually the software defined networking technology behind Skywire, will allow us to build physical networks (actual mesh nets) that can begin to replace centralized ISPs. However, the current Skywire prototype is still running over the existing internet, but later we will start building out our own hardware. Skywire is a solution for protecting people’s privacy and is also a solution to net neutrality. If Skycoin can can decentralize the ISPs with blockchain, then we wont have to beg the FCC to protect our rights. Skywire is just a prototype of a larger system. Eventually we will allow people to sell bandwidth, computational resources and storage. On the hardware side, the Skywire Miner is a like a personal cloud, for blockchain applications. It has eight computers in it and you plug it in and you can run your blockchain applications on it. You can even earn coins by renting out capacities to other users on the network.
How would your everyday, average Joe user access the Skywire network? Let's say from their phone…
We designed Skywire and Skycoin to be as usable as possible. We think you should not have to be a software developer to use blockchain applications. Skywire is designed to be “zeroconf”, with zero configuration. You just plug in your node and it works. Its plug and play. Eventually you will be able to buy a Skywire Miner and delegate control of the hardware to a “pool”, who will configure it for you and do all the work, optimize the settings and the pool will just take a small fee for the service and owner of the hardware will receive the rest of the coins their miners are earning. You will just plug in the Skyminer and start earning coins. It will be plug and play. Most users will not know their traffic is being carried over Skywire. Just like they do not know if they are using TCP or UDP. They will just connect their computer to the network with wifi or an ethernet cable and it will work exactly like the internet does now.
Are you completely anonymous on Skywire, or do you need to add a VPN and go through Tor for extra protection?
Skywire is designed, to protect users privacy much better than the existing internet. Each node only knows the previous hop and the next hop for any packet. The contents of the packet are encrypted (like HTTPS), so no one can spy on the data. Since Skywire is designed to be faster than the existing internet, you give up a little privacy for the speed. Tor makes packets harder to trace by reshuffling them and slowing them done. While Skywire is designed for pure speed and performance.
Will Skywire users be able to access traditional internet resources like Google and Facebook over Skywire?
Yes. Most users will not even know they are using Skywire at all. It will be completely invisible to them. Skywire has two modes of operation. One mode looks like the normal internet to the user and the other mode is for special applications designed to run completely inside of the Skywire network. Skywire native apps will have increased privacy, speed and performance, but all existing internet apps will still work on the new network.
How difficult will it be for a traditional e-service to port their products and services to Skywire / Skycoin? Are there plans in place to facilitate those transitions as companies find the exceeding value in joining the free distributed internet?
We are going to make it very easy. Existing companies run their whole internal networks on MPLS and Skywire is almost identical to MPLS, so they wont have to make any changes in most cases.
What is the routing protocol? How are the routes found?
Skywire is source routed. This means that you choose the route your data takes. You can chose routes that offer higher privacy, more bandwidth (for video downloads) or lower latency (for gaming). Skywire puts control of the data back to the user.
I have also understand that the protocols underlying in skywire will be/already are pretty different from the Internet protocols. Taking into account the years of research applied to the current Internet and the several strategies for routing it doesn't seem an easy task to rebuild everything and make it work. Where can be found the information about the routing strategies used in skywire?
The routing strategies are user defined. There is no best routing strategy that is optimal for every user or application. Instead we allow people to choose their routes and policies, based upon the application, time of day, available bandwidth, reliability and other factors. This is actually the way the original internet worked. However, it was scrapped because of the RAM limitations of early computers which only had 4 KB of memory. So the internet was built upon stateless routing protocols because of the limitations of the available computers at the time, not because the networking protocols were the best or highest performance. Today even a cell phone has 4 GB of ram and 1 million times the memory of a computer in the 1980s, so there is no reason to accept these limitations anymore. Our implementation is simpler and faster because we are stripping away the layers of junk that have accumulated. The internet was actually built up piecemeal, without any coherence, coordination or planning. The internet today is a mishmash of different ad-hoc protocols that have been duct taped together over decades, without any real design. Skywire is an re-envisioning of the internet, if it was built today knowing what we know now. This means simplifying the protocols and improving the performance.
How will the routing work if someone from Europe wants to access a video from a node in Australia (for example)? How do the nodes know the next hop if they cant read the origin or destiny of any packet?
If you have a route with N hops, then you contact each of the nodes on the route (through a messaging service) and set the route table on each route. Then when you drop a packet in the route, it gets forwarded automatically. You could have 60 or 120 hops between Australia and Europe and its fine. Each individual node only knows the previous hop and the next hop in the chain. That is all the node needs to know.
Could you estimate a timeline for when Skywire will operate independently from the current ISP infrastructure?
I think Skycoin is a very ambitious project and some parts could take ten or twenty years. Even if we started with a network of a few thousand nodes and we were growing the network over 1% per day, it will still take a decade or two to conquer the Earth. We are going to start with small scale prototypes (neighborhoods), then try cities. I think the first demonstration networks will be working this year.
How will bandwidth be priced in terms of coin hours and who determines this rate?
You could have 40 PHDs each do a thesis on this. The short answer is that an auction model has to be used (similar to Google’s Ad Words auction model) and the auction has to be designed in a way so that the bandwidth prices reach a stable equilibrium. There are parts of Skycoin that are completely open source and public, like the blockchain and consensus algorithm and Skywire. There are secrets like the auction model and pricing, that are designed to protect Skycoin from being forked and to prevent competitors from copying our work. We estimate that if a competitor was to start today, with 2 million dollars a year in R&D, that it would take them a minimum of eight years to develop a working bandwidth pricing model. And from experience in auction models for advertising networks, 80% of the competitors will fail to develop a working model at all. A working, fair, decentralized bandwidth pricing model that was competitive with what we have would take even longer. There are very few people (less than 4) on Earth who have the experience in mathematics, economics, game theory and cryptographic protocols to design the required auction and pricing models. One of Google’s secrets that allows them to dominate the internet advertising industry, is their auction model for ad pricing. That is what allows Google to pay the content producers the most money for their advertising inventory, while charging the advertising buyers the least. Google’s auction models for pricing AdSense inventory are even more secretive and important than Google’s search algorithm. This is one of the most important and secretive parts of Google’s business. Even companies like Facebook, with billion dollar war chests have been unable to replicate to close the algorithm gap in this area. Expertise in these algorithms and their auction and pricing models is one of the reasons that Google has been able to extract advertising premiums over Facebook. Even if a competitor raises a billion dollars and hires all the PHDs in the field and they had ten years to do research, I doubt they would be able to develop anything close to what we have now. The history of bandwidth markets is very interesting and Enron tried to do a trading desk for bandwidth and bandwidth futures and it completely failed. The mathematical stability and predictability of the pricing of bandwidth under adversarial conditions is one of the major problems. For instance, one of our “competitors” suggests that people will be paid coins if someone accesses their content. So why don’t you just put a website and then have 2000 bots go to it, to get free coins! How are they going to stop that. Or if they are pricing bandwidth, if the price is fixed and the price is too low, then people will not build capacity and bandwidth will be insufficient and the network will be slow. Or if the price is variable and adjusts with demands, what will stop someone from buying up the capacity for a link (“Cornering the Market”) to drive the price up 50x on links they control and extort money out of the other people on the network with a fake bandwidth shortage? The pricing algorithm has to be stable under adversarial conditions. It is a very difficult problem, harder than even consensus algorithm research. Even if a competitor had unlimited funding and unlimited time, it is unlikely that they would find a superior solution to what we have and that alone nearly guarantees that we are going to win this market. It gets even more difficult if you need price stability and you admit any type of bandwidth futures, that allow speculation on future prices. This is a kind of problem like Bitcoin consensus algorithm that can only be solved by an act of genius. We have a lot of experience in this area. It is hyper specialized and a very difficult area and is one of the areas that will give Skycoin a strong sustainable advantage.
Will there be a DNS for Skywire to register .sky domains?
Of course. We will definitely add some kind of DNS and name system eventually. Remembering and typing public keys is too difficult. We want to make it as easy as possible. We want people to be able to register aliases (like screen names) so that people can send coins to aliases instead of having to type in addresses every time. This will let people send 5 Skycoin to “@bobcat” instead of sending coins to “23TeSPPJVZ9HvXh6iYiKAaLNQroKg8yCdja”. This will be a revolution in usability.
When operating a Skyminer, will people in my surrounding area see it as a Wifi option on their devices?
You can configure it to expose a wifi access point. It depends on what you are trying to do.
While I plan on running a DIY miner regardless of the payout, will one of the first 6000 DIY miners built to the same spec as the official miner receive a worthwhile payout in Sky coin? What is the requirement for a DIY miner to get whitelisted (and earning Skycoin) on the Skywire testnet?
The reason we have white-listing on the testnet, is to stop too many nodes from joining the network at once. The network can only support so many nodes until we upgrade certain infrastructure (like the messaging/inter-process communication standard). Eventually, all DIY miners will be whitelisted, but there will probably be a queue.
The Sky team is developing antennas by their own instead of buying or using technology already developed, why is such an effort necessary?
You can of course, buy any commercial antenna or wifi system and use it for Skywire. We are developing our own custom antennas, to push performance limitations and experiment with advanced technology, like FPGAs (Field Programmable Arrays) and SDR (Software Defined Radio). Existing wifi has a huge latency (15 milliseconds per hop). We need to make several modification to get that down to 0.5 millisecond per hop. We have several custom PCB boards in development. We have a few secret hardware projects that will be announced when they are ready. For instance, the Skywire Miner was in development for two years before we publicly announced it. Some of our next hardware projects are focused on payments at the point of sale and improving usability, not just the meshnet.
So back in January Steve was asked a question in the skywire group: "Steve, I am not a tech savage, so how can I understand better the safety running a miner if people on the network do DeepWeb stuff? So i will receive and redirect data packets with crazy things and also there is around 128 GB of storage on my miner. How can i have peace of mind of that?" He replied with "If you don’t run an exit node to the open internet it won’t matter you can run relay nodes if you’re worried about it, or proxy specific content." This seems to goes counter to what you mentioned regarding end-to-end encryption with Skywire. Will some people only be relay nodes and some will be exit nodes as well?
I think the question is wrong. You only store content for public keys that you explicitly subscribe to. This means if you do not like particular content or do not want it on your hardware, then you can just blacklist those public keys or don’t subscribe to them. Data never goes on your machine unless you requested it. If you are holding data for a third party such as forwarding packets, it’s always going to be encrypted, so will look like random noise. There will never be anything in the data that causes legal liability. It will look the same as the output of a random number generator.
If using the skyminer, how much bandwidth will be necessary to run it at its best? And what about the router? It's true it has only 100mbits output? Is a 1gigbits connection necessary to reach toprates?
Hold on!!!! Let us get the software and test net running first, lol. We will know once we know what works for the testnet.
What will the price be for future Skynodes (formerly called Skyminers)?
We are working on ways of reducing the cost, such as by buying our own factory, doing custom PCB boards and using different materials. The cheapest Skywire Miner node will be about $30 for a single node miner. We will have a very cheap personal Skywire “hardware VPN” node also. The miners we are shipping now are for powering the network backbone and have 8 computers and are about $800 each. We sold people the miners for 1 BTC each so they can support development, but gave them a Skycoin bonus equal to about 1 BTC worth of Skycoin. Then that money, went to fund the cost for developing the newer hardware.
Como ser anónimo na Internet – [TUTORIAL COMPLETO]
Antes de mais, não sou um especialista, apenas alguém interessado em segurança e comunicação e este tutorial é apenas direccionado à educação :D
1) HTTPS ou TOR?
Ao navegarmos a Internet convencional ou a “surface web” usamos protocolos. Tudo começou com o HTTP (HyperText Transfer Protocol), foi um dos primeiros protocolos quando tentamos aceder a um site mas é bastante fácil para um “hacker” ver o que fazemos e por onde navegamos isto porque não há qualquer tipo de encriptação entre o servidor web e a vossa máquina ou seja, basta alguém estar estar na mesma rede do que vocês, por exemplo a mesma rede wifi, e executar um MITM (man in the midle atack). Onde o hacker redireciona o tráfego da máquina alvo para o seu servidor e ele literalmente lê os pacotes de dados (informação trocada ou seja, passwords, utilizadores, etc) com um simples “sniff” no wireshark (programa que nos permite ver pacotes de dados (TPC, UDP, etc)). Forma bastante eficaz de roubar informações a alguém em servidores desprotegidos. Felizmente e a nosso favor a maioria dos sites hoje em dia usa HTTPS (HTTP + SSL), muitas pessoas convencionam o “S” no final do HTTPS como “secure”, daí o cadeado verde que vemos quando acedemos a esses websites. O processo (SSL) começa quando nos tentamos conectar a um site e ele manda-nos uma cópia do seu certificado SSL (Chave pública), o navegador verifica se o certificado está expirado, em vigor, valido, etc (uma grande treta de acreditação). Se o navegador confiar no certificado, ele cria e envia de volta uma chave de sessão simétrica utilizando a chave pública do servidor. O servidor da decrypt da chave de sessão simétrica usando a sua chave privada e envia de volta uma confirmação criptografada com a chave de sessão para iniciar a sessão segura e agora o servidor e o navegador comunicam com, supostamente, segurança. São assim realizados os primeiros momentos de conexão quando acedemos a um website com HTTPS. P.S: Pensem em chaves publica como algo que transforma x em alguma coisa que só pode ser aberto com a chave privada, y. Mais sobre isso a frente.
1.2) Se HTTPS é assim tão seguro, porque usar tor?
Bom, mesmo com esse tipo de segurança há várias formas de ver ou atacar alguém. Sempre podemos fazer phishing, ainda usar MITM (fazermo-nos passar por o servidor verdadeiro, é difícil AF mas possível) entre muitas outras coisas.. Com o Tor deixamos de ter esses problemas. Mais ou menos.
1.3) Mas o que é Tor?
Tor é uma comunidade, uma rede de computadores muitas vezes referida como Dark Web ou Deep Web. A rede Tor dá-nos um nível de segurança com 128-bit AES (Advanced Encryption Standard) end-to-end (De computadores para computadores, não da nossa máquina até ao website). No final das contas é uma rede que sobrepõe “IP’S” em várias camadas e deve ser tratada como tal. O melhor é usar HTTPS e Onions (Tor), HTTPS protege os nossos dados a nível de navegadores (nós)<=>(WEBSITE) e a rede Onion reforça o anonimato com “loops” pela internet de modo a escondemos a nossa identidade (IP). Mas esse nível de segurança depende do próprio website/servidor com que estamos a tentar comunicar. Para os nerds que desconheciam esta tecnologia, aqui têm um “Let’s Encrypt” para onions (here) A rede tor funciona a partir de nodes, qualquer um pode fazer um relay, node de saida, etc. Uma autentica rede de computadores que comunicam entre si anonimamente.
1.3.1) Um aparte do funcionamento dos nodes…
A comunicação do vosso computador para a internet depende do node de entrada onde basicamente o vosso computador entra na rede tor. Esse node de entrada comunica convosco e sabe o vosso endereço IP.
Esse node de entrada em seguida passa a vossa ligação para um relay. O relay comunica com o node de entrada e outro relay (pode haver vários) ou um node de saída mas não conhece o vosso IP
E finalmente a vossa ligação chega ao node de saída onde o vosso pedido inicial é desincriptado e mandado pela Internet. O node de saída não conhece o vosso IP, apenas o IP do relay anterior.
Utilizando este modelo de 3 ou mais nodes fica mais difícil, mas não impossível de correlacionar o vosso pedido inicial com o vosso IP original. Também queria frisar que a maior parte destes nodes são universidades (fun fact) O problema vem quando escrevemos “plain text” num site que acessamos via Tor, imaginemos que o meu exit node é o FBI ou a NSA. Se tivermos introduzido dados sensíveis apenas rezem que quem estiver a manteoperacional o exit node não tenha poder computacional suficiente para desencriptar a vossa ligação.
1.4) Let’s get REAL
Depois disto não parece nada seguro usar tor né? O bom é que é praticamente e impossível quebrar 128-bit AES. Toda a rede de bitcoin (hash rate atual é de 60M) demoraria 2.158 x 10^12 anos para quebrar 1 só chave. E para além do mais, sempre podemos configurar os nossos nodes, mais aqui. Apenas não coloquem nada que não gostariam que se tornasse publico pois a segurança nunca é garantida! O que é (praticamente) garantido é o anonimato com o tor :)(Eu diria até que o vosso anonimato é garantido, todos os websites na deepweb que foram fechados até o dia de hoje por exemplo, não teve nada a ver com uma falha na rede tor mas sim foi um descuido dos administradores) E para comunicação na web (chat) usem sempre PGP (Pretty Good Privacy), vamos falar mais a frente.
2) Que sistema operativo usar / Como Operar
Pretty bit topic here..
2.1) Sistemas Operativos
Querem anonimato? Usem um sistema operativo ao vivo (Live Operating System / Live CD). É um sistema operativo contido num dispositivo de armazenamento móvel, podem usar em qualquer lado com um computador (motherboard não desbloqueada) não deixando qualquer rasto no pc da sua existência (kinda, mais a frente).Caso não queiram ser tão hardcores sempre podem usar linux muito bom também, updates constantes da comunidade ;)Para o típico utilizador windows.. sabiam que o windows envia tudo o que vocês escrevem e falam para a Microsoft? Aqui têm tools que removem a telemetria and stuff (here) Se são uns completos noobs e nunca instalaram nenhum OS (operating system) podem usar uma coisa chamada Virtual Box que emula um sistema operativo dentro de outro. Pesquisem.
P.S: No que toca à Apple não tenho experiência portanto, não comento.P.S2: Dêm uma vista de olhos no “qubes”, sistema operativo hardcore para segurança.
2.2) PGP, Como Operar & Related
2.2.1) Mini Introdução
Temos de assumir sempre o pior, qualquer agência de inteligência ou governamental interceptou e desencriptou os nossos dados. O que eles podem usar contra nós? Temos sempre de agiter o cuidado de nunca compartilhar dados pessoais, NUNCA. Ter uma boa password sem nada que nos identifique (Tenho uma boa password?) e diferentes passwords e entidades para cada serviço/website que usemos. Lembrem-se, basta “deslizar-mos” uma vez e somos comprometidos. Caso usem o mesmo utilizadopass qualquer organização/pessoa com intenções pode “ligar os pontos” e identificar-te.
2.2.1) PGP (Pretty Good Privacy)
Outro passo que devem tomar é comunicar apenas usando PGP. Lembram-se das chaves publico e privadas? Vou salientar novamente esse tópico.Tomem em conta que nem sempre é possível comunicar com PGP, quando estamos a preencher informação num website ou wtv essa informação pode estar comprometida. Side Note: Há uns open sorce code para usar o Proton Mail com PGP com alguma facilidade, pesquisem nerds.
O processo PGP:
Criam uma chave privada e uma chave pública
A chave pública é aquela que vocês mandam para as pessoas poderem encriptar mensagens/ficheiros/etc.
A vossa chave privada é guardada por vocês, é a única coisa que pode desencriptar os ficheiros encriptados pela chave pública.
A pessoa com quem comunicarem tem de fazer exactamente o mesmo processo e vocês tem de usar a chave publica delas para lhes enviar mensagens.
GUARDEM BEM A VOSSA CHAVE PRIVADA, GUARDEM NUM LOCAL OFF-GRID, fisicamente escondida. Caso comprometida, fudeu. E já agora, se a perderem não há nenhuma forma de a recuperar. No tails a área onde podem mexer com o PGP fica no canto superior direito, uma que parece uma prancheta, vão a “manage keys”. Por exemplo, uma das razões que o Silk Road falhou foi que Ross (um dos administradores) nem sempre comunicava através de encriptação PGP e depois de ser apanhado (meteu informações pessoais na net no inicio da sua jornada) as autoridades tiveram acesso a tudo o que não estava encriptado. Sugiro sempre que guardem as suas chaves privadas num cartão SD ou melhor num microSD para que se um dia forem apanhados e alguém for-vos bater à porta podem simplesmente parti lo e os vossos dados ficam seguros x)
2.2.2) Tails e resíduos
(assumindo que têm o tails a funfar..) Tails é um excelente sistema operativo para privacidade, quando ligado e “bootado” no PC ele cria um drive virtual e quando é fechado tal é apagado, mas não permanentemente. Como deve ser conhecimento geral, armazenamento na memória de um computador (no seu disco rígido) funciona a base de 0’s e 1’s. Vamos supor que crio uma pasta chamada “teste”. O disco rígido será desempenhado de designar os respetivos 0’s e 1’s a uma secção do disco e saber onde está tal secção. Temos 2 dados importantes aqui, os dados da pasta “teste” (0’s e 1’s) e a sua localização na respectiva secção do disco, chamam-se “pointers”. Pointers apontam o local do disco onde estão armazenados os dados (0’s e 1’s).Quando apagamos algo (tradicionalmente) apenas apagamos os pointers e os 0’s e 1’s anteriormente designados à pasta teste estarão agora labled como livres, esperando serem rescritos por novos 0’s e 1’s de novos dados. Espero ter sido claro. Portanto, alguém com habilidades pode pesquisar no disco 0 e 1’s designados como “espaço livre” que, organizados “façam sentido” e recuperar os nossos dados privados. Temos 2 opções:
Dar Shread nos ficheiros (Rescrever aleatoriamente 0’s e 1’s “livres”)
Encriptar o disco rígido
2.2.3) Encriptação do disco inteiro & destruição segura de ficheiros & RAM
No que toca a encriptação do disco tails tem uma funcionalidade incorporada chamada FDE (Full Disk Encryption) ou seja, formata-vos a pen (ou o quer que seja que estão a usar) e rescreve-a com o seu conteúdo encriptado sendo apenas possível ganhar-lhe acesso com uma palavra-passe. E como sempre, guardem a password num local seguro ou memorizem-na. Tutorial de como encriptar o disco (here) E no que toca a destruição segura dos ficheiros há vários programas para o fazer, apenas recomendo que o faças no mínimo 3x (para garantir aleatoriedade). Duck it. Mesmo com o disco encriptado e os dados limpados ainda podemos extrair-te informações pela tua RAM📷 Chamam-se de “Cold Boot” esses tipos de ataques.
Primeiro, RAM (random acess memory), quesamerda?
RAM é o local onde o computador armazena dados que apenas são necessários temporariamente e isso acontece milhões de vezes por segundo. Pensem na RAM como uma memoria onde pode ser escrita e rescrita os 0’s e 1’s extremamente rapido. Imaginemos que estão a trabalhar num documento de texto, enquanto trabalham tal está a ser guardado na RAM (armazenamento de curto prazo) até que clicam em salvar e o documento é armazenado no disco rígido em si (armazenamento de longo prazo). Nesse período de tempo os dados são armazenados na RAM sem qualquer tipo de encriptação. Quando desligamos o computador normalmente ele passa por um ciclo onde limpa os dados armazenados na RAM mas se ele perder energia abruptamente os dados ficam “leaked” na RAM e é onde são realizados os Cold Boot Atacks. A única medida que podemos implementar contra este tipos de ataques é usar RAM DDR3 (isto porque ela necessita de eletricidade para manter dados, passado x tempo os dados são apagado) e desligar o PC normalmente, sempre.
Abram uma nova tab (janela) no navegador e escrevam “about:config” e cliquem no botão “I’ll be careful, I promise.” (apenas versões mais antigas, se não tiverem botão, ignorem)
(se usam tails, cada vez que o iniciam poderão de ter de fazer isto)
2.2.4) Dados EXIF
Tiramos tantas fotografias com os nossos telemóveis né? Sabiam que provavelmente a vossa localização está incorporada nelas? Quase todos os formatos de fotos podem ter as cordeadas incorporadas menos o formato .PNG portanto é imperativo para um criador de um website apenas permitir formatos PNG e também para nos porque a nossa informação pode dar “leak” por um erro tão simples como este. Felizmente o Tails tem uma solução, basta irmos a Applications -> Accessories -> Metadata Anonymisation Toolkit, mais info –> (here)
2.2.5) VPN + TOR = PERFECTION?
Bem, não. VPN’s não são de confiança. A famosa “HideMyAss” que supostamente tinha uma carrada de implementações de segurança que nem eles próprios conseguiriam ver o que o utilizador fazia abriu a boca quando questionada pelo governo da Inglaterra sobre o caso LulzSec.Mas se tentarem a vossa sorte escolham uma que no mínimo tenha 128 bits ou até mesmo 256 bits de encriptação. Se querem ainda mais segurança do que já têm, comprem umas raspberryPi, disfarçam-nas e coloquem-nas em um sitio que tenha uma rede Wifi Publica escondidas e com eletricidade, façam uns servidores OpenVPN, uns proxies da treta e GG (Como criar uma rede tor mas caseira). Fiz um tutorial de como fazer uma VPN numa raspberry, depois é só fazer uns loops. P.S: DNSQueries, não confiem na vossa rede.
2.2.6) Cuidado com downloads
Por vezes numa comunidade da deepweb recebemos PM (private messages) que nos dizem que a nova atualização do tor tem uma falha de segurança e aqui está o link X para dar patch. Treta, nunca confiem e façam sempre o download do website oficial (cuidado com o phishing) mas podemos sempre verificar a autenticidade dos nossos downloads. Recomendo o uso do GnuPG. Pesquisem, muito importante! Voltamos a usar o nosso amigo PGP ;) P.S: Não só downloads, também podem assinar mensagens encriptadas (quase como encriptado 2x)
2.2.7) Simples e eficaz, adeus monitorização da treta
Podem-nos identificar de várias maneiras, uma delas é pelos nossos padrões habituais que podem ser usados contra nós em tribunal. Uma forma fácil de acabar com isso é desabilitar “mostrar o meu status online”, muito comum em fóruns e comunidades.
2.2.8) Usem bridges!
Mesmo com esta segurança quando ligados ao tor o vosso ISP (Internet Service Provider) pode ver que vocês estão a usar o Tor, para tal sempre podemos usar bridges. Lista de bridges (here) captcha é hard mesmo.. (ataques de correlação) Depois de entrarem vão ter acesso a uma lista de bridges que são publicamente disponiveis pelo Tor, talvez não seja a melhor opção mas sempre tens a opção de mandar diretamente um email para [[email protected]](mailto:[email protected]) com o body da mensagem sendo “get bridges”, infelizmente só funciona para Gmail e Yahoo (anti bots) Para usa-las no boot do tails aparecem 2 opções: Live e Live (Fail Safe), neste menu cliquem em Tab , Espaço e escrevam “bridge” e depois enter. Modo bridge ativado. Ao entrarem no tails basta adicionar as vossas bridges numa tab que vos vai aparecer neste formato-> IP:PORTA e gg. Visto que é muito menos provável que o vosso ISP conheça estas ligações. Também podem especificar o pais assim: XXX.XXX.XXX.XXX – COUNTRY: X De qualquer das formas bridges é um assunto complexo, do your homework. Coisas bonitas para vocês (here)
3) Governo e polícia
3.1) Os seus limites
Bom, não têm, pelo menos os americanos (casos mais conhecidos). Eles chegaram ao ponto de ter uma conta no silk road como vendedores onde seriam vendidas fake ID’S (durante 7 anos), após esse período começaram de apreensões. E no serviço postal dos US, qualquer encomenda “ilegal” não eram apreendida mas sim colocavam-lhe um tracker. Tenham sempre em mente que se eles vos querem apanhar mesmo, eles farã tudo no seu alcance para vos capturar. Tenham sempre em mente que se vocês estão a fazer qualquer tipo de actividade considerada ilegal têm sempre de ter em conta o pior cenário possível. Vocês até podem ter uns PC’s, uns servidores e algumas skills mas não é nada comparado com o poder deles. Lembrem-se, basta escorregarem uma vez e acabou, sejam prudentes.
3.2) O que fazer quando se é apanhado
Errar é humano. Provavelmente vamos todos cometer um erro e se o governo achar que somos um peixe suficientemente grande ele vem a trás de nós. É sempre melhor prevenir do que remediar, temos de ter já um advogado pago 50k + extra (caso sejam ilegais, mesmo.) isto porque o governo pode congelar-nos as contas/apreender o dinheiro. Sabiam que o silencio é um direito? Mantenham a boca fechada. Eles vão tentar usar todas as táticas para nos fazer admitir que somos culpados dos crimes de que somos acusados. Provavelmente a primeira coisa que eles vos vão dizer é que nos querem ajudar e estão a trás do maior peixe do cardume, ignorem, treta. Eles vão dizer “então não queres cooperar? Estava a tentar ajudar-te mas agora só vais dar problemas” ou “Tens alguma noção dos crimes de que és acusado?”. Mais uma vez, mantenham-se calados e continem a pedir por um advogado. Nunca falem sem o vosso advogado presente e nunca façam nada que não seja exigido legalmente. Vocês têm o DIREITO de estar calados. Não discutam com os policias sobre se eles têm ou não alguma coisa contra ti, sê chill nesse assunto. Age assustado, ansioso e confuso. Como se não soubesses o que se passa e apenas queres o teu advogado. Diz aos policias: “Vocês estão-me a assustar, apenas quero o meu advogado”… como eu amo engenharia social. Com o vosso advogado é o basico, sejam honestos com ele e trabalhem como uma equipa. Privilegio Cliente-advogado.
4) Cool Stuff
TorChat funciona da mesma forma que o tor funciona com todas a features que todos gostamos, cria links .onion da mesma forma que o tor mas usa-o para identificar um ID de uma pessoa em particular sendo que esse ID pode comunicar com outros ID.
P.S: Não recomendo, ideia bonita mas não sabemos o nível de anonimato ou as vulnerabilidades que tal implica visto que funciona da mesma forma do que se como tivéssemos criado um HiddenService (um site tor) no nosso PC. Isso pode levar a problemas sérios. Fica à vossa mercê, de qualquer das formas a sua comunicação eu<=>parceiro teria o mesmo nível de segurança do que o tor.
News.Bitcoin.com took a look at how Televend operates and the program simply works like any bot hosted on Telegram. Televend’s bot gives a list of commands, products, order records, vendor ... was successfully added to your cart. Home; Buy proxies; Extra features; Help; Contact; Login ... The Bitcoin.com mining pool has the lowest share reject rate (0.15%) we've ever seen. Other pools have over 0.30% rejected shares. Furthermore, the Bitcoin.com pool has a super responsive and reliable support team. Während ein einzelner Bitcoin Tausende von Dollar wert ist, liegt der Preis eines Monero bei rund 100 US-Dollar, was klein genug ist, um keinen Verdacht zu erregen. Gleichzeitig wird erwartet, dass der Wert dieser digitalen Währung in absehbarer Zeit in die Höhe schnellen wird, was für Hacker erhebliche finanzielle Gewinne bedeuten kann. Strong claims need strong proof, so when the founders of NeuroMesh described their bitcoin-based product as an “unhackable botnet”, there were a lot of questions to be asked.