Bitcoin.Directory - High Quality Bitcoin Websites

cant launch bitcoin-qt(linux)

bitcoin-qt under linux(arch) used to run without a problem, one day have a problem with kvm, computer freezed, rebooted and everyting fine, except for bitcoin-qt.
didnt worked anymore after that, even reinstalled all the packages(without re-installing), compiled and installed bitcoint-qt 0.17 and not worked.
whats my problem?, launch bitcoin-qt, but nothing happens, launch from cli and just:
[[email protected] ~]$ bitcoin-qt
and nothing, task manager show bitcoin-qt but dont launch, dont take a lot of ram, nothing, just stay there, until press ctrl+c to cancel. Rename .bitcoin data dir(to avoid donwload blockchain again) and force a new start, and nothing.
any ideas?
submitted by relgueta to Bitcoin [link] [comments]

Reddcoin (RDD) 02/20 Progress Report - Core Wallet v3.1 Evolution & PoSV v2 - Commits & More Commits to v3.1! (Bitcoin Core 0.10, MacOS Catalina, QT Enhanced Speed and Security and more!)

Reddcoin (RDD) Core Dev Team Informal Progress Report, Feb 2020 - As any blockchain or software expert will confirm, the hardest part of making successful progress in blockchain and crypto is invisible to most users. As developers, the Reddcoin Core team relies on internal experts like John Nash, contributors offering their own code improvements to our repos (which we would love to see more of!) and especially upstream commits from experts working on open source projects like Bitcoin itself. We'd like tothank each and everyone who's hard work has contributed to this progress.
As part of Reddcoin's evolution, and in order to include required security fixes, speed improvements that are long overdue, the team has up to this point incorporated the following code commits since our last v3.0.1 public release. In attempting to solve the relatively minor font display issue with MacOS Catalina, we uncovered a complicated interweaving of updates between Reddcoin Core, QT software, MacOS SDK, Bitcoin Core and related libraries and dependencies that mandated we take a holistic approach to both solve the Catalina display problem, but in doing so, prepare a more streamlined overall build and test system, allowing the team to roll out more frequent and more secure updates in the future. And also to include some badly needed fixes in the current version of Core, which we have tentatively labeled Reddcoin Core Wallet v3.1.
Note: As indicated below, v3.1 is NOT YET AVAILABLE FOR DOWNLOAD BY PUBLIC. We wil advise when it is.
The new v3.1 version should be ready for internal QA and build testing by the end of this week, with luck, and will be turned over to the public shortly thereafter once testing has proven no unexpected issues have been introduced. We know the delay has been a bit extended for our ReddHead MacOS Catalina stakers, and we hope to have them all aboard soon. We have moved with all possible speed while attempting to incorproate all the required work, testing, and ensuring security and safety for our ReddHeads.
Which leads us to: PoSV v2 activation and the supermajority on Mainnet at the time of this writing has reached 5625/9000 blocks or 62.5%. We have progressed quite well and without any reported user issues since release, but we need all of the community to participate! This activation, much like the funding mechanisms currently being debated by BCH and others, and employed by DASH, will mean not only a catalyst for Reddcoin but ensure it's future by providing funding for the dev team. As a personal plea from the team, please help us support the PoSV v2 activation by staking your RDD, no matter how large or small your amount of stake.
Every block and every RDD counts, and if you don't know how, we'll teach you! Live chat is fun as well as providing tech support you can trust from devs and community ReddHead members. Join us today in staking and online and collect some RDD "rain" from users and devs alike!
If you're holding Reddcoin and not staking, or you haven't upgraded your v2.x wallet to v3.0.1 (current release), we need you to help achieve consensus and activate PoSV v2! For details, see the pinned message here or our website or medium channel. Upgrade is simple and takes moments; if you're nervous or unsure, we're here to help live in Telegram or Discord, as well as other chat programs. See our website for links.
Look for more updates shortly as our long-anticipated Reddcoin Payment Gateway and Merchant Services API come online with point-of-sale support, as we announce the cross-crypto-project Aussie firefighter fundraiser program, as well as a comprehensive update to our development roadmap and more.
Work has restarted on ReddID and multiple initiatives are underway to begin educating and sharing information about ReddID, what it is, and how to use it, as we approach a releasable ReddID product. We enthusiastically encourage anyone interested in working to bring these efforts to life, whether writers, UX/UI experts, big data analysts, graphic artists, coders, front-end, back-end, AI, DevOps, the Reddcoin Core dev team is growing, and there's more opportunity and work than ever!
Bring your talents to a community and dev team that truly appreciates it, and share the Reddcoin Love!
And now, lots of commits. As v3.1 is not yet quite ready for public release, these commits have not been pushed publicly, but in the interests of sharing progress transparently, and including our ReddHead community in the process, see below for mind-numbing technical detail of work accomplished.
e5c143404 - - 2014-08-07 - Ross Nicoll - Changed LevelDB cursors to use scoped pointers to ensure destruction when going out of scope. *99a7dba2e - - 2014-08-15 - Cory Fields - tests: fix test-runner for osx. Closes ##4708 *8c667f1be - - 2014-08-15 - Cory Fields - build: add funcs.mk to the list of meta-depends *bcc1b2b2f - - 2014-08-15 - Cory Fields - depends: fix shasum on osx < 10.9 *54dac77d1 - - 2014-08-18 - Cory Fields - build: add option for reducing exports (v2) *6fb9611c0 - - 2014-08-16 - randy-waterhouse - build : fix CPPFLAGS for libbitcoin_cli *9958cc923 - - 2014-08-16 - randy-waterhouse - build: Add --with-utils (bitcoin-cli and bitcoin-tx, default=yes). Help string consistency tweaks. Target sanity check fix. *342aa98ea - - 2014-08-07 - Cory Fields - build: fix automake warnings about the use of INCLUDES *46db8ad51 - - 2020-02-18 - John Nash - build: add build.h to the correct target *a24de1e4c - - 2014-11-26 - Pavel Janík - Use complete path to include bitcoin-config.h. *fd8f506e5 - - 2014-08-04 - Wladimir J. van der Laan - qt: Demote ReportInvalidCertificate message to qDebug *f12aaf3b1 - - 2020-02-17 - John Nash - build: QT5 compiled with fPIC require fPIC to be enabled, fPIE is not enough *7a991b37e - - 2014-08-12 - Wladimir J. van der Laan - build: check for sys/prctl.h in the proper way *2cfa63a48 - - 2014-08-11 - Wladimir J. van der Laan - build: Add mention of --disable-wallet to bdb48 error messages *9aa580f04 - - 2014-07-23 - Cory Fields - depends: add shared dependency builder *8853d4645 - - 2014-08-08 - Philip Kaufmann - [Qt] move SubstituteFonts() above ToolTipToRichTextFilter *0c98e21db - - 2014-08-02 - Ross Nicoll - URLs containing a / after the address no longer cause parsing errors. *7baa77731 - - 2014-08-07 - ntrgn - Fixes ignored qt 4.8 codecs path on windows when configuring with --with-qt-libdir *2a3df4617 - - 2014-08-06 - Cory Fields - qt: fix unicode character display on osx when building with 10.7 sdk *71a36303d - - 2014-08-04 - Cory Fields - build: fix race in 'make deploy' for windows *077295498 - - 2014-08-04 - Cory Fields - build: Fix 'make deploy' when binaries haven't been built yet *ffdcc4d7d - - 2014-08-04 - Cory Fields - build: hook up qt translations for static osx packaging *25a7e9c90 - - 2014-08-04 - Cory Fields - build: add --with-qt-translationdir to configure for use with static qt *11cfcef37 - - 2014-08-04 - Cory Fields - build: teach macdeploy the -translations-dir argument, for use with static qt *4c4ae35b1 - - 2014-07-23 - Cory Fields - build: Find the proper xcb/pcre dependencies *942e77dd2 - - 2014-08-06 - Cory Fields - build: silence mingw fpic warning spew *e73e2b834 - - 2014-06-27 - Huang Le - Use async name resolving to improve net thread responsiveness *c88e76e8e - - 2014-07-23 - Cory Fields - build: don't let libtool insert rpath into binaries *18e14e11c - - 2014-08-05 - ntrgn - build: Fix windows configure when using --with-qt-libdir *bb92d65c4 - - 2014-07-31 - Cory Fields - test: don't let the port number exceed the legal range *62b95290a - - 2014-06-18 - Cory Fields - test: redirect comparison tool output to stdout *cefe447e9 - - 2014-07-22 - Cory Fields - gitian: remove unneeded option after last commit *9347402ca - - 2014-07-21 - Cory Fields - build: fix broken boost chrono check on some platforms *c9ed039cf - - 2014-06-03 - Cory Fields - build: fix whitespace in pkg-config variable *3bcc5ad37 - - 2014-06-03 - Cory Fields - build: allow linux and osx to build against static qt5 *01a44ba90 - - 2014-07-17 - Cory Fields - build: silence false errors during make clean *d1fbf7ba2 - - 2014-07-08 - Cory Fields - build: fix win32 static linking after libtool merge *005ae2fa4 - - 2014-07-08 - Cory Fields - build: re-add AM_LDFLAGS where it's overridden *37043076d - - 2014-07-02 - Wladimir J. van der Laan - Fix the Qt5 build after d95ba75 *f3b4bbf40 - - 2014-07-01 - Wladimir J. van der Laan - qt: Change serious messages from qDebug to qWarning *f4706f753 - - 2014-07-01 - Wladimir J. van der Laan - qt: Log messages with type>QtDebugMsg as non-debug *98e85fa1f - - 2014-06-06 - Pieter Wuille - libsecp256k1 integration *5f1f2e226 - - 2020-02-17 - John Nash - Merge branch 'switch_verification_code' into Build *1f30416c9 - - 2014-02-07 - Pieter Wuille - Also switch the (unused) verification code to low-s instead of even-s. *1c093d55e - - 2014-06-06 - Cory Fields - secp256k1: Add build-side changes for libsecp256k1 *7f3114484 - - 2014-06-06 - Cory Fields - secp256k1: add libtool as a dependency *2531f9299 - - 2020-02-17 - John Nash - Move network-time related functions to timedata.cpp/h *d003e4c57 - - 2020-02-16 - John Nash - build: fix build weirdness after 54372482. *7035f5034 - - 2020-02-16 - John Nash - Add ::OUTPUT_SIZE *2a864c4d8 - - 2014-06-09 - Cory Fields - crypto: create a separate lib for crypto functions *03a4e4c70 - - 2014-06-09 - Cory Fields - crypto: explicitly check for byte read/write functions *a78462a2a - - 2014-06-09 - Cory Fields - build: move bitcoin-config.h to its own directory *a885721c4 - - 2014-05-31 - Pieter Wuille - Extend and move all crypto tests to crypto_tests.cpp *5f308f528 - - 2014-05-03 - Pieter Wuille - Move {Read,Write}{LE,BE}{32,64} to common.h and use builtins if possible *0161cc426 - - 2014-05-01 - Pieter Wuille - Add built-in RIPEMD-160 implementation *deefc27c0 - - 2014-04-28 - Pieter Wuille - Move crypto implementations to src/crypto/ *d6a12182b - - 2014-04-28 - Pieter Wuille - Add built-in SHA-1 implementation. *c3c4f9f2e - - 2014-04-27 - Pieter Wuille - Switch miner.cpp to use sha2 instead of OpenSSL. *b6ed6def9 - - 2014-04-28 - Pieter Wuille - Remove getwork() RPC call *0a09c1c60 - - 2014-04-26 - Pieter Wuille - Switch script.cpp and hash.cpp to use sha2.cpp instead of OpenSSL. *8ed091692 - - 2014-04-20 - Pieter Wuille - Add a built-in SHA256/SHA512 implementation. *0c4c99b3f - - 2014-06-21 - Philip Kaufmann - small cleanup in src/compat .h and .cpp *ab1369745 - - 2014-06-13 - Cory Fields - sanity: hook up sanity checks *f598c67e0 - - 2014-06-13 - Cory Fields - sanity: add libc/stdlib sanity checks *b241b3e13 - - 2014-06-13 - Cory Fields - sanity: autoconf check for sys/select.h *cad980a4f - - 2019-07-03 - John Nash - build: Add a top-level forwarding target for src/ objects *f4533ee1c - - 2019-07-03 - John Nash - build: qt: split locale resources. Fixes non-deterministic distcheck *4a0e46e76 - - 2019-06-29 - John Nash - build: fix version dependency *2f61699d9 - - 2019-06-29 - John Nash - build: quit abusing AMCPPFLAGS *99b60ba49 - - 2019-06-29 - John Nash - build: avoid the use of top and abs_ dir paths *c8f673d5d - - 2019-06-29 - John Nash - build: Tidy up file generation output *5318bce57 - - 2019-06-29 - John Nash - build: nuke Makefile.include from orbit *672a25349 - - 2019-06-29 - John Nash - build: add stub makefiles for easier subdir builds *562b7c5a6 - - 2020-02-08 - John Nash - build: delete old Makefile.am's *066120079 - - 2020-02-08 - John Nash - build: Switch to non-recursive make
Whew! No wonder it's taken the dev team a while! :)
TL;DR: Trying to fix MacOS Catalina font display led to requiring all kinds of work to migrate and evolve the Reddcoin Core software with Apple, Bitcoin and QT components. Lots of work done, v3.1 public release soon. Also other exciting things and ReddID back under active dev effort.
submitted by TechAdept to reddCoin [link] [comments]

Having Trouble with Regtest Running Inside a Docker Container

Hello everyone. First of all, thanks in advance for any help.
I'm running a BTCPay server using BTCPay server docker. If I understand it correctly, it exposes the regtest Bitcoin core through a Tor network.
I followed the instructions on the [BTCPay Server docs to Connect Wasabi to BTCPay Server Full Node. Unfortunately, after following these instructions, the bottom-left corner of Wasabi Wallet still reads "Connecting...".
My logs.txt reveals:
2020-03-29 20:34:51 INFO Program (44) Wasabi GUI started (14879af3-85dd-42aa-9d41-674d87a5dd77). 2020-03-29 20:34:52 INFO Global (164) Config is successfully initialized. 2020-03-29 20:34:52 INFO TransactionStore (28) ConfirmedStore.InitializeAsync finished in 4 milliseconds. 2020-03-29 20:34:52 INFO TransactionStore (28) MempoolStore.InitializeAsync finished in 12 milliseconds. 2020-03-29 20:34:52 INFO Global (401) Fake AddressManager is initialized on the RegTest. 2020-03-29 20:34:52 INFO AllTransactionStore (27) InitializeAsync finished in 16 milliseconds. 2020-03-29 20:34:52 INFO IndexStore (43) InitializeAsync finished in 40 milliseconds. 2020-03-29 20:34:52 INFO BitcoinStore (39) InitializeAsync finished in 43 milliseconds. 2020-03-29 20:34:52 INFO TorProcessManager (249) Starting Tor monitor... 2020-03-29 20:34:52 INFO Global (230) TorProcessManager is initialized. 2020-03-29 20:34:52 INFO HostedServices (49) Started Software Update Checker. 2020-03-29 20:34:52 INFO TorProcessManager (66) Tor is already running. 2020-03-29 20:34:53 ERROR Global (328) System.Net.Internals.SocketExceptionFactory+ExtendedSocketException (61): Connection refused [::ffff:127.0.0.1]:18444 at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw(Exception source) at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult) at NBitcoin.Protocol.Connectors.SocketExtensions.<>c.b__0_0(IAsyncResult iar) --- End of stack trace from previous location where exception was thrown --- at NBitcoin.Extensions.WithCancellation[T](Task`1 task, CancellationToken cancellationToken) at NBitcoin.Protocol.Connectors.DefaultEndpointConnector.ConnectSocket(Socket socket, EndPoint endpoint, NodeConnectionParameters nodeConnectionParameters, CancellationToken cancellationToken) at NBitcoin.Protocol.Node.ConnectAsync(Network network, EndPoint endpoint, NetworkAddress peer, NodeConnectionParameters parameters) at WalletWasabi.Gui.Global.InitializeNoWalletAsync() 2020-03-29 20:34:53 INFO Global (349) Start connecting to nodes... 2020-03-29 20:34:53 INFO Global (373) Start synchronizing filters... 2020-03-29 20:34:53 INFO MainWindow.xaml (74) UiConfig is successfully initialized. 2020-03-29 20:34:57 ERROR PeriodicRunner (72) System.NotSupportedException: Invalid StatusLine: ?. - System.IndexOutOfRangeException: Index was outside the bounds of the array. at WalletWasabi.Http.Models.StatusLine.Parse(String statusLineString) --- End of inner exception stack trace --- at WalletWasabi.Http.Models.StatusLine.Parse(String statusLineString) at System.Net.Http.HttpResponseMessageExtensions.CreateNewAsync(Stream responseStream, HttpMethod requestMethod) at WalletWasabi.TorSocks5.TorHttpClient.SendAsync(HttpRequestMessage request, CancellationToken cancel) at WalletWasabi.TorSocks5.TorHttpClient.SendAsync(HttpMethod method, String relativeUri, HttpContent content, CancellationToken cancel) at TorHttpClientExtensions.SendAndRetryAsync(ITorHttpClient client, HttpMethod method, HttpStatusCode expectedCode, String relativeUri, Int32 retry, HttpContent content, CancellationToken cancel) at WalletWasabi.WebClients.Wasabi.WasabiClient.GetVersionsAsync(CancellationToken cancel) at WalletWasabi.WebClients.Wasabi.WasabiClient.CheckUpdatesAsync(CancellationToken cancel) at WalletWasabi.Services.UpdateChecker.ActionAsync(CancellationToken cancel) at WalletWasabi.Bases.PeriodicRunner.ExecuteAsync(CancellationToken stoppingToken) 2020-03-29 20:35:01 ERROR WasabiSynchronizer (305) System.NotSupportedException: Invalid StatusLine: ?. - System.IndexOutOfRangeException: Index was outside the bounds of the array. at WalletWasabi.Http.Models.StatusLine.Parse(String statusLineString) --- End of inner exception stack trace --- at WalletWasabi.Http.Models.StatusLine.Parse(String statusLineString) at System.Net.Http.HttpResponseMessageExtensions.CreateNewAsync(Stream responseStream, HttpMethod requestMethod) at WalletWasabi.TorSocks5.TorHttpClient.SendAsync(HttpRequestMessage request, CancellationToken cancel) at WalletWasabi.TorSocks5.TorHttpClient.SendAsync(HttpMethod method, String relativeUri, HttpContent content, CancellationToken cancel) at TorHttpClientExtensions.SendAndRetryAsync(ITorHttpClient client, HttpMethod method, HttpStatusCode expectedCode, String relativeUri, Int32 retry, HttpContent content, CancellationToken cancel) at WalletWasabi.WebClients.Wasabi.WasabiClient.GetSynchronizeAsync(uint256 bestKnownBlockHash, Int32 count, Nullable`1 estimateMode, CancellationToken cancel) at System.Threading.Tasks.TaskExtensions.WithAwaitCancellationAsync[T](Task`1 me, CancellationToken cancel, Int32 waitForGracefulTerminationMilliseconds) at WalletWasabi.Services.WasabiSynchronizer.<>c__DisplayClass60_0.<b__0>d.MoveNext()
while my config.json is:
json { "Network": "RegTest", "MainNetBackendUriV3": "http://wasabiukrxmkdgve5kynjztuovbg43uxcbcxn6y2okcrsg7gb6jdmbad.onion/", "TestNetBackendUriV3": "http://testwnp3fugjln6vh5vpj7mvq3lkqqwjj3c2aafyu7laxz42kgwh2rad.onion/", "MainNetFallbackBackendUri": "https://wasabiwallet.io/", "TestNetFallbackBackendUri": "https://wasabiwallet.co/", "RegTestBackendUriV3": "http://oqaqivyaxctrp2gix5id4bbd7mav2xt5n4fzqsnwtrhtsmgjhg7sneqd.onion:8333/", "UseTor": true, "StartLocalBitcoinCoreOnStartup": false, "StopLocalBitcoinCoreOnShutdown": true, "LocalBitcoinCoreDataDir": "/Users/my-name-here/Library/Application Support/Bitcoin", "TorSocks5EndPoint": "127.0.0.1:9050", "MainNetBitcoinP2pEndPoint": "127.0.0.1:8333", "TestNetBitcoinP2pEndPoint": "127.0.0.1:18333", "RegTestBitcoinP2pEndPoint": "127.0.0.1:8333", "MixUntilAnonymitySet": 50, "PrivacyLevelSome": 2, "PrivacyLevelFine": 21, "PrivacyLevelStrong": 50, "DustThreshold": "0.00005" }
The environment in which bitcoind runs is here: https://gist.github.com/AryanJ-NYC/78c770f3e918d06e62301f1ebc6fba31 (I would copy and paste but quite long).
I'm 98% sure the error lies in this line of the log: 2020-03-29 20:34:53 ERROR Global (328) System.Net.Internals.SocketExceptionFactory+ExtendedSocketException (61): Connection refused [::ffff:127.0.0.1]:18444. However, I haven't a clue what port regtest normally runs on.
FWIW, main and testnet connect just fine (both nodes also running on my local machine).
submitted by TheWebDevCoach to WasabiWallet [link] [comments]

I want to run a bitcoin-node but live in a third world country with a connection giving maximum download speeds of 1mbps and that's on a good. Is there any point?

And this is 1 meaga bit per second not even MBs. Upload speeds probably much poorer.
Basically I got intrested in Bitcoin after a course on edX and now I'd like to run a node. But given my current internet connection, is there even a point?
submitted by Bottleneck_ram to Bitcoin [link] [comments]

The anti-Japan sentiment in this sub is pretty toxic and stupid

Since there are gonna be some people saying things like "yOu aMeRiCaNs gO hOmE", I would first like to say I am ethnically and legally a Korean. And to add more on to my background, I have been flying in and out of Korea since I was 1 year old. I lived about 2/3 of my life in Korea and 1/3 in English speaking countries (NA and OCE). So I think I can look at the Korean society and culture from an outsider point of view, but with the knowledge of an insider and vice versa.
Since this summer, I believe, the anti-Japan sentiment has grown for some reasons but mostly from the trade dispute between ROK and JP. I have made exchanges with some users on this sub through comments about this topic and more than often when a user sees that I hold a different worldview they attack me for some reason. I totally understand that people have different values and backgrounds thus agreeing on trivial topics like this is not easy but after seeing this post today, I felt that the anti-Japanese sentiment on this sub is so toxic and stupid. The comments on the post were mostly mockery towards Japan. No single reasoning or contemplation on the article itself, but only comments laughing at other's failure is the state of the anti-Japan sentiment in this sub. The comments on this other post talking about the anti-Korea sentiment in Japan was also pretty painful to read because they never mention the same default emotions Koreans have towards Japan.
The reason why I think all this is toxic and stupid is because I know that 90% of the people in this sub are not even Korean. And almost 70% of the people on this sub have an intermediate or lower reading level in Korean. (/Korea Survey 2019). So inevitably the majority demographic (35 years old and younger) that come in this sub are mostly people from other countries who can't even read Korean properly, but hate Japan??? What has Japan done to you? I'm pretty sure nobody in this sub lived in Korea between 1910-1945. Funnily enough, my grandpa who is almost 90 now has lived through these years and he absolutely loves Japan.
To me, it just seems like a bunch of foreigners learned some stuff about the ROK-JP rivalry from their friends and media or whatever, and pretend to be supportive to the country they are staying in. Which is pretty weird because I thought western philosophy has evolved out of the totalitarian/nationalistic trend that ended in 1945 with Nazi Germany. Why is it that when it comes to ROK vs. JP people lose all individual reasoning and instead choose to become a zealot of nationalistic values that has no benefit in the well-being of either the nation or individual?
I would like to address some serious flaws of the anti-Japan movement.
  1. How do you define boycott-Japan? If you're going to boycott Japanese products how far will you go? If you find that the cabus/train you are riding has Japanese parts in it, which is a very high possibility, will you not take it? I've seen a Korean owning a Japanese themed restaurant in Seoul that was going broke because people won't eat "Japanese". In the same sense, why people who own Japanese cars should be apologetic to everyone else? Why are people bullying these car owners? So, to some people the definition of Japanese is anything that was influenced by Japanese culture. But how can a country can not be influenced by its neighbor country? Especially when Korea was colonized by Japan for 35 years, how can anything cannot be influenced by Japan in Korea? Even the words people use in day to day life there are many Japanese nuances because modern Korean and Hangul were reinvented and became widely available during the colonization era. Before Japan reintroduced Hangul to the Koreans, the Joseon dynasty banned any use of Hangul. Will you abandon Hangul and the modern Korean language? A movement without a distinct definition or goal only creates chaos and worst case it will affect the ones who were supposed to be protected by it.
  2. What has caused the whole boycott-Japan movement? Did Japan restricted exports to Korea for no reason? No. Japan had some good reasons to restrict exports. North Korea has developed a blockchain that happens to be used for freight ships. They also stole a bunch of Bitcoins to fund their nuclear program. And Cho-Guk had ties to both bitcoin and freight ships. And Cho-Guk himself is blatantly a Leninist while the US secretary of defense is openly quoting that president Moon's policy is benefiting China and North Korea. And Japan, which is also an ally of the US raised concerns that some of the strategical materials were smuggled into North Korea. The current administration basically said "F*** off" when they could simply show some paper work that the materials were used/shipped to somewhere else to prove their innocence. Why wouldn't Korea do this and embarrass Japan for their false allegations? The current administration had a very good chance at elevating their popularity without going through all the drama, which is still on effect, but chose to do nothing. What does that say to you?
  3. The boycott-Japan movement is not an organic movement. 민주연구원, a think tank under the Minjoo party released a research paper suggesting that they should use the emotional response to Japan's export restrictions to win the upcoming general elections. In Korea, propaganda from this side of the political spectrum is becoming more and more obvious since the 2008 US Beef protest. Back in 2008, MBC aired a program showing the "danger" of US beef, causing hundreds of thousands of people to storm the streets of Seoul. Brainwashed by one TV program, people lost their minds. So many Koreans thought everyone will all die from the Mad Cow Disease. But what now? American beef is now the best selling meet in Korea. Later the TV program was ruled as fake news by the supreme court and MBC made a statement with their apologies. And when you look at the ones who lead these protests based on fake news and mass lunacy, they are always the same people!
What I have learned is that many people in this sub underestimate the military/geopolitical climate of Korea. But again, with a 90% chance, I think that is just another naive point of view coming from someone who clearly doesn't understand Korean culture and history. However, I cannot tolerate when people actually push their ill-informed narrative on this sub to other people- where literally anyone on Earth can come and read posts and comments in the most widely used language.
submitted by rexkoner to korea [link] [comments]

The most asked question: "Why do you think Moon is a communist?"

  1. The Institute for Democracy is a think tank under the Minjoo party. One of their most well-known researches were about using the anti-Japan sentiment to influence the upcoming general elections. The Institute for Democracy entered an agreement with the Central Party School of the Communist Party of China to cooperate in policies and research. The Central Party School of the Communist Party of China is the most important education institution of all China because it is specifically dedicated to train officials for the CCP. Why are these two having these agreements and what is the purpose of sharing political studies with the communist party?
  2. Once leader of the Minjoo party and now the minister of justice Choo Mi-ae delivered a keynote at the Conversation Between World Parties and the Communist Party at Beijing when she was the leader of the Minjoo party. Most democratic nations did not attend this meeting. At the event she said, "중국 공산당 최고지도자이자 신시대의 설계사인 시진핑 총서기가 주장한 ‘두 개의 100년’과 ‘중국의 꿈’이 세계 평화와 번영에 공헌할 것으로 기대한다 ("The Two 100 Years" and the "Chinese Dream" will contribute to world peace and prosperity. And I am looking forward for it to happen because the supreme leader of the communist party, general secretary Xi as the architect of the new age has been preaching it)".
  3. The ex-minister of justice Cho kuk's cousin was the real owner of 코링크PE (a private equity management firm). This private equity invested in Bitcoins, but lucky enough they cashed out a month before the regulations were announced that was followed by a huge market crash. This private equity invested in a Korean cryptocurrency trader called 코인링크 that attracted investment deals from Huobi (Chinese crypto trader). 코인링크 also advanced it's market base to Russia. But guess what. North Korea also cooperates with Chinese and Russian cyrpto traders. Also, Cho kuk's relative was the owner of a freight ship company that owned a ship moving coal to North Korea. North Korea was behind a scam coin called Marine Chain, which was supposed to be used for "vessel transactions and offered partial ownership of maritime vessels in exchange for digital tokens". But most importantly, Cho kuk actually justified the need for a Leninist revolution in Korea.
  4. Im Jong-seok, the former chief of staff openly operated as a North Korean spy. He openly praised Kim Il-sung and the North Korean regime. He also went to jail for his activities.
His associates says it all. Moon himself has no difference. The only difference is his inability to speak without a prompter. And this.
submitted by rexkoner to KoreaRealism [link] [comments]

Development update for week of February 16th, 2020

Development update for week of February 16th, 2020 Skynet gets released! https://blog.sia.tech/skynet-bdf0209d6d34 Development Progress - The Sia team has been hard at work on the Siamux features. Siamux will enable parallel renter-host calls. Enabling a user to download multiple files simultaneously, or stream a video while simultaneously seeking to a different place. This is expected to dramatically improve the perceived speed of Sia as more actions can take place concurrently. - A new SIA_DATA_DIR env variable was added that can be used instead of the --sia-directory flag. - Sia now follows a standard 3 digit Semver 2.0 release schema.
Other News - David will be speaking about Skynet at the MIT Bitcoin Expo on March 7th https://mitbitcoinexpo.org/ - Sia & Filebase meetup on March 11th https://www.eventbrite.com/e/drinks-and-data-with-sia-filebase-tickets-93366709341
From the Community - Repertory released version 1.2.3 on Friday https://bitbucket.org/blockstorage/repertory/downloads/
Stats - 16 merge requests were accepted into Nebulous repos this week.
submitted by tbenz9 to siacoin [link] [comments]

Testnet wallet won't load

Hi I am trying to use testnet but the wallet won't load. Tried like 10 times. tried with/without vpn. I am syncing from China.
Config file:
{
"Network": "TestNet",
"MainNetBackendUriV3": "http://wasabiukrxmkdgve5kynjztuovbg43uxcbcxn6y2okcrsg7gb6jdmbad.onion/",
"TestNetBackendUriV3": "http://testwnp3fugjln6vh5vpj7mvq3lkqqwjj3c2aafyu7laxz42kgwh2rad.onion/",
"MainNetFallbackBackendUri": "https://wasabiwallet.io/",
"TestNetFallbackBackendUri": "https://wasabiwallet.co/",
"RegTestBackendUriV3": "http://localhost:37127/",
"UseTor": false,
"StartLocalBitcoinCoreOnStartup": false,
"StopLocalBitcoinCoreOnShutdown": true,
"LocalBitcoinCoreDataDir": "/Users/jeff/Library/Application Support/Bitcoin",
"TorSocks5EndPoint": "127.0.0.1:9050",
"MainNetBitcoinP2pEndPoint": "127.0.0.1:8333",
"TestNetBitcoinP2pEndPoint": "127.0.0.1:18333",
"RegTestBitcoinP2pEndPoint": "127.0.0.1:18444",
"MixUntilAnonymitySet": 50,
"PrivacyLevelSome": 2,
"PrivacyLevelFine": 21,
"PrivacyLevelStrong": 50,
"DustThreshold": "0.00000001"
}
the log file is here:
2019-12-25 20:15:58 INFO Program (44) Wasabi GUI started (1d6f97d5-f50c-45aa-adb3-789af0cf8479).
2019-12-25 20:15:59 INFO Global (163) Config is successfully initialized.
2019-12-25 20:15:59 INFO TransactionStore (28) MempoolStore.InitializeAsync finished in 16 milliseconds.
2019-12-25 20:15:59 INFO TransactionStore (28) ConfirmedStore.InitializeAsync finished in 8 milliseconds.
2019-12-25 20:15:59 INFO AllTransactionStore (27) InitializeAsync finished in 26 milliseconds.
2019-12-25 20:15:59 INFO Global (225) TorProcessManager is initialized.
2019-12-25 20:15:59 INFO Global (399) Loaded AddressManager from `/Users/jeff/.walletwasabi/client/AddressManageAddressManagerTestNet.dat`.
2019-12-25 20:16:00 INFO IndexStore (43) InitializeAsync finished in 344 milliseconds.
2019-12-25 20:16:00 INFO BitcoinStore (39) InitializeAsync finished in 347 milliseconds.
2019-12-25 20:16:01 INFO HostedServices (49) Started Software Update Checker.
2019-12-25 20:16:01 INFO Global (334) Start connecting to nodes...
2019-12-25 20:16:01 INFO Global (356) Start synchronizing filters...
2019-12-25 20:16:01 INFO MainWindow.xaml (74) UiConfig is successfully initialized.
2019-12-25 20:16:09 INFO Global (703) Wallet loaded: Wallet_electrum.
2019-12-25 20:16:09 INFO Global (487) Start Chaumian CoinJoin service...
2019-12-25 20:16:09 INFO Global (489) Starting WalletService...
2019-12-25 20:16:09 INFO CoinJoinClient (141) CoinJoinClient is successfully initialized.
submitted by recoba8814 to WasabiWallet [link] [comments]

Is it normal for a new Full Node server to repeatedly show Potential Sale Tip detected messages? What does this even mean. I surprisingly can't find anything with a solution on the internet. Please look at my log dump and give me an idea what to do. Im trying to run a full node in service to the net

Here is my log messages:

2019-11-14T03:05:38Z Bitcoin Core version v0.18.1 (release build)
2019-11-14T03:05:38Z Assuming ancestors of block 0000000000000000000f1c54590ee18d15ec70e68c8cd4cfbadb1b4f11697eee have valid signatures.
2019-11-14T03:05:38Z Setting nMinimumChainWork=0000000000000000000000000000000000000000051dc8b82f450202ecb3d471
2019-11-14T03:05:38Z Using the 'sse4(1way),sse41(4way)' SHA256 implementation
2019-11-14T03:05:38Z Default data directory /home/norman/.bitcoin
2019-11-14T03:05:38Z Using data directory /media/norman/Seagate Expansion Drive/.bitcoin/
2019-11-14T03:05:38Z Config file: /media/norman/Seagate Expansion Drive/.bitcoin/bitcoin.conf (not found, skipping)
2019-11-14T03:05:38Z Using at most 125 automatic connections (1024 file descriptors available)
2019-11-14T03:05:38Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2019-11-14T03:05:38Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2019-11-14T03:05:38Z Using 8 threads for script verification
2019-11-14T03:05:38Z scheduler thread start
2019-11-14T03:05:38Z HTTP: creating work queue of depth 16
2019-11-14T03:05:38Z No rpcpassword set - using random cookie authentication.
2019-11-14T03:05:38Z Generated RPC authentication cookie /media/norman/Seagate Expansion Drive/.bitcoin/.cookie
2019-11-14T03:05:38Z HTTP: starting 4 worker threads
2019-11-14T03:05:38Z Using wallet directory /media/norman/Seagate Expansion Drive/.bitcoin/
2019-11-14T03:05:38Z init message: Verifying wallet(s)...
2019-11-14T03:05:38Z Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
2019-11-14T03:05:38Z Using wallet /media/norman/Seagate Expansion Drive/.bitcoin/
2019-11-14T03:05:38Z BerkeleyEnvironment::Open: LogDir=/media/norman/Seagate Expansion Drive/.bitcoin/database ErrorFile=/media/norman/Seagate Expansion Drive/.bitcoin/db.log
2019-11-14T03:05:39Z init message: Loading banlist...
2019-11-14T03:05:39Z Cache configuration:
2019-11-14T03:05:39Z * Using 2.0 MiB for block index database
2019-11-14T03:05:39Z * Using 8.0 MiB for chain state database
2019-11-14T03:05:39Z * Using 440.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
2019-11-14T03:05:39Z init message: Loading block index...
2019-11-14T03:05:39Z Opening LevelDB in /media/norman/Seagate Expansion Drive/.bitcoin/blocks/index
2019-11-14T03:05:39Z Opened LevelDB successfully
2019-11-14T03:05:39Z Using obfuscation key for /media/norman/Seagate Expansion Drive/.bitcoin/blocks/index: 0000000000000000
2019-11-14T03:05:39Z LoadBlockIndexDB: last block file = 0
2019-11-14T03:05:39Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=1, size=293, heights=0...0, time=2009-01-03...2009-01-03)
2019-11-14T03:05:39Z Checking all blk files are present...
2019-11-14T03:05:39Z Opening LevelDB in /media/norman/Seagate Expansion Drive/.bitcoin/chainstate
2019-11-14T03:05:40Z Opened LevelDB successfully
2019-11-14T03:05:40Z Using obfuscation key for /media/norman/Seagate Expansion Drive/.bitcoin/chainstate: fb03fb54abfe4745
2019-11-14T03:05:40Z Loaded best chain: hashBestChain=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f height=0 date=2009-01-03T18:15:05Z progress=0.000000
2019-11-14T03:05:40Z init message: Rewinding blocks...
2019-11-14T03:05:40Z init message: Verifying blocks...
2019-11-14T03:05:40Z block index 1516ms
2019-11-14T03:05:40Z init message: Loading wallet...
2019-11-14T03:05:40Z BerkeleyEnvironment::Open: LogDir=/media/norman/Seagate Expansion Drive/.bitcoin/database ErrorFile=/media/norman/Seagate Expansion Drive/.bitcoin/db.log
2019-11-14T03:05:40Z [default wallet] nFileVersion = 180100
2019-11-14T03:05:40Z [default wallet] Keys: 2001 plaintext, 0 encrypted, 2001 w/ metadata, 2001 total. Unknown wallet records: 0
2019-11-14T03:05:41Z [default wallet] Wallet completed loading in 449ms
2019-11-14T03:05:41Z [default wallet] setKeyPool.size() = 2000
2019-11-14T03:05:41Z [default wallet] mapWallet.size() = 0
2019-11-14T03:05:41Z [default wallet] mapAddressBook.size() = 0
2019-11-14T03:05:41Z mapBlockIndex.size() = 1
2019-11-14T03:05:41Z nBestHeight = 0
2019-11-14T03:05:41Z torcontrol thread start
2019-11-14T03:05:41Z Imported mempool transactions from disk: 0 succeeded, 0 failed, 0 expired, 0 already there
2019-11-14T03:05:41Z Bound to [::]:8333
2019-11-14T03:05:41Z Bound to 0.0.0.0:8333
2019-11-14T03:05:41Z init message: Loading P2P addresses...
2019-11-14T03:05:41Z Loaded 253 addresses from peers.dat 16ms
2019-11-14T03:05:41Z init message: Starting network threads...
2019-11-14T03:05:41Z net thread start
2019-11-14T03:05:41Z dnsseed thread start
2019-11-14T03:05:41Z opencon thread start
2019-11-14T03:05:41Z init message: Done loading
2019-11-14T03:05:41Z addcon thread start
2019-11-14T03:05:41Z msghand thread start
2019-11-14T03:05:52Z Loading addresses from DNS seeds (could take a while)
2019-11-14T03:05:54Z 187 addresses found from DNS seeds
2019-11-14T03:05:54Z dnsseed thread exit
2019-11-14T03:37:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 1890 seconds ago)
2019-11-14T03:48:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 2520 seconds ago)
2019-11-14T03:58:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 3150 seconds ago)
2019-11-14T04:09:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 3780 seconds ago)
2019-11-14T04:19:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 4410 seconds ago)
2019-11-14T04:30:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 5040 seconds ago)
2019-11-14T04:40:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 5670 seconds ago)
2019-11-14T04:51:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 6300 seconds ago)
2019-11-14T05:01:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 6930 seconds ago)
2019-11-14T05:12:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 7560 seconds ago)
2019-11-14T05:22:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 8190 seconds ago)
2019-11-14T05:33:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 8820 seconds ago)
2019-11-14T05:43:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 9450 seconds ago)
2019-11-14T05:54:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 10080 seconds ago)
2019-11-14T06:04:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 10710 seconds ago)
2019-11-14T06:15:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 11340 seconds ago)
2019-11-14T06:25:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 11970 seconds ago)
2019-11-14T06:36:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 12600 seconds ago)
2019-11-14T06:46:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 13230 seconds ago)
2019-11-14T06:57:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 13860 seconds ago)
2019-11-14T07:07:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 14490 seconds ago)
2019-11-14T07:18:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 15120 seconds ago)
2019-11-14T07:28:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 15750 seconds ago)
2019-11-14T07:39:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 16380 seconds ago)
2019-11-14T07:49:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 17010 seconds ago)
2019-11-14T08:00:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 17640 seconds ago)
2019-11-14T08:10:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 18270 seconds ago)
2019-11-14T08:21:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 18900 seconds ago)
2019-11-14T08:31:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 19530 seconds ago)
2019-11-14T08:42:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 20160 seconds ago)
2019-11-14T08:52:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 20790 seconds ago)
2019-11-14T09:03:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 21420 seconds ago)
2019-11-14T09:13:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 22050 seconds ago)
2019-11-14T09:24:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 22680 seconds ago)
2019-11-14T09:34:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 23310 seconds ago)
2019-11-14T09:45:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 23940 seconds ago)
2019-11-14T09:55:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 24570 seconds ago)
2019-11-14T10:06:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 25200 seconds ago)
2019-11-14T10:16:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 25830 seconds ago)
2019-11-14T10:27:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 26460 seconds ago)
2019-11-14T10:37:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 27090 seconds ago)
2019-11-14T10:48:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 27720 seconds ago)
2019-11-14T10:58:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 28350 seconds ago)
2019-11-14T11:09:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 28980 seconds ago)
2019-11-14T11:19:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 29610 seconds ago)
2019-11-14T11:30:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 30240 seconds ago)
2019-11-14T11:40:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 30870 seconds ago)
2019-11-14T11:51:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 31500 seconds ago)
2019-11-14T12:01:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 32130 seconds ago)
2019-11-14T12:12:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 32760 seconds ago)
2019-11-14T12:22:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 33390 seconds ago)
2019-11-14T12:33:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 34020 seconds ago)
2019-11-14T12:43:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 34650 seconds ago)
2019-11-14T12:54:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 35280 seconds ago)
2019-11-14T13:04:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 35910 seconds ago)
2019-11-14T13:15:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 36540 seconds ago)
2019-11-14T13:25:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 37170 seconds ago)
2019-11-14T13:36:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 37800 seconds ago)
2019-11-14T13:46:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 38430 seconds ago)
2019-11-14T13:57:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 39060 seconds ago)
2019-11-14T14:07:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 39690 seconds ago)
2019-11-14T14:18:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 40320 seconds ago)
2019-11-14T14:28:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 40950 seconds ago)
2019-11-14T14:39:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 41580 seconds ago)
2019-11-14T14:49:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 42210 seconds ago)
2019-11-14T15:00:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 42840 seconds ago)
2019-11-14T15:10:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 43470 seconds ago)
2019-11-14T15:21:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 44100 seconds ago)
2019-11-14T15:31:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 44730 seconds ago)
2019-11-14T15:42:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 45360 seconds ago)
2019-11-14T15:52:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 45990 seconds ago)
2019-11-14T16:03:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 46620 seconds ago)
2019-11-14T16:13:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 47250 seconds ago)
2019-11-14T16:24:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 47880 seconds ago)
2019-11-14T16:34:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 48510 seconds ago)
2019-11-14T16:45:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 49140 seconds ago)
2019-11-14T16:55:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 49770 seconds ago)
2019-11-14T17:06:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 50400 seconds ago)
2019-11-14T17:16:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 51030 seconds ago)
2019-11-14T17:27:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 51660 seconds ago)
2019-11-14T17:37:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 52290 seconds ago)
2019-11-14T17:48:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 52920 seconds ago)
2019-11-14T17:58:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 53550 seconds ago)
2019-11-14T18:09:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 54180 seconds ago)
2019-11-14T18:19:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 54810 seconds ago)
2019-11-14T18:30:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 55440 seconds ago)
2019-11-14T18:40:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 56070 seconds ago)
2019-11-14T18:51:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 56700 seconds ago)
2019-11-14T19:01:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 57330 seconds ago)


this goes on until I decided just to shut down server after 24 hours and the .dat blockchain file was stuck at 16MB in size. Seemed like going nowhere.
submitted by Alchemy333 to Bitcoin [link] [comments]

Massive List of BSV Apps (please comment for new ones or updates/errors etc...)

🔗 means app lives on-chain. i.e. the app/content is hosted on the blockchain, something we take great pride in with BSV.

Block Explorers

Communities

Content

Exchanges

Financial Services

Gaming & Entertainment

News

Onchain Storage

Search Engines

Merchants & Services

Freeview Video / Radio / Podcasts

Tried to list prominent channels, open to all ideas but don't want channels with 3 subscribers and 2 videos. Show your Proof of Work!

Streamanity Video Channels

TODO. Think it is important to separate Freeview (Youtube etc..) from Streaminity, for new people to the space who don't have BSV.

Wallets

Credit: For initial list http://agora.icu and some jim-btc webscraping ;) Pastebin here (to easily reply to any reddit post about lack of apps): https://pastebin.com/qyzf8z2c
submitted by jim-btc to bitcoincashSV [link] [comments]

AMA/Tutorial: Run a full node on AWS free tier with local LAN storage

AMA/Tutorial: Run a full node on AWS free tier with local LAN storage
This is a tutorial/AMA on how you can be running a full node, in the AWS cloud, for very low cost or even free.
I used to run a node on my local network but there is a problem with this; your public IP is broadcast, and then it gets associated with Bitcoin. Node owners are likely to own Bitcoin, and this raises your personal threat profile, validated against my IDS/IPS logs.
Run a VPN? Many VPNs are automatically blocked, or sketchy. Tor is also blocked on a large portion of the internet. Neither provide you with a real static IP, and that helps out the network.
There is a easy solution to this; run a node on the AWS free tier, and use an elastic IP so you have a static address. Bandwidth is free in, and low cost out, and you can control how much of that you use easily, and control your spent. The problem is that Amazon charges a LOT for online storage and even with a 1MB blocksize, the blockchain is very large and growing steadily! We mitigate this by using a VPN back to your network, where you can store the blockchain on a SMB share.
It is not complicated to do, but there are very many moving pieces to keep track of and configure. In order to fully trust your node, the best way is to build it from scratch. This is my goal in walking you through the process.
There are lots of ways to accomplish this same task; I only want to present one that works, and you can go from there. Once you have access to the blockchain in the cloud for reasonable prices, you can also look at things like the Lightning Network.
This article makes four major assumptions:

  1. That you have a OpenVPN server on your network and know how to configure it. I use pfSense and OpenVPN; others will work just as well, but you'll need to do a little work to figure out the particulars. If you don't know how, do not fret! There are loads of good tutorials for just about every platform. Or ask below. I also limited the user with access to the share at the firewall specifically to the IP hosting the share to lower the threat envelope.
  2. That you have the blockchain downloaded locally and reasonably up to date. If you don't, head on over to bitcoin.org and download it for OSX or Windows or Linux, whatever you use for your workstation. Follow the directions to set up the software and download/synchronize it to the network. This will take awhile! Once you've synchronized, copy the data directory to your SMB share you want the AWS instance to access. You could also synchronize everything directly on AWS too, but it will likely take longer and may cost a bit for the bandwidth.
  3. That you're on windows. OSX and Linux will have slightly different processes to connect to the instance via the terminal and SSH. If you need help, ask, and I am sure we can get you fixed up.
  4. That you've read the excellent bitcoin.org full node tutorial here: https://bitcoin.org/en/full-node

With that, on with the show!
First: Head on over to https://aws.amazon.com/ and make yourself an account.
Once you've set up you'll need to start the process of creating a virtual machine on AWS. Look for this graphic and click on it:

Start by launching a new machine

Follow the rabbit hole, and you'll be looking to create a plain jane Amazon AMI Linux instance. It looks like this:

Pick the basic AMI instance
Keep in mind you want to pick the x86 version, which is the default.

Continue clicking, you'll want to select the t2.micro instance that is eligible for the free tier for new accounts.

Pick the free tier. You can also upgrade to the smaller tier for more ram, but the micro works for now.
Now, you're going to need a way to connect to your soon-to-be-created node in the cloud. Amazon uses SSH keys to do this, so the next step means you're going to make some. You need to save this file, as if you lose it, you won't be able to access your node anymore. Much like your wallet private keys!

Beware losing your keys!

If you've made it this far, you're almost launched!
Now we need to convert the key to a format that we can use to connect to the instance from Windows. I recommend using Putty! https://www.putty.org/ if you don't have it already; if you're on OSX or Linux, you likely have what you need already.
Follow the guide here to get connected: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/putty.html

Next you'll need to set up a opening in the firewall if you want incoming connections. This is done by adding to the security group in the "Network and Security" section; edit it to look like this:

Change the inbound security rules for the instance to accept incoming connections on 8333.

The hard part is over!
Optional: Configuring a static IP. Amazon calls their implementation "elastic" IPs, but it's really a static IP that you can move around between instances very easily. It will ensure your public address on AWS does not change; it isn't required, but it is better if you intend on allowing outgoing connections.
Go back to the main dashboard display.
In "Network and Security", click on "Elastic IPs".
Select Allocate New Address (blue button on top) and then select it in the table. In actions, you will see "Associate Address". Select this then assign the address to the instance you have previously configured. Done!

Next up: Log into your machine, and immediately update everything. Use the IP provided by Amazon, or the Elastic IP if you assigned one to the instance in the last step.
type: "sudo yum update"

Now, let's get the VPN configured.
First step is to install OpenVPN. We need to install the extended package library to do this.
type: "sudo amazon-linux-extras install epel"
type: "sudo yum-config-manager --enable epel"
Now you can install OpenVPN.
type: "sudo yum install openvpn"
You will need your credential file from OpenVPN; it's a file you generate that will have a .ovpn extension. But you're going to need to upload it to the instance. You can do this through the scp command on OSX or Linux, but if you're on Windows, you'll need another utility. Get WinSCP here: https://winscp.net/eng/download.php
But we'll have to tell it where your key file is so you can login. Select "New Session", then use the same IP and username as you did to connect before. We'll need to tell it about the key file though! Select the "Advanced" tab then under the SSH section, click on "Authentication" and then select your private key file you generated in the tutorial above.
Connect and upload the .ovpn file that you generated when you added a user for the VPN. This step depends on your OpenVPN configuration - ask below if you have problems.
Next, let's verify we can connect to the VPN!
type: "openvpn --config my-configuration-file-made-by-openvpn.ovpn &"
You will be prompted for a password if you configured one.
Verify operation by pinging your LAN router, e.g.
type: "ping 192.168.2.1" or the address of the SMB server where you shared the information.

Allllrighty! Next up is getting connected to your blockchain. Create a directory where the data directory will be mounted.
type: "mkdir blockchain"
We need to install samba and some utilities to get things mounted.
type: "sudo yum install samba"
type: "sudo yum install cifs-utils"

Now let's mount the folder:
type: "sudo mount -t cifs //192.168.2.100/Bitcoin ./blockchain -o user=bitcoin,vers=2.0,uid=ec2-user,gid=ec2 user,file_mode=0777,dir_mode=0777"
Where " //192.168.2.100/Bitcoin" is the address of the SMB server and share where you put the data directory from your initial sync. If you didn't, and just want to sync everything from AWS, then make sure it's a folder where your user has access. In this case, I'm assuming you've made a SMB user with the name "Bitcoin". The command will prompt you for the password to access the share. The other bits ensure you can have read and write access to the share once it's mounted in AWS.

Now we're ready for some Bitcoin! Props to the tutorial here: https://hackernoon.com/a-complete-beginners-guide-to-installing-a-bitcoin-full-node-on-linux-2018-edition-cb8e384479ea
But I'll summarize for you:
Download and then re-upload with WinSCP, or download directly to your instance with wget, the most current Bitcoin core. In this case, it's bitcoin-0.18.0-i686-pc-linux-gnu.tar.gz downloaded from https://bitcoin.org/en/bitcoin-core/.
Let's verify it hasn't been tampered with once you have it uploaded to the terminal:
type: "sha256sum bitcoin-0.18.0-i686-pc-linux-gnu.tar.gz"
Then compare that with the hash value that's listed in the SHA256SUMS.asc file on bitcoin.org. In this case, "36ce9ffb375f6ee280df5a86e61038e3c475ab9dee34f6f89ea82b65a264183b" all matches up, so we know nobody has done anything evil or nefarious to the file.
Unzip the file:
type: "tar zxvf bitcoin-0.18.0-i686-pc-linux-gnu.tar.gz"
There is a warning about a symbolic link; everything seems to work OK regardless, but if anyone knows what or how to fix, please comment.
We'll need to get some missing libraries before we can run it; these aren't in the basic AMI instance.
type: "sudo yum install glibc.i686"
type: "yum install libgcc_s.so.1"

FINALLY! We are ready to launch the program. Go to the "bin" directory inside where you unzipped the Bitcoin Core tarball. (e.g. /home/ec2-useblockchain/bitcoin-0.18.0/bin)
./bitcoind -datadir=/home/ec2-useblockchain/data
You will see the program either start to sync and download, or start to read the existing blockchain file that you put in the share from before.

Congrats!

There are a couple extra steps to have it automatically start on reboot, but let's see if anyone gets this far first. I use the "screen" program to do this, but there's also a daemon mode, and some other functionality that is discussed in the hackernoon tutorial.
The primary cost will be outgoing bandwidth. AWS charges $0.10/GB beyond 15GB; You can limit the outgoing bandwidth easily according to your budget: https://bitcoin.org/en/full-node#reduce-traffic

Hope this encourages people to try running a free, or very low cost, cloud node, with a substantially reduced threat profile.
submitted by xtal_00 to Bitcoin [link] [comments]

Trying to debug a "found" library. Compiles fine but get "Read error" on console upon upload

This happens whether or not the device connected. BTW I have the data line connected to power via 4K7 resistor.
Here's the library :
LaCrosse_TX23.h - Library for reading LaCrosse TX23 anemometer data.
LaCrosse TX23 is a wind speed and direction sensor. It uses 3 wires for communication and power: Pin1 Brown(Black) DATA Pin2 Red Vcc Pin3 Green N/C Pin4 Yellow GND
DATA pin is to be connected directly to one of Arduino ports. 
Created by Krzysztof Egzmont, 06.11.2016. Based on https://w...content-available-to-author- only...k.nz/2012/08/la-crosse-tx23u-anemometer- communication-protocol/ Big thanks for John.
Donations: Bitcoin - 1JrHQwJWt1JNZepT1EXqPSioXcwD227nnU Ethereum - 0xFC9713013e78f6F14bA5064E36f875dbbB32B94a
BSD license, all text above must be included in any redistribution *************************************************************************************************/
#include  LaCrosse_TX23::LaCrosse_TX23(int pin) { pinMode(pin, INPUT); _pin = pin; 
}
void LaCrosse_TX23::pullBits(void dst, bool *src, int count) { uint8_t * d = (uint8_t) dst; for (int i=0; i bool LaCrosse_TX23::read(float &speed, int &direction) { speed = 0; direction = 0;
digitalWrite(_pin,LOW); pinMode(_pin,OUTPUT); delay(500); pinMode(_pin,INPUT); pulseIn(_pin,LOW); unsigned bitLen = 1200; bool data[50]; bool lastState = 1; unsigned long start = micros(); for(unsigned long t = 0; t<50000; t = micros()-start) { bool state = digitalRead(_pin); unsigned bitNum = t/bitLen; if(t%bitLen>bitLen/2) data[bitNum] = state; if(state!=lastState) { unsigned delta = t%bitLen; if(delta<100) start -= delta; else if(delta>900) start += delta; lastState = state; } } uint8_t ctr = 0; pullBits(&ctr,data+0,5); uint8_t dir = 0; pullBits(&dir,data+5,4); uint16_t spd = 0; pullBits(&spd,data+9,12); uint8_t sum = 0; pullBits(&sum,data+21,4); uint8_t ndir = 0; pullBits(&ndir,data+25,4); ndir ^= 0x0f; uint16_t nspd = 0; pullBits(&nspd,data+29,12); nspd ^= 0x0fff; uint8_t csum = 0x0f & (dir + (spd&0x0f) + ((spd>>4)&0x0f) + ((spd>>8)&0x0f)); if(ctr!=27) return false; if(csum!=sum) return false; if(spd!=nspd || dir!=ndir) return false; speed = spd/10.0; direction = dir; return true; 
submitted by jnr890 to arduino [link] [comments]

Bitcoind stuck in startup loading block index

Hi,
I have had bitcoin core running on a raspberry pi for about 4 month now (followed the raspibolt instructions from stadicus) and it worked fine until 3 days ago it suddenly stopped working. With bitcoin-cli blockchaininfo i got
error code: -28 Loading block index... 
or something similar. When a looked in the debug log file i saw this:
2019-08-29T16:48:08Z BerkeleyEnvironment::Open: LogDir=/home/bitcoin/.bitcoin/database ErrorFile=/home/bitcoin/.bitcoin/db.log 2019-08-29T16:48:11Z init message: Loading banlist... 2019-08-29T16:48:11Z Cache configuration: 2019-08-29T16:48:11Z * Using 2.0 MiB for block index database 2019-08-29T16:48:11Z * Using 8.0 MiB for chain state database 2019-08-29T16:48:11Z * Using 90.0 MiB for in-memory UTXO set (plus up to 47.7 MiB of unused mempool space) 2019-08-29T16:48:11Z init message: Loading block index... 2019-08-29T16:48:11Z Opening LevelDB in /home/bitcoin/.bitcoin/blocks/index 2019-08-29T16:48:11Z Opened LevelDB successfully 2019-08-29T16:48:11Z Using obfuscation key for /home/bitcoin/.bitcoin/blocks/index: 0000000000000000 2019-08-29T16:54:14Z 2019-08-29T16:54:14Z Bitcoin Core version v0.18.1 (release build) 2019-08-29T16:54:14Z Assuming ancestors of block 0000000000000000000f1c54590ee18d15ec70e68c8cd4cfbadb1b4f11697eee have valid signatures. 2019-08-29T16:54:14Z Setting nMinimumChainWork=0000000000000000000000000000000000000000051dc8b82f450202ecb3d471 2019-08-29T16:54:14Z Using the 'standard' SHA256 implementation 2019-08-29T16:54:15Z Default data directory /home/bitcoin/.bitcoin 2019-08-29T16:54:15Z Using data directory /home/bitcoin/.bitcoin 2019-08-29T16:54:15Z Config file: /home/bitcoin/.bitcoin/bitcoin.conf 2019-08-29T16:54:15Z Using at most 20 automatic connections (1024 file descriptors available) 2019-08-29T16:54:15Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements 2019-08-29T16:54:15Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements 2019-08-29T16:54:15Z Using 4 threads for script verification 2019-08-29T16:54:15Z scheduler thread start 2019-08-29T16:54:15Z HTTP: creating work queue of depth 16 2019-08-29T16:54:15Z Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcauth for rpcauth auth generation. 2019-08-29T16:54:15Z HTTP: starting 4 worker threads 2019-08-29T16:54:15Z Using wallet directory /home/bitcoin/.bitcoin 2019-08-29T16:54:15Z init message: Verifying wallet(s)... 2019-08-29T16:54:15Z Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2019-08-29T16:54:15Z Using wallet /home/bitcoin/.bitcoin 2019-08-29T16:54:15Z BerkeleyEnvironment::Open: LogDir=/home/bitcoin/.bitcoin/database ErrorFile=/home/bitcoin/.bitcoin/db.log 2019-08-29T16:54:16Z init message: Loading banlist... 2019-08-29T16:54:16Z Cache configuration: 2019-08-29T16:54:16Z * Using 2.0 MiB for block index database 2019-08-29T16:54:16Z * Using 8.0 MiB for chain state database 2019-08-29T16:54:16Z * Using 90.0 MiB for in-memory UTXO set (plus up to 47.7 MiB of unused mempool space) 2019-08-29T16:54:16Z init message: Loading block index... 2019-08-29T16:54:16Z Opening LevelDB in /home/bitcoin/.bitcoin/blocks/index 2019-08-29T16:54:16Z Opened LevelDB successfully 2019-08-29T16:54:16Z Using obfuscation key for /home/bitcoin/.bitcoin/blocks/index: 0000000000000000 
After that there should follow a line about Loading the block index but it never appears.
It seems to be restarting without shutting down correctly, maybe it cannot find the block index? I tried reinstalling core, recreating the symlink to the hdd and resetting the service but nothing happened. Everytime it starts it gets stuck at the same point. It also takes an awful long time to stop bitcoind but i don't know if that is normal.
I found several people with similar problems online but noting helped so far. Has anyone had a similar problem in the past and found a solution to this?
submitted by BologneseWithCheese to Bitcoin [link] [comments]

Dosen't inizialize propriety inside the class with the constructor compiling error

Hello guys,
I'm a java programmer and I'm studying C++ with my personal project I want to create a Singleton pattern that contains the proprieties, but when go to initialize the propriety inside the private constructor no-arg I have a compiling error with, it is this
[ 5%] Building CXX object CMakeFiles/SpyCBlockRPC.dicommands/DecodeScriptCommand.cpp.o [ 11%] Building CXX object CMakeFiles/SpyCBlockRPC.diClientBitcoinSingleton.cpp.o /home/vincenzo/Github/SpyCBlockRPC/ClientBitcoinSingleton.cpp: In constructor ‘spyCBlockRPC::ClientBitcoinSingleton::ClientBitcoinSingleton()’: /home/vincenzo/Github/SpyCBlockRPC/ClientBitcoinSingleton.cpp:9:62: error: no matching function for call to ‘BitcoinAPI::BitcoinAPI()’ spyCBlockRPC::ClientBitcoinSingleton::ClientBitcoinSingleton() ^ In file included from /home/vincenzo/Github/SpyCBlockRPC/ClientBitcoinSingleton.h:7:0, from /home/vincenzo/Github/SpyCBlockRPC/ClientBitcoinSingleton.cpp:3: /uslocal/include/bitcoinapi/bitcoinapi.h:28:5: note: candidate: BitcoinAPI::BitcoinAPI(const string&, const string&, const string&, int, int) BitcoinAPI(const std::string& user, const std::string& password, const std::string& host, int port, int httpTimeout = 50000); ^~~~~~~~~~ /uslocal/include/bitcoinapi/bitcoinapi.h:28:5: note: candidate expects 5 arguments, 0 provided /uslocal/include/bitcoinapi/bitcoinapi.h:19:7: note: candidate: constexpr BitcoinAPI::BitcoinAPI(const BitcoinAPI&) class BitcoinAPI ^~~~~~~~~~ /uslocal/include/bitcoinapi/bitcoinapi.h:19:7: note: candidate expects 1 argument, 0 provided 
This is my file ClientBitcoinSingleton.h

namespace spyCBlockRPC { class ClientBitcoinSingleton { public: static ClientBitcoinSingleton& getInstance() { static ClientBitcoinSingleton SINGLETON; return SINGLETON; } BitcoinAPI getBitcoinApi() const; private: ClientBitcoinSingleton(); //BitcoinAPI bitcoinApi{"", "", "", 8332}; //TODO chanhe this resolve the problem, I don't want inizialize it with this code BitcoinAPI bitcoinApi; } 
This is my file ClientBitcoinSingleton.cpp
#include  #include "ClientBitcoinSingleton.h" using namespace std; using namespace cppproperties; using namespace spyCBlockRPC; spyCBlockRPC::ClientBitcoinSingleton::ClientBitcoinSingleton() { string user =""; string pass = ""; string ip =""; int port = 8080; this->dirLogTest = config.GetProperty(DIR_LOG_TEST); this->dirDatatest = config.GetProperty(DIR_DATA_TEST); bitcoinApi = BitcoinAPI{user, pass, ip, port}; } 
I'm not understanding the error, how I want to write this code with no one error?

Thanks so much for your help
submitted by crazyjoker96 to cpp_questions [link] [comments]

advice style confension to the code

Hello guys,

I'm new the C++., and now I'm working on my personal project, an now I'm asking if exist on method better for import another fil inside another directory.

I have my project with the files divides to the directories, an now I have this #include ".."
an example
#include  #include "../../../include/spycblockrpc/core/graph/WrapperInformations.h" #include "DAOTransactionsGraph.h" #include "../../DAOException.h" #include "../../../core/ConfiguratorSingleton.h" 
How can import this file with different mode?

My file CMake
cmake_minimum_required(VERSION 3.9) project(SpyCBlock) set(CMAKE_CXX_STANDARD 14) # Locate GTest enable_testing() find_package(GTest REQUIRED) include_directories(${GTEST_INCLUDE_DIRS}) #Glog find_package(glog 0.3.5 REQUIRED) ## Json library find_package(nlohmann_json 3.2.0 REQUIRED) find_package(RapidJSON) #This find the element in the OS #bitcoin rpc lib find_library(bitcoinapi 0.3 REQUIRED) # Link runTests with what we want to test and the GTest and pthread library add_executable( SpyCBlockTests test/util/DAOUtilTest.cpp test/StructureBitcoinCoreTest.cpp test/SHABitcoinCoreTest.cpp test/SerealizationTest.cpp test/DAOJsonTest.cpp test/NullDataTransactionsTest.cpp test/ExceptionCompactsizeTest.cpp test/ConfiguratorSingletonTest.cpp test/DAOManagerGraphTest.cpp util/uint256.cpp util/strencodings.cpp util/prevector.cpp ) #using glog target_link_libraries(${PROJECT_NAME} glog::glog) target_link_libraries(SpyCBlockTests glog::glog) #using gtest target_link_libraries(SpyCBlockTests ${GTEST_LIBRARIES} pthread) ##using filesystem target_link_libraries(${PROJECT_NAME} stdc++fs) target_link_libraries(SpyCBlockTests stdc++fs) ##Json library target_link_libraries(${PROJECT_NAME} nlohmann_json::nlohmann_json) #bitcoin rpc lib target_link_libraries(SpyCBlockTests bitcoinapi) target_link_libraries(${PROJECT_NAME} bitcoinapi) 
submitted by crazyjoker96 to cpp_questions [link] [comments]

Optimizing Compiler with google benchmark on raspberry pi 3b

Hi guys,

I have a problem that I believe concerns the optimization of the raspberry compiler, I will explain my problem to you.

I'm writing a parser for the bitcoin core raw files and I used C ++, now I have two types of decodes,



Now I ask you, is there something wrong with my code? Is there a possibility that the library optimizes something it shouldn't?

#include  #include  #include  #include "../../core/SpyCBlock.h" using namespace spyCBlock; using namespace std; string getRootPath() { return experimental::filesystem::current_path(); } const string FILE_DIR = getRootPath() + "/file/"; void createGraphTxOneFile(); void createGraphIdWalletOneFile(); void decodeJsonOneFile(); //BM void BM_createGraphTxOneFile(benchmark::State& state) { while (state.KeepRunning()) { createGraphTxOneFile(); } } void BM_decodeJsonOneFile(benchmark::State& state) { while (state.KeepRunning()) { decodeJsonOneFile(); } } BENCHMARK(BM_createGraphTxOneFile)->Arg(8); BENCHMARK(BM_decodeJsonOneFile)->Arg(8); void createGraphTxOneFile() { SpyCBlock spyCBlock; spyCBlock.convertBlkIntoGraphForm(FILE_DIR, FILE_DIR); benchmark::DoNotOptimize(pathLogRoot); benchmark::DoNotOptimize(spyCBlock); } //for this I need configure bitcoind with mainet void createGraphIdWalletOneFile() { SpyCBlock spyCBlock; spyCBlock.convertBlkIntoGraphFormPubKey(FILE_DIR, FILE_DIR); benchmark::DoNotOptimize(pathLogRoot); benchmark::DoNotOptimize(spyCBlock); } void decodeJsonOneFile() { SpyCBlock spyCBlock; spyCBlock.convertBlkIntoJson(FILE_DIR, FILE_DIR); benchmark::DoNotOptimize(pathLogRoot); benchmark::DoNotOptimize(spyCBlock); } BENCHMARK_MAIN(); 
submitted by crazyjoker96 to cpp_questions [link] [comments]

[DEVELOPMENT] Bitcoind IPV4 testnet port (18332) is failing to bind

[SOLVED] Thanks for everyone that have helped!


Hello everyone, this is a development problem that I'm currently having. Since the BTC Development sub is kind of inactive and I couldn't find any rule contraty to posting about BTC Development, I'll try my luck in here as I'm hopeless already. I've posted on BTC Stack Exchange but no answers also. Please, don't get me wrong, I'm trying to solve this problem for many days now, I've looked up everywhere for this.
I'm new to Bitcoin development and I'm currently having difficulties trying to make RPC calls from a Docker Container to a Bitcoin-Core daemon running in a SSH server. I suppose that the problem may be with Firewall or closed ports, but I also do not know much about Network settings.
I'm using nbobtc/bitcoind-php package to make the RPC calls with HTTP requests, and it is running in a Docker container. I'm sure the container is functional and is not the problem.
So here's what happening: when I run bitcoind in root user (but normal also won't work) in my SSH server, the IPV4 testnet port seems to be not opened. This message goes up when I run bitcoind:
Binding RPC on address 0.0.0.0 port 18332 failed.
Here's what my bitcoin.conf looks like (I want to use testnet in here). I'm using Bitcoin-Core "subversion": "Satoshi:0.17.1".
server=1 debug=net txindex=1 testnet=1 rpcuser=userb rpcpassword=test test.rpcport=18332 # I've already tried allowing the IP these 3 ways: # rpcallowip=192.168.xx.xx # My machine's IP # rpcallowip=172.19.x.x/xx # Docker's NBOBTC container IP # rpcallowip=0.0.0.0/0 # Allowing all IP datadir=/home/bitcoin-dev/.bitcoin debuglogfile=/home/bitcoin-dev/.bitcoin/debug.log 
Here's what appears in debug.log right after I run Bitcoind:
2019-05-06T14:43:10Z Bitcoin Core version v0.17.1 (release build) 2019-05-06T14:43:10Z InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1 2019-05-06T14:43:10Z Assuming ancestors of block 0000000000000037a8cd3e06cd5edbfe9dd1dbcc5dacab279376ef7cfc2b4c75 have valid signatures. 2019-05-06T14:43:10Z Setting nMinimumChainWork=00000000000000000000000000000000000000000000007dbe94253893cbd463 2019-05-06T14:43:10Z Using the 'sse4(1way),sse41(4way)' SHA256 implementation 2019-05-06T14:43:10Z Default data directory /root/.bitcoin 2019-05-06T14:43:10Z Using data directory /home/bitcoin-dev/.bitcoin/testnet3 2019-05-06T14:43:10Z Using config file /home/bitcoin-dev/.bitcoin/bitcoin.conf 2019-05-06T14:43:10Z Using at most 125 automatic connections (1024 file descriptors available) 2019-05-06T14:43:10Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements 2019-05-06T14:43:10Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements 2019-05-06T14:43:10Z Using 4 threads for script verification 2019-05-06T14:43:10Z scheduler thread start 2019-05-06T14:43:10Z Binding RPC on address 0.0.0.0 port 18332 failed. 2019-05-06T14:43:10Z HTTP: creating work queue of depth 16 2019-05-06T14:43:10Z Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcauth for rpcauth auth generation. 2019-05-06T14:43:10Z HTTP: starting 4 worker threads 2019-05-06T14:43:10Z Using wallet directory /home/bitcoin-dev/.bitcoin/testnet3/wallets 2019-05-06T14:43:10Z init message: Verifying wallet(s)... 2019-05-06T14:43:10Z Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2019-05-06T14:43:10Z Using wallet wallet.dat 2019-05-06T14:43:10Z BerkeleyEnvironment::Open: LogDir=/home/bitcoin-dev/.bitcoin/testnet3/wallets/database ErrorFile=/home/bitcoin-dev/.bitcoin/testnet3/wallets/db.log 2019-05-06T14:43:10Z net: setting try another outbound peer=false 2019-05-06T14:43:10Z Cache configuration: 2019-05-06T14:43:10Z * Using 2.0MiB for block index database 2019-05-06T14:43:10Z * Using 56.0MiB for transaction index database 2019-05-06T14:43:10Z * Using 8.0MiB for chain state database 2019-05-06T14:43:10Z * Using 384.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space) 2019-05-06T14:43:10Z init message: Loading block index... 2019-05-06T14:43:10Z Opening LevelDB in /home/bitcoin-dev/.bitcoin/testnet3/blocks/index 2019-05-06T14:43:10Z Opened LevelDB successfully 2019-05-06T14:43:10Z Using obfuscation key for /home/bitcoin-dev/.bitcoin/testnet3/blocks/index: 0000000000000000 2019-05-06T14:43:19Z LoadBlockIndexDB: last block file = 161 2019-05-06T14:43:19Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=755, size=30875345, heights=1513309...1514061, time=2019-04-29...2019-05-03) 2019-05-06T14:43:19Z Checking all blk files are present... 2019-05-06T14:43:20Z Opening LevelDB in /home/bitcoin-dev/.bitcoin/testnet3/chainstate 2019-05-06T14:43:20Z Opened LevelDB successfully 2019-05-06T14:43:20Z Using obfuscation key for /home/bitcoin-dev/.bitcoin/testnet3/chainstate: 2686d59caeb1917c 2019-05-06T14:43:20Z Loaded best chain: hashBestChain=00000000b3b6a5db140b6058b7abe5cb00d8af61afd2a237ae3468cd36e387fa height=927391 date=2016-09-08T15:04:00Z progress=0.311180 2019-05-06T14:43:20Z init message: Rewinding blocks... 2019-05-06T14:43:29Z init message: Verifying blocks... 2019-05-06T14:43:29Z Verifying last 6 blocks at level 3 2019-05-06T14:43:29Z [0%]...[16%]...[33%]...[50%]...[66%]...[83%]...[99%]...[DONE]. 2019-05-06T14:43:29Z No coin database inconsistencies in last 6 blocks (500 transactions) 2019-05-06T14:43:29Z block index 19450ms 2019-05-06T14:43:29Z Opening LevelDB in /home/bitcoin-dev/.bitcoin/testnet3/indexes/txindex 2019-05-06T14:43:30Z Opened LevelDB successfully 2019-05-06T14:43:30Z Using obfuscation key for /home/bitcoin-dev/.bitcoin/testnet3/indexes/txindex: 0000000000000000 2019-05-06T14:43:30Z init message: Loading wallet... 2019-05-06T14:43:30Z txindex thread start 2019-05-06T14:43:30Z [default wallet] nFileVersion = 170100 2019-05-06T14:43:30Z [default wallet] Keys: 2005 plaintext, 0 encrypted, 2005 w/ metadata, 2005 total. Unknown wallet records: 1 2019-05-06T14:43:30Z Syncing txindex with block chain from height 694205 2019-05-06T14:43:30Z [default wallet] Wallet completed loading in 123ms 2019-05-06T14:43:30Z [default wallet] setKeyPool.size() = 2000 2019-05-06T14:43:30Z [default wallet] mapWallet.size() = 7 2019-05-06T14:43:30Z [default wallet] mapAddressBook.size() = 4 2019-05-06T14:43:30Z mapBlockIndex.size() = 1515581 2019-05-06T14:43:30Z nBestHeight = 927391 2019-05-06T14:43:30Z torcontrol thread start 2019-05-06T14:43:30Z Bound to [::]:18333 2019-05-06T14:43:30Z Bound to 0.0.0.0:18333 2019-05-06T14:43:30Z init message: Loading P2P addresses... 2019-05-06T14:43:30Z Loaded 10420 addresses from peers.dat 36ms 2019-05-06T14:43:30Z init message: Loading banlist... 2019-05-06T14:43:30Z Loaded 0 banned node ips/subnets from banlist.dat 29ms 2019-05-06T14:43:30Z init message: Starting network threads... 2019-05-06T14:43:30Z net thread start 2019-05-06T14:43:30Z dnsseed thread start 2019-05-06T14:43:30Z addcon thread start 2019-05-06T14:43:30Z msghand thread start 2019-05-06T14:43:30Z init message: Done loading 2019-05-06T14:43:30Z opencon thread start 
After all that appears above, there are just "UpdateTip", "Requesting block", "received block" and "getdata" messages. (so the P2P port, 18333, works).

And here is when I netstat:

sudo netstat -nap|grep bitcoin|grep LISTEN
tcp 0 0 0.0.0.0:18333 0.0.0.0:* LISTEN 31185/bitcoind tcp6 0 0 :::18332 :::* LISTEN 31185/bitcoind tcp6 0 0 :::18333 :::* LISTEN 31185/bitcoind 
Thank you in advance!

PS: A few days ago I could make it work when running bitcoind with root user, but now even that won't solve the problem.
submitted by VicPietro to Bitcoin [link] [comments]

*help* moving wallet folder to a larger HDD, but keeps taking up space on my small SSD

i tried moving the folder to the new larger HDD, but in the process i got a BSOD, and now when i start the bitcoin-qt it starts downloading the entire chain on my C drive, a small SSD (that doesn't have enough space for the blockchain), and i can't figure out how to get it to download it do my 2TB free HDD.
submitted by time2fly2124 to Bitcoin [link] [comments]

Issues with bitcoin-qt

I know this is frequently posted, but I'm incensed at how absurdly slow reindexing becomes. There's got to be something wrong with the sync mechanism.
I was 100% synced a week ago on my MacBook Pro. Latest version of the client (v0.17.0.1). I rsync'd the whole bitcoin dir (blocks, chainstate, index, etc) to another disk, ran a node on another machine using that copy for a couple of hours, then I stopped the node and rsync'd back to the Mac.
Bitcoin-qt did not like the updated blockchain. The other machine didn't like its blockchain either. Oh well, I thought, maybe it didn't shutdown properly and borked the last block. I'll let it reindex, in a few minutes it'll be grand.
But no. Bitcoin-qt decided that it was time to start over from scratch, ignoring the flawless 99.999% of data on disk. Yay.
That was 10 days ago. At one point several days ago it was about 3 hours from finishing, with a progress of around 19% per hour. A day later progress was at 0.25%. This can't be right, I thought, maybe there's a bug, a memory leak or something. I'll shut it down and restart it. Of course it's going to restart from where it left, right? Right?
No. It started from 0% again.
Several days later, it's at 0.14% and predicting it'll finish sometime next week. CPU is 96% idle, RAM is at 25%, bandwidth is 120 Mb/s and the disk is used by bitcoin-qt and nothing else. It's the only thing running on this Mac and has been for the past two weeks. NOTHING is different between 19% and 0.14% in terms of bandwidth, CPU, RAM, or disk I/O. This very machine, under the exact same conditions, was able to process 19% of the blockchain in one hour.
In the meantime, I can't move my BTC because my wallet, which has all the blocks including the ones containing the transactions with my BTC in them, doesn't believe the blocks are there.
Bitcoin-qt is broken in more ways than one. First, something is causing this absurd variation in performance. Second, it's not saving state, which is particularly painful when it takes ages to get to the end to the blockchain. Is state only kept in RAM? I've seen other threads suggesting a change in the config (dbcache seems to be the main one), but I can't just change the setting without restarting, and restarting is not an option because I'll lose everything again.
Sorry, this is extremely frustrating. I'm thinking of extracting the private key and abandoning the idea of running my own wallet. It's unusable.
submitted by jungle to Bitcoin [link] [comments]

Tι είναι Ransomware ; 13 απλές απαντήσεις

Tι είναι Ransomware ; 13 απλές απαντήσεις

Tι είναι Ransomware ;

Ας ξεκινήσουμε από τα βασικά, στο παρακάτω άρθρο σας δίνουμε 13 απαντήσεις για το τι είναι Ransomware.
Οι Ransomware είναι κακόβουλα λογισμικά τα οποία επιτίθενται και κρυπτογραφούν τα δεδομένα του θύματός τους, ενώ στη συνέχεια ζητούν την πληρωμή λύτρων με μορφή Bitcoin για την αποκρυπτογράφηση.

https://preview.redd.it/0j9s33vr4jl31.jpg?width=640&format=pjpg&auto=webp&s=6fd5cbfb3222b26273eb79a75cd61dc814683006
Με την έξαρση που παρουσιάζουν οι επιμολύνσεις από τους Ransomware τα τελευταία χρόνια, ακόμα και οι πιο έμπειροι χρήστες μπορεί να την πατήσουν, πόσο μάλλον οι λιγότερο εξοικειωμένοι.
Χρησιμοποιούμε όλες τις διαθέσιμες τεχνικές για να μπορέσουμε να αποκρυπτογραφήσουμε τα δεδομένα που έχουν επιμολυνθεί, όμως κάποιες φορές ερχόμαστε στη δυσάρεστη θέση να ενημερώσουμε τους πελάτες μας ότι ούτε κι εμείς πλέον μπορούμε να κάνουμε κάτι για να τους βοηθήσουμε.

Τι κάνουν οι ιοί Ransomware ;

Για να μην βρισκόμαστε συχνά σε αυτή τη δυσάρεστη θέση, ετοιμάσαμε έναν οδηγό για να βοηθήσουμε – ενημερώσουμε όλους τους ενδιαφερόμενους για τον τρόπο με τον οποίο μπορούν να αποφύγουν τις επιθέσεις των Ransomware στο καλύτερο τoυλάχιστον δυνατό ποσοστό.
Ακολουθώντας αυτά τα βήματα, θα μπορείτε να θωρακίσετε τον Η/Υ σας και κατ'επέκταση τον εαυτό σας, τα δεδομένα σας, τη δουλειά σας και τους αγαπημένους σας από δυσάρεστα γεγονότα.
Σας προτείνουμε να ακολουθήσετε πιστά αυτόν τον οδηγό. Αν σας φαίνεται μεγάλος ή πολύπλοκος, ζητήστε από κάποιον με περισσότερη εμπειρία να σας βοηθήσει σε αυτά τα πρώτα βήματα.

Πως λειτουργούν οι Ransomware ; Βίντεο !

Στο παρακάτω βίντεο μπορείτε να δείτε αναλυτικά πως λειτουργεί ο Ransomware Petya και να καταλάβετε τι δεν πρέπει να κάνετε ή τι να αναγνωρίσετε αν κάτι τέτοιο συμβεί στον υπολογιστή σας.
Παρακάτω σας αναφέρουμε όλα όσα πρέπει να κάνετε για να μην κινδυνεύετε...
από τους ιούς κρυπτογράφησης καθώς και σας αναλύουμε όλα τα βήματα για να προστατέψετε και τους υπολογιστές του γραφείου σας ώστε να μην χρειαστεί να πληρώσετε τα λύτρα που σας ζητάει ο Ransomware ιός σε bitcoin.

Πως μπορεί να μολυνθεί ο υπολογιστής από Ransomware ;

Σας αναφέρουμε αναλυτικά 13 απλές απαντήσει για το πως μπορεί να μολυνθεί ο υπολογιστής σας.
1) ΚΑΝΟΝΑΣ ΠΡΩΤΟΣ:

> Έχετε Backup ;

Δεν χρειάζεται να πούμε πολλά εδώ, είναι ο βασικότερος κανόνας τον οποίο θα πρέπει να ακολουθείτε ανεξαρτήτως αν κινδυνεύετε να επιμολυνθείτε από Ransomware ή όχι. Στην περίπτωση που έχετε πρόσφατο backup και επιμολυνθείτε από Ransomware, το μόνο που έχετε να κάνετε είναι να απομακρύνετε την επιμόλυνση και να επαναφέρετε τα δεδομένα σας από το backup.
Δυστυχώς η απλή προσθήκη ενός σκληρού δίσκου στον Η/Υ σας και τήρηση των backup εκεί κάθε τόσο, δεν είναι αρκετή. Ο λόγος είναι ότι τα Ransomware θα στοχεύσουν σε όλους τους τοπικούς δίσκους του Η/Υ και σε όλους τους δικτυακούς δίσκους (πολλές φορές και σε αυτούς που δεν έχουν γίνει map). Αυτό σημαίνει ότι τα backup σε τοπικά και απομακρυσμένα μέσα θα κρυπτογραφηθούν επίσης.

https://preview.redd.it/n0tosf3t4jl31.jpg?width=900&format=pjpg&auto=webp&s=0084ab98188c325bd4f8a199fe099984552e446d
Οι λύσεις σε αυτήν την περίπτωση είναι δύο: α) Τήρηση του backup σε Cloud με ό,τι αυτό συνεπάγεται (κόστος, πρόβλημα με την εχεμύθεια, αργή πρόσβαση)
β) Τήρηση του backup σε έναν δίσκο ο οποίος δεν είναι στο δίκτυο και αποσυνδέεται μετά την ολοκλήρωση του backup από τον Η/Υ.
2) ΚΑΝΟΝΑΣ ΔΕΥΤΕΡΟΣ:

> Έχετε καλό λογισμικό προστασίας ;

Σιγουρευτείτε ότι ο Η/Υ σας προστατεύεται από αξιόπιστο λογισμικό προστασίας. Προτείνουμε να εγκατασταθούν λογισμικά antivirus, anti-ransomware και anti-exploit τα οποία να έχουν τη δυνατότητα ανάλυσης της συμπεριφοράς του υπολογιστή και να σας ενημερώνουν αν εντοπίσουν μόλυνση από Ransomware, ακόμα και αν αυτοί είναι νέοι (zero day tolerance).

https://preview.redd.it/9jy4juxu4jl31.jpg?width=1200&format=pjpg&auto=webp&s=a253b68e148b9d971868115772e3af3c17e716f9
3) ΚΑΝΟΝΑΣ ΤΡΙΤΟΣ:

> Έχετε τις ενημερώσεις του λειτουργικού συστήματος στην ώρα τους

Οι πιο πολλοί Ransomware εγκαθίστανται μέσω scripts τα οποία ονομάζονται exploit kits. Αυτά στοχεύουν σε αδυναμίες και τρύπες ασφαλείας του λειτουργικού συστήματος του Η/Υ (πχ. των Windows). Αν λαμβάνετε ειδοποίηση από τα Windows ότι υπάρχουν ενημερώσεις, εγκαταστήστε τις. Πολλές από αυτές τις ενημερώσεις αφορούν την ασφάλεια και σας προστατεύουν από κενά ασφαλείας, τα οποία θα προστατεύσουν τον Η/Υ από το να εκτελεί εντολές του επιτιθέμενου.

https://preview.redd.it/i8q7abtv4jl31.jpg?width=1048&format=pjpg&auto=webp&s=ece549533d37c64feec5e9672895963436373c18
Η Microsoft δημοσιεύει ενημερώσεις στο Patch Tuesday, το οποίο είναι κάθε δεύτερη Τρίτη κάθε μήνα, οπότε να είστε έτοιμοι να κάνετε αυτές τις ενημερώσεις και να επανεκκινήσετε τον Η/Υ σας εκείνη τη στιγμή για να ισχύσουν άμεσα οι αλλαγές.
Τα υπόλοιπα λειτουργικά συστήματα, όπως τις Apple ή οι διανομές Linux δημοσιεύουν ενημερώσεις όποτε αυτές είναι απαραίτητες. Να είστε προετοιμασμένοι να τις εγκαταστήσετε μόλις δημοσιευτούν για να εκμηδενίσετε τις πιθανότητες επιμόλυνσης.
4) ΚΑΝΟΝΑΣ ΤΕΤΑΡΤΟΣ:

> Διατηρείτε τα εγκατεστημένα προγράμματα ενημερωμένα ;

Ακριβώς όπως με τα λειτουργικά συστήματα, τα exploit kits στοχεύουν σε κενά ασφαλείας σε κοινώς χρησιμοποιούμενα λογισμικά και προγράμματα του Η/Υ, όπως η Java, ο Adobe Flash Player, o Adobe Reader και άλλα.
Επομένως είναι απολύτως αναγκαίο να τηρείτε τα εγκατεστημένα προγράμματα ενημερωμένα.
https://preview.redd.it/d9gjl70x4jl31.jpg?width=1199&format=pjpg&auto=webp&s=68958eae0b52ec56a158799d3d8852ca8fc3f531
Για Windows, προτείνουμε το Flexera Personal Software Inspector, το οποίο θα κάνει έλεγχο των εγκατεστημένων προγραμμάτων και λογισμικών και θα σας ενημερώνει όταν υπάρχουν ανανεώσεις. UPDATE: Μιας και το Flexera πλέον δεν είναι διαθέσιμο, προτείνουμε το FileHippo App Manager το οποίο είναι δωρεάν.
Για Mac, προτείνουμε το MacUpdate Desktop, το οποίο όμως δεν είναι δωρεάν.
5) ΚΑΝΟΝΑΣ ΠΕΜΠΤΟΣ:

> Τα φίλτρα SPAM σας είναι λειτουργικά ;

Ίσως η πιο διαδεδομένη μέθοδος διασποράς Ransomware είναι μέσω SPAM emails τα οποία παριστάνουν πως είναι δελτία αποστολής, τιμολόγια, βιογραφικά σημειώματα κλπ.

https://preview.redd.it/o3486a7y4jl31.jpg?width=605&format=pjpg&auto=webp&s=b39508882eb7dcda29edc88ff70bfa409293eee0
Αν χρησιμοποιείτε web mail παρόχους όπως η Gmail, η Yahoo και η Hotmail, τότε τα περισσότερα από αυτά τα email φιλτράρονται πριν φτάσουν στο Inbox σας.
Δυστυχώς αν έχετε δικό σας domain και η υπηρεσία του SPAM filtering δεν λειτουργεί σωστά, πολλά από αυτά τα email θα καταλήξουν στα εισερχόμενά σας.
6) ΚΑΝΟΝΑΣ EKTOΣ:

> Ενεργοποιήσατε την προβολή των επεκτάσεων των αρχείων ;

Ως προεπιλογή, τα Windows και τα MacOS δεν δείχνουν την επέκταση των αρχείων όταν περιηγείστε σε έναν φάκελο. Αυτό βοηθάει τους επιτιθέμενους στο να ξεγελάσουν τον χρήστη κάνοντας τον να νομίζει ότι ένα εκτελέσιμο αρχείο είναι στην πραγματικότητα ένα πιο οικείο αρχείο όπως ένα αρχείο Word, Excel ή PDF. Το θύμα θα ανοίξει το αρχείο περιμένοντας να δει περιεχόμενο, όμως στην πραγματικότητα αυτό που κάνει είναι να εκτελεί το αρχείο που θα εγκαταστήσει το Ransomware.
https://preview.redd.it/1x1988fz4jl31.jpg?width=640&format=pjpg&auto=webp&s=3658c3b8f39fcf9f1bee3b7306cc3f4091df2359
Στην παραπάνω εικόνα φαίνεται ένα παράδειγμα όπου ένα κακόβουλο εκτελέσιμο αρχείο (.exe) παριστάνει ότι είναι .pdf. Με την ενεργοποίηση της προβολής των επεκτάσεων βλέπουμε την πραγματική του ταυτότητα (.pdf.exe).
7) ΚΑΝΟΝΑΣ ΕΒΔΟΜΟΣ:

> Ανοίξατε επισυναπτόμενα αρχεία που δεν γνωρίζετε την προέλευσή τους ;

📷Με την επιμόλυνση από Ransomware μέσω SPAM email, είτε η ίδια η επιμόλυνση είτε ο downloader μέσω του οποίου κατεβαίνει η επιμόλυνση στον Η/Υ σας, βρίσκεται στα επισυναπτόμενα.
Αν λάβετε ένα email που περιέχει επισυναπτόμενο και δεν γνωρίζετε είτε γιατί το έστειλαν σε εσάς, είτε τον αποστολέα, μην το ανοίξετε.
📷
Στην παρακάτω εικόνα φαίνεται ένα email με επισυναπτόμενο το οποίο περιέχει τον Locky Ransomware. Όπως βλέπουμε, έχει ένα .xls επισυναπτόμενο (άρα φαινομενικά αθώο) και μας παρακινεί να το ανοίξουμε για να δούμε το τιμολόγιο που μας αποστέλλει κάποιος.
Αν κάνετε το λάθος και ανοίξετε το επισυναπτόμενο και δείτε μία προτροπή να ενεργοποιήσετε τις μακροεντολές ή το περιεχόμενο (Enable Macros ή enable Content), μην το κάνετε, γιατί αυτό θα κατεβάσει τον Ransomware στον Η/Υ σας και θα ξεκινήσει την επιμόλυνση.
8) ΚΑΝΟΝΑΣ ΟΓΔΟΟΣ:

> Προσέχετε τι κατεβάζετε και από που ;

Τα δωρεάν downloads από το Internet, από Torrents και από P2P συνδέσεις μπορεί να ακούγονται δελεαστικά, όμως συχνά κρύβουν δυσάρεστες Ransomware εκπλήξεις.
Να προσέχετε πάντα να κατεβάζετε από ιστοσελίδες που εμπιστεύεστε και να προσέχετε που πατάτε ΟΚ.
9) ΚΑΝΟΝΑΣ ΕΝΑΤΟΣ:

> Μετονομάσατε το vssadmin στα Windows ;

Τα Shadow Copies χρησιμοποιούνται από τα Windows για να αποθηκεύουν αυτόματα Backup ή προηγούμενες εκδόσεις των αρχείων. Αυτά τα backup βοηθάνε στο να ανακτώνται δεδομένα που έχουν μεταβληθεί ή αλλοιωθεί.
https://preview.redd.it/joy6nmx15jl31.jpg?width=960&format=pjpg&auto=webp&s=29d0049bc51bc59697bebbcd7a14a3df53b2576a
Δυστυχώς οι δημιουργοί των Ransomware είναι αρκετά καλοί γνώστες αυτής της λειτουργίας, με αποτέλεσμα μία από τις πρώτες ενέργειες που κάνουν μόλις ξεκινήσει η επιμόλυνση είναι η διαγραφή όλων εκδόσεων των shadow copies εκτελώντας την εντολή vssadmin.exe.
Αν δεν έχετε λογισμικά που βασίζονται στο vssadmin προτείνουμε να το μετονομάσετε.
Για να μετονομάσετε το vssadmin θα πρέπει να “τρέξετε” το παρακάτω script:
@echo off
REM We are redirecting the output of the commands and any errors to NUL.
REM If you would like to see the output, then remove the 2>NUL from the end of the commands.
REM Check if vssadmin.exe exists. If not, abort the script
if NOT exist %WinDir%\system32\vssadmin.exe (
echo.
echo.%WinDir%\system32\vssadmin.exe does not exist!
echo.
echo Script Aborting!
echo.
PAUSE
goto:eof
)
REM Check if the script was started with Administrator privileges.
REM Method from http://stackoverflow.com/questions/4051883/batch-script-how-to-check-for-admin-rights
net session >nul 2>&1
if %errorLevel% NEQ 0 (
echo.
echo You do not have the required Administrator privileges.
echo.
echo Please run the script again as an Administrator.
echo.
echo Script Aborting!
echo.
PAUSE
goto:eof
)
REM We need to give the Administrators ownership before we can change permissions on the file
takeown /F %WinDir%\system32\vssadmin.exe /A >nul 2>&1
REM Give Administrators the Change permissions for the file
CACLS %WinDir%\system32\vssadmin.exe /E /G "Administrators":C >nul 2>&1
REM Generate the name we are going to use when rename vssadmin.exe
REM This filename will be based off of the date and time.
REM http://blogs.msdn.com/b/myocom/archive/2005/06/03/so-what-the-heck-just-happened-there.aspx
for /f "delims=/ tokens=1-3" %%a in ("%DATE:~4%") do (
for /f "delims=:. tokens=1-4" %%m in ("%TIME: =0%") do (
set RenFile=vssadmin.exe-%%c-%%b-%%a-%%m%%n%%o%%p
)
)
REM Rename vssadmin.exe to the filename in the RenFile variable
ren %WinDir%\system32\vssadmin.exe %RenFile% >nul 2>&1
REM Check if the task was completed successfully
if exist %WinDir%\system32\%RenFile% (
echo.
echo vssadmin.exe has been successfully renamed
echo to %WinDir%\system32\%RenFile%.
pause
) else (
echo.
echo There was a problem renaming vssadmin.exe
echo to %WinDir%\system32\%RenFile%.
echo.
pause
)
:END
10) ΚΑΝΟΝΑΣ ΔΕΚΑΤΟΣ:

> Απενεργοποιήσατε το Windows Script Host ;

📷
Πολλές Ransomware επιμολύνσεις εγκαθίστανται μέσω επισυναπτόμενων τα οποία είναι script γραμμένα σε JS ή VBS.
  • Αν γνωρίζετε τι είναι αυτά, έχει καλώς.
  • Αν όχι, προτείνουμε να απενεργοποιήσετε τη δυνατότητα εκτέλεσης τέτοιων αρχείων στα Windows.
Για να το κάνετε αυτό, ακολουθήστε τις οδηγίες της Microsoft από εδώ:
https://technet.microsoft.com/en-us/library/ee198684.aspx
📷
Αν το κάνετε αυτό και προσπαθήσει να εκτελεστεί script τέτοιου τύπου, θα λάβετε αυτήν την ειδοποίηση:
11) ΚΑΝΟΝΑΣ ΕΝΔΕΚΑΤΟΣ:

> Απενεργοποιήσατε το Windows Powershell ;

📷
Ομοίως με προηγουμένως, το PowerShell χρησιμοποιείται από τους επιτιθέμενους με σκοπό την εγκατάσταση των Ransomware ή ακόμα και την κρυπτογράφηση αρχείων.
Αν δεν το χρησιμοποιείτε, απενεργοποιήστε το.
Για να το κάνετε αυτό, πηγαίνετε Έναρξη> Γράψτε CMD> Enter
και δώστε την ακόλουθη εντολή στο Command Prompt
powershell Set-ExecutionPolicy -ExecutionPolicy Restricted
Αν θέλετε να το ενεργοποιήσετε και πάλι, μπορείτε να αλλάξτε από την παραπάνω εντολή το Restricted σε Unrestricted.
12) ΚΑΝΟΝΑΣ ΔΩΔΕΚΑΤΟΣ:

> Χρησιμοποιείτε πολύπλοκους κωδικούς ασφαλείας ;

Πάντα να χρησιμοποιείτε πολύπλοκους, δύσκολους κωδικούς.
Ξεχάστε τα 12345, 0000, 15101969 κ.ο.κ.
Αντ'αυτών, χρησιμοποιείτε κωδικούς όπως [email protected]Υ!&87kM-=^
13) ΚΑΝΟΝΑΣ ΔΕΚΑΤΟΣ ΤΡΙΤΟΣ:

> Απενεργοποιήσατε το Remote Desktop των Windows ;

> Αλλάξατε την προεπιλεγμένη θύρα του ;

Αν δεν χρησιμοποιείτε το Remote Desktop, απενεργοποίηστε το. Είναι ένας από τους πιο διαδεδομένους τρόπους εισβολής στον Η/Υ σας.
https://preview.redd.it/h9qtdei45jl31.png?width=683&format=png&auto=webp&s=d3b4a3e589dfd72809c3d46fc58003d83198d79f
Αν το χρησιμοποιείτε και το χρειάζεστε, αλλάξτε την θύρα που χρησιμοποιεί για την επικοινωνία με τον έξω κόσμο.
Για να το κάνετε αυτό: Έναρξη > Γράψτε REGEDIT > Enter
Στο παράθυρο που θα ανοίξει πηγαίνετε στο:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp και βρείτε την εγγραφή PortNumber στην δεξιά πλευρά του παραθύρου. Με διπλό κλικ επιλέξτε το, και στο παράθυρο που θα σας ανοίξει επιλέξτε Decimalαλλάξτε το Value Data από 3389 σε ό,τι θέλετε εσείς.
ΣΥΝΟΨΗ Tι είναι Ransomware ; 13 απλές απαντήσεις
Ακολουθώντας αυτές μας τις οδηγίες θα έχετε θωρακίσει τον Η/Υ σας σε τεράστιο βαθμό.

https://preview.redd.it/916d8ck35jl31.jpg?width=1754&format=pjpg&auto=webp&s=fc9655bc99df47d935e99967a7086ee14fe9e5ad
Στην δυσάρεστη περίπτωση που έχετε μολυνθεί από Ransomware,
ΜΗ ΠΛΗΡΩΣΕΤΕ ΤΑ ΛΥΤΡΑ ΚΑΙ ΕΛΑΤΕ ΣΕ ΕΠΙΚΟΙΝΩΝΙΑ ΜΑΖΙ ΜΑΣ ΑΜΕΣΑ!
Αν θέλετε να κατεβάσετε τον οδηγό επιβίωσης
πατήστε εδώ...
submitted by DataRecoveryGreece to greektech [link] [comments]

Configure correctly CMake with sumbodule project github and C++

Hy Guys,

I'm java programmer and I'm learning a C++ with CMake with a my project on Bitcoin core, now If want use the submodule GitHub for configuring my external project but I want to include the submodule correctly in the my CMake file configuration, can you help me to understand this?

cmake_minimum_required(VERSION 3.9) project(SpyCBlock) set(CMAKE_CXX_STANDARD 17) # Locate GTest enable_testing() find_package(GTest REQUIRED) include_directories(${GTEST_INCLUDE_DIRS}) #Glog find_package(glog 0.3.5 REQUIRED) ## Json library find_package(nlohmann_json 3.2.0 REQUIRED) # Link runTests with what we want to test and the GTest and pthread library add_executable( SpyCBlockTests test/StructureBitcoinCoreTest.cpp test/DAOBlockchainTest.cpp test/SHABitcoinCoreTest.cpp test/SerealizationTest.cpp test/JsonSerializationTest.cpp test/DAOBlkToJsonTest.cpp test/DAOJsonTest.cpp test/NullDataTransactionsTest.cpp test/ExceptionCompactsizeTest.cpp test/ConfiguratorSingletonTest.cpp util/uint256.cpp util/strencodings.cpp util/prevector.cpp cryptobitcoin/Sha256.cpp cryptobitcoin/Sha256Hash.cpp cryptobitcoin/Utils.cpp structure/block/block.cpp structure/block/blockHeader.cpp structure/transaction/RawTransaction.cpp structure/transaction/TransactionOutput.cpp structure/transaction/TransactionInput.cpp structure/script/scriptCode.cpp structure/type/Outpoint.cpp structure/type/DVarInt.cpp structure/type/DScript.cpp structure/type/Outpoint.cpp persistence/DAOBlockchain.cpp persistence/DAOException.cpp persistence/json/DAOBlkToJson.cpp persistence/json/DAOJson.cpp persistence/SerializationUtil.cpp crypto/UtilCrypto.cpp crypto/CryptoCore.cpp core/ConfiguratorSingleton.cpp #cpp-properties file include include/cpp-properties/src/Properties.cpp include/cpp-properties/src/PropertiesParser.cpp include/cpp-properties/src/PropertiesUtils.cpp #rapidjson include/rapidjson/include/rapidjson/writer.h ) add_executable( ${PROJECT_NAME} core/ParserMain.cpp core/SpyCBlock.cpp core/ConfiguratorSingleton.cpp util/uint256.cpp util/strencodings.cpp util/prevector.cpp structure/block/block.cpp structure/block/blockHeader.cpp structure/transaction/RawTransaction.cpp structure/transaction/TransactionOutput.cpp structure/transaction/TransactionInput.cpp structure/script/scriptCode.cpp structure/type/Outpoint.cpp structure/type/DVarInt.cpp structure/type/DScript.cpp structure/type/Outpoint.cpp persistence/DAOException.cpp persistence/DAOBlockchain.cpp persistence/DAOException.cpp persistence/SerializationUtil.cpp persistence/json/DAOBlkToJson.cpp persistence/json/DAOJson.cpp crypto/UtilCrypto.cpp crypto/CryptoCore.cpp cryptobitcoin/Sha256.cpp cryptobitcoin/Sha256Hash.cpp cryptobitcoin/Utils.cpp #cpp-properties file include include/cpp-properties/src/Properties.cpp include/cpp-properties/src/PropertiesParser.cpp include/cpp-properties/src/PropertiesUtils.cpp ) #using glog target_link_libraries(${PROJECT_NAME} glog::glog) target_link_libraries(SpyCBlockTests glog::glog) #using gtest target_link_libraries(SpyCBlockTests ${GTEST_LIBRARIES} pthread) ##using filesystem target_link_libraries(${PROJECT_NAME} stdc++fs) target_link_libraries(SpyCBlockTests stdc++fs) ##Json library target_link_libraries(${PROJECT_NAME} nlohmann_json::nlohmann_json) 

The Cmake work, but I think is a bad configuration.
cpp-properties is a submodule and its location is /include/cpp-properties

ps: Sorry my more questions today
submitted by crazyjoker96 to cpp_questions [link] [comments]

WSB101 - THE BOOK OF YOLO: BEGINNERS GUIDE TO TRADING LIKE A DEGENERATE AND EVERYTHING WSB

The Book of Yolo: COMPLETE GUIDE TO WSB
The goal of this is to actually create something that all of you WSB newbies can read - because we’re all tired of seeing the endless wave of uninformed and unavoidable stupidity from those who have never touched the stock market. CALLING ALL NEWFAGS AND NORMIES.
If you can’t read, GFY now.
Now that we will be on the popular section of reddit, this has become pertinent. WSB can't avoid newcomers, so we might as well explain how the clock ticks here. This one is for you all.
This is to serve as a reference what values we hold, what instruments we use, and as a general place to educated the uneducated.
First off, this is the LEAST helpful stock market-based community for newcomers. Sarcastic answers are the only thing of true value here. It isn't a place to learn, but a place to plan out where you will dock your yacht. Newcomers are usually berated upon asking the inevitable stupid questions that they could learn slowly from reading here, or just using a damn search engine. Instead of embarrassing yourself here, you now have the opportunity to read this and get what we’re all rambling about.
This will help you understand what to expect if you make the decision to undertake a WSB style trading career, so you can stay here and contribute to the yolo lifestyle or otherwise GFY.
I will edit in any suggestions that our frequenting users or mods want to add to this as well.
To begin: Here are our topics for WSB101
-Basics (Equities/Stocks)
;
-ETF's
;
-Options
;
-Futures Trading
;
-SubCulture
;
BASICS/EQUTIES Skip if you understand basic stock stuff
Okay, so what is an equity/stock? An equity is essentially what you’d think of as your “vanilla” trading tool. They move up or down depending on market forces, and can range from pennies to thousands of dollars per share. To explain how stocks work, let's define a few terms.
Volume: The number of shares of stock traded during a particular time period, normally measured in average daily trading volume.
Spread: The difference between the bid and the ask price
Bid Price: The current price in which someone wants to buy at
Ask Price:The current price in which someone wants to sell at
Volatility: The WSB favorite. Volatility is referring to the price movements of a stock as a whole. The higher the volatility, the more the stock is moving up or down. Highly volatile stocks are ones with extreme daily up and down movements and wide intraday trading ranges.
Margin: A margin account lets a person borrow money (take out a loan essentially) from a broker to purchase an investment. The difference between the amount of the loan, and the price of the securities, is called the margin. Margin is one of WSB’s popular instruments of wealth and destruction.
Dividend: This is a portion of a company’s earnings that is paid to shareholders, or people that own hat company’s stock, on a quarterly or annual basis. Not all companies do this.
PPS: Acronym for “Price per Share”
Moving Average: A stock’s average price-per-share during a specific period of time.
Bullish: Expecting the stock to go up
Bearish: Expecting the stock to go down
Any raised hands can redirect themselves to here:
http://www.investopedia.com/articles/investing/082614/how-stock-market-works.asp?ad=dirN&qo=investopediaSiteSearch&qsrc=0&o=40186
Now that these terms are defined, let's move into the details of why this is even useful. Most people know what a stock is, but how and why stocks move is a different story. The stock market is essentially a big virtualization of supply and demand - meaning that usually high positive volume creates upwards movement in the PPS, where high negative volume does the opposite. This creates a trader’s opportunity; Generally, the most effective time to buy or sell is where the candlesticks (volume data) are thinning out. When you are ready to take an entry point or execute an exit point, waiting till the volatility (candlesticks) thin out is one method to give you best trade possible.
WSB FAVORITE EQUITIES: Of many equities, WSB favors the riskier ones - but avoiding penny stocks is a policy.
AMD - CEO Lisa Su, Next Gen Processors, chips, graphics. It’s the gamers gambit. Up roughly 1400% as of 2/7/2017 since WSB first mentioned it
NVDA - AMD’s sister? Mother? Daddy? Who knows. NVDA has been a sexy semiconductor leader. Is up 400% since gaining traction on WSB.
FNMA / pfds - Mnunchin, Trump, Big fat fannies. Get your self deep in the fannie. We all want it. WSB 10 bagger candidate for reforming the housing market. WSB holds a large cumulative position that can be seen below. Also a good read is the beginners guide to FNMA. Any post by u/NOVACPA is very often VERY informative on FMNA/pfds.
https://www.reddit.com/wallstreetbets/comments/5oissp/results_wsb_fnmafmcc_holdings
https://www.reddit.com/wallstreetbets/comments/5t7gba/beginngers_guide_to_fnma_fmcc_read_this_before/
ARRY - A biotech champion that prevailed after a lot of failures and huge losses in the biotech sector. Dark times for WSB. Up ~300% since getting traction on the subreddit.
TWTR - WSB likes to buy put option contracts on her. Exemplary of a social media platform that is unable to monetize itself.
TSLA - Maybe not unanimously a favorite, but loved for it’s sexy volatility, Elon Musk, and ridiculously expensive options.
GILD - A Shkreli pump and dump? The greatest large cap pharma recovery of all time? Who knows. Martin took the time to make a post on this reddit and it is up $5 dollars since.
ETF'S
Welcome to the world of investing made easy. Exchange traded funds (etfs) are devices that can be traded like stocks, but often track the value of many companies by investing in their listed assets accordingly. Specifically, An ETF, or exchange traded fund, is a marketable security that tracks an index, a commodity, bonds, or a basket of assets like an index fund. Unlike mutual funds, an ETF trades like a common stock on a stock exchange. ETFs experience price changes throughout the day as they are bought and sold. ETFs typically have higher daily liquidity and lower fees than mutual fund shares, making them an attractive alternative for individual investors.
ETF’s come in beautiful and delicious varieties, often with a BEAR form and a BULL form of each; but the most delicious to WSB are the 3x etf’s. A 3x ETF is one in which the underlying movement of the ETF is leveraged 3:1. Meaning for every movement within the underlying index or stocks, the 3x ETF moves well.... 3x as much..
WSB FAVORITE AND USEFUL ETF’S:
JNUG - 3x Gold Miner Bull - A hit or miss, has extreme intraday movements and essentially tracks GDX (gold miner’s index). Jnug will usually move with a pretty strong correlation to gold, which is affected by the mentioning of rate hikes (negatively), movement of the US dollar (inversely), uncertainty (positively), and supply and demand.
NUGT - Jnug with a different price tag
JDST - The inverse 3x etf of JNUG - or the bear etf. It does almost exactly the opposite movements of JNUG by the tick. Moves for the same reasons, but obviously opposite directions.
DUST - Jdst with a different price tag.
UGAZ - Natural Gas 3x Bull ETF - essentially tracks the price value of the commodity Natural Gas, but more specifically the S&P GSCI Natural Gas Index ER. The index comprises futures contracts on a single commodity and is calculated according to the methodology of the S&P GSCI Index. Natural gas is most affected by Weather temperature conditions (use your brain), petroleum prices, and broader economic conditions.
DGAZ - Inverse of UGAZ
UWT - Crude Oil Bull 3x ETF - extreme intraday movements, closely follows the price of oil. More specifically, it tracks futures. UWT seeks to replicate, net of expenses, three times of the S&P GSCI® Crude Oil Index ER. The index tracks a hypothetical position in the nearest-to-expiration NYMEX light sweet crude oil futures contract, which is rolled each month into the futures contract expiring in the next month. The value of the index fluctuates with changes in the price of the relevant NYMEX light sweet crude oil futures contracts.
DWT - Inverse of UWT
FAS - Financial Bull, specifically FAS seeks daily investment results, before fees and expenses, of 300% of the performance of the Russell 1000 ® Financial Services Index. The fund creates long positions by investing at least 80% of its assets in the securities that comprise the Russell 1000 ® Financial Services Index and/or financial instruments that provide leveraged and unleveraged exposure to the index. Can be used when bullish on US financial services - so banks, lenders, etc.
FAZ - Inverse of FAS
UPRO - S&P500 Bull 3x ETF, essentially tracks the S&P500 and multiplies it’s returns by 3x.
BRZU - Tracks Brazil (in its most basic form). It creates long positions in the MSCI Brazil 25/50 Index.
LABU - Tracks the Biotech sector, or specifically 300% of the performance of the S&P Biotechnology Select Industry Index ("index"). It should be noted that LABU has doubled since just before the election of Donald Trump.
LABD - Inverse of LABU
RUSL - roughly creates 300% of the performance of the MVIS Russia Index.
RUSS - Inverse of RUSL
SPY - Tracks the S&P500, but is not 3x.
OPTIONS:
Alright, so half you are going to understand this, and half of you are not. Pull up an options chain now on any stock (penny stocks and specific stocks do not have chains because of their market cap). Options are truly the ultimate way to achieve maximum risk/reward.
An option is a contract that gives the buyer the right to buy or sell 100 shares of a stock at a certain price, on a certain date. This concept makes options a commodity themselves.
KEY TERMS:
A CALL - is the right to buy. Buying calls is taking a bullish position in its most extreme form.
A PUT - is the right to sell.
The underlying - is the stock that the option is covering i.e. AAPL, GOOG, AMZN
Strike Price - the price at which a put or call option can be exercised.
ITM, In the money - In the money means that a call option's strike price is below the market price of the underlying asset or that the strike price of a put option is above the market price of the underlying asset. Being in the money does not mean you will profit, it just means the option is worth exercising.
OTM, Out of the money - a call option with a strike price that is higher than the market price of the underlying asset, or a put option with a strike price that is lower than the market price of the underlying asset.
ATM - At the money - Strike price at the same price as the underlying
Expiration - Expiries for options are every friday of every week usually, with exceptions such as every month, or every other day - depending on the underlying. SPY and SPX are great examples of very active option chains with expiries every other day. On the expiry date or any time before (with american options), an option can be, but doesn’t have to be exercised, meaning the holder of the option can use it to buy or sell shares of the underlying stock at the strike price. Most people on WSB do not exercise the contracts, but merely flip them for increases in value as the underlying moves.
For example, when AAPL was at 120 before its earnings report, Joe Shmoe Yolo buys 10 FEB 17th CALLS at strike 127 for .60 , each. Now .60 cents is really 60 dollars each, because the contract is multiplied by 100 (the right to 100 shares). In total, Joe Shmoe Yolo spends $600 dollars + commision on this trade. The next day, AAPL leaps to 130 upon great news. These same option contracts are now worth 3.50 each. $350 dollars per contract, times ten contracts is $3500 dollars. Joe Shmoe Yolo just turned $600 into $3500 dollars. MAGIC. Spoiler alert: Joe Shmoe Yolo was me.
That same Joe Shmoe later buys FEB 17th XOM calls at 90, hoping for similar results. However, XOM ends up never reaching anywhere close to the strike price, and the options expire worthless. Get it?
Now what determines the pricing of options?
OPTION PRICING:
Below is sourced from investopedia
Intrinsic Value: The intrinsic value is the actual value of a company or an asset based on an underlying perception of its true value including all aspects of the business, in terms of both tangible and intangible factors. This value may or may not be the same as the current market value. Additionally, intrinsic value is primarily used in options pricing to indicate the amount an option is in the money.
Time Value: Time Value = Option Price - Intrinsic Value. The more time an option has until it expires, the greater the chance it will end up in the money. The time component of an option decays exponentially. The actual derivation of the time value of an option is a fairly complex equation. As a general rule, an option will lose one-third of its value during the first half of its life and two-thirds during the second half of its life. This is an important concept for securities investors because the closer you get to expiration, the more of a move in the underlying security is needed to impact the price of the option. Time value is basically the risk premium that the option seller requires to provide the option buyer the right to buy/sell the stock up to the date the option expires. It is like an insurance premium of the option; the higher the risk, the higher the cost to buy the option. Makes sense, right?
Time value is determined by the expiration date. An expiration date in derivatives is the last day that an options contract is valid. When investors buy options, the contracts gives them the right but not the obligation, to buy or sell the assets at a predetermined price, called a strike price, within a given time period, which is on or before the expiration date. If an investor chooses not to exercise that right, the option expires and becomes worthless, and the investor loses the money paid to buy it.
Volatility:
In an options pricing, you see IV. This stands for implied volatility. The higher that is, the higher the options will be priced Volatility is the extent to which the return of the underlying asset will fluctuate between now and the option's expiration. Volatility, as expressed as a percentage coefficient within option-pricing formulas, arises from daily trading activities. How volatility is measured will affect the value of the coefficient used.
Decaying Nature of Options:
Decay refers to derivative trading (i.e. options). When you sell or buy a call/put (using those two for simplicity purposes) you don't get an infinite time frame to make your dreams come true. Time is your enemy; the further out the expiration date, the less time decay there is. Time decay really hits the worst the week of expiration. Sound confusing? Say you're buying options of the stock WSB (I hope you're seeing what I did there) - and the option costs $1, the expiration is this Friday. Say today is Monday. You buy a call expecting WSB to take you to the moon and beyond. Each day the stock doesn't move closer to your strike price or remains stagnant/drops, you lose value on your option + the time decay. Meaning if it finishes closer to your strike price, your option could be worthless because of that time decay. Questions? Ask away.
A great example of these factors in action is TSLA.
TSLA’s options are among the most expensive for companies in its price range, why?
An in the money TSLA call expiring this week is worth around $1100 per contract. Insanely expensive. But for a reason. TSLA has extreme intraday movements and calls have an implied volatility of 40.92%. Which is fairly high. In addition to that, it holds high intrinsic value / price per share, and a week of time value.
-Futures 101 - The Ultimate YOLO Guide (thanks to u/IncendiaryGames)
Okay, a lot of you have been YOLOing on faggot delights on SPY options. How would you like to trade something with the same or more leverage, 1.0 delta, and no time premium costs? Have you considered futures? What are futures? Unlike options, futures is a contract where both the buyer and seller is obligated to perform the transaction by the expiration. Conversely, in options, only the seller is obligated to perform. That means you can lose more than your investment. Originally they were used by farmers to sell future crops early and guarantee some amount of sales. Since then futures have expanded not just to commodities but currency and equity indices like the S&P 500. Why the heck would I want to trade futures? Here are the advantages: Leverage $5k is the margin requirement for most contracts. For example with the E-mini S&P 500 with 5k you're trading $120k worth of stuff. 1 contract = 500 spy shares. Some brokers offer intraday daytrading margin rates too - TD Ameritrade is 25% of the overnight margin rate($1,250.) Some brokers go as low as $500 an /ES future. SPAN Margin If 24x overnight leverage and 240x day trade leverage didn't give you a hard on there is also SPAN margin, which is like portfolio margin on steroids. The beauty of SPAN margin is you don't need a $125k+ account to be eligible. SPAN will greatly reduce your margin requirements if you hold uncorrelated or inversely correlated positions (up to an 80% discount, here is a list of groups that give discounts) and if you hedge with options. Hedge with the right option or asset and now you have up to 500x day trading margin. 23/7 and day trading Ever get in and out of an equity only to have your broker yell at you to stop doing that or deposit $25k? There is no pattern day trading restrictions on futures. Feel free to day trade and blow up your account as often as you want! You can also trade 23 hours a day. Get trading on how the S&P 500 index will react to news from China right away. Taxes No matter how long or how short you hold you always get taxed under the 60/40 rule. 60% of your profit from futures will be taxed as a long term gain and 40% will be taxed as short term gain. No wash sales. Trade your hearts out. Just remember holding past Dec 31st will treat you as if you closed all your positions that day and you'll be taxed on unrealized gains. Long/Short No need to pay interest or borrow shares as being short a future contract is being a writer, just like an options writer. Options Of course there are options. What fun would it be without options? Unlike stock options each contract gives different number of future contracts. Research what you're trading.
Ok. I'm convinced. I want to strat trading futures! What are some good strategies?
YOLO Strategies
Swing trading Trying to guess/predict/ride sudden market momentum. A low volume average day in the S&P 500 (/ES) for one contract can swing +- $500. Get it right and you can see a huge appreciation of value. /ES is usually highly liquid during regular hours with average volume of 1 million trades and usually bid-ask spreads of one tick. One approach is to buy or short in your direction and put in a stop loss to an amount you're comfortable to lose (say $200.) Since it's so liquid you'll likely be filled at or near your stop loss during the day if your trade goes against you. If you can guess the direction 50% of the time and have trades like this: trade 1 - gain $800 trade 2 - lose $200 Then you may profit over the time period. If you have a 50% chance of being wrong and losing $200 or 50% chance of being right and gaining $800 then over time you'll gain more than you lose. Also, since the present value of your futures contract is included in your margin calculation then if it goes strongly in your favor your position can quickly grow to cover its own margin and you can let it ride for a while. You'll want to be sure you enter a combo buy/short order along with a stop loss order simultaneously, like this for Thinkorswim. Futures can move suddenly and a sudden movement can make you lose a ton of money. Exploiting outdated SPAN margin guidelines There are several out of date correlations between popular futures like oil and say things like wheat that SPAN gives you margin credits on. Take whatever position you want in oil (/cl) then take the opposite in something that doesn't move much day to day with less volatility such as /w (wheat)) and your /cl and /w positions will get a 75% credit, giving you 50% more buying power on crude oil. (2 positions * .25 = 0.5). Trade your heart out on the more volatile future then when you're done close your safer future pair. SPAN is constantly changing but such a complex system definitely has its exploits. Automated/algorithmic trading For you programmer geeks out there it's really hard to algorithmic trade on small accounts due to pattern day trading rules and economies of scale with broker fees. Futures is probably the best way to get your feet wet. Join us on /algotrading if you want to explore more!
Boring safer strategies
I'm including these for completeness but these belong on /investing. Scalping With high frequency trading scalping is less guaranteed. Basically scalping is using tiny momentum as usually there are small micro patterns in futures buying and selling activity where it will rise or fall a couple of ticks. Since the notional value of each tick is $12.5 it's profitable for retail investors and small accounts to act as a market maker after fees at the smallest bid-ask spread possible. Spreads Just like you can trade spreads in options, you can trade calendar spreads in futures. Futures have contracts with different expiration dates and the prices are different for each month of expiration based on the market's expectations. You can go long or short the near month expiration and the opposite for the far month. This will hedge out any sudden market moves as that would likely affect both months. Bull markets in general tend to increase the price of the near month faster than the far month. Basically with a spread trade you're making a long term bet on bull or bear for the underlying future. Pairs trading You can go long in one future say the dow jones (/ym) and short the S&P 500 index and profit off the relative growth. This is a hedged trade as any market ups or downs will likely affect both positions with the same % value. For the past 180 days /ym - /es has been really profitable. Even if you don't do a full perfect pairs trade it is still a great option to reduce the leverage too on whatever index future you're trading so you can stay in longer or overnight. Interest rate and optimal leverage plays Since the $5k investment is equal to $120k of the S&P 500 index currently then you'll likely beat out the market by buying one future contract and putting $115k in safe treasuries or bonds or uncorrelated assets. Some people choose to leverage their stock portfolio and you can get the exact leverage ratio of liquid investments to future ratios. In probability theory the max leverage you can gain is determined by the Kelly Criterion which modeling shows indicates the S&P 500 index to be leveraged to 1.40x. Yes, you could do the same with options but even on SPY deep in the money call leaps are illiquid and have a time premium. Even today they are so deep ITM that the options you would need to use have 0 open interest and a bid-ask spread of $5 per share (so $500 per contract.) You'd need ~5 contracts per 120k so you're already eating $2.5k/$120k - 2% interest rate a year for that leverage. SPX isn't better, it's bid ask is 22 so you'd be eating $2.2k/$120k - 1.83% interest rate. It's doubtful you won't get much past the ask as its only market makers providing liquidity and guess what the market maker will do if you buy/sell the option? They will hedge with the underlying futures until their minimum profit is the risk free interest rate. Hedging Going long and short in various non correlated or negatively correlated assets to seek out a high sharpe ratio and have a higher risk free return that is market neutral. Basic hedge fund stuff. The variety and price efficiency of futures makes things pretty attractive in this area.
SUBCULTURE
Wallstreetbets is a community that has become infamous for the most wild west, moon or cardboard box trades on the planet earth. WSB is a place where you can take out thousand dollar loans, refinance your homes, cash advance all of your credit cards only to put it all on JNUG, and we will still love you. Your mother won't. Your father will never understand your spectrum of autism, but we will always love you. It is a uniquely beautiful community focused on praising its biggest losers as much as its biggest winners. To begin on the subculture, we should define some key moments in the sub's history.
HISTORY: (As made by u/digadiga) + my additions
2012: Jartek [+1] creates /wallstreetbets, and word slowly starts to ooze out. 2013: americanpegasus discovers pennies. AP has seen the light, and is a penny stock evangelist. Jartek & AP have an epic options vs pennies battle - they both lose a couple of hundred bucks, but we are entertained, and WSB is officially born. AP blows up his retirement, swears off pennies and moves onto bitcoins.