Why don't you just contact the mining pools directly and ask?  At worst, they'll say no... at best, they'll say yes. My guess would be somewhere in the middle and they'll probably say "OK, but for $$$"  |
|
|
|
A newbie with a self-moderated thread... offering $300 worth of account for $6? That couldn't be more scammy if the thread title was "This is a scam"  Be thankful that you only lost $6... I assume the 1 negative feedback on his "shoppy" is from you? That's about all that can be done in this instance. Why on earth do people keep sending these scammers money? For what it is worth, I've tagged the user. Archived his threads: http://archive.is/pBghLhttp://archive.is/uvQgShttp://archive.is/VbPGV |
|
|
|
If two did actually complete the requirements and they did in fact renege on the actual give away I would in this case support a negative rating. If there is evidence of this I would like to see it.
Actually... it looks like I misinterpreted something that QS mentioned upthread... my bad. I've edited my post. But blenderio did indeed say that there were "too few people"... and also claims that they meant that anyone who didn't make 10 posts would not be counted as participants. No, I meant the ones who didn't make 10 posts won't be counted as a participants. Unfortunately, there were too few ppl for 2nd week and none of them completed requirements. Stay tuned for the next event, it will be as big as this one, if not even bigger.
In the end, I don't believe they were running a "scam"... TryNinja did get an iPhoneX as promised... tbh, it seems like just a very poorly run giveaway... ¯\_(ツ)_/¯ |
|
|
|
|
Like I told you in PMs, it makes no difference... the 12 word passphrase is created "external" to any network... And (for whatever reason), both Mainnet and Testnet use exactly the same addresses. So you didn't create your account "in mainnet" or "in testnet"... you simply created a random 12 word passphrase.
At some point, you obviously misclicked and accidentally selected "Testnet" (you don't need to click on the arrow btw, clicking ANYWHERE on the network dropdown box activates it)... and the wallet just remembers what you last selected.
|
|
|
|
Odd... after a complete reboot it should have removed any "zombie" ArmoryDB processes... So, unless you have some other app/util/service that also happens to be using Port 9001 I'm not sure why ArmoryDB seems to think that port is in use. Maybe try following the instructions here: https://veerasundar.com/blog/2009/10/how-to-check-which-application-is-using-which-port/1. Open the command prompt - start » run » cmd or start » All Programs » Accessories » Command Prompt.
2. Type: netstat -aon | findstr "[port_number]". Replace the [port_number] with the actual port number that you want to check and hit enter.
3. If the port is being used by any application, then that application’s detail will be shown. The number, which is shown at the last column of the list, is the PID (process ID) of that application. Make note of this.
4. Type: tasklist | findstr "[PID]". Replace the [PID] with the number from the above step and hit enter.
You’ll be shown the application name that is using your port number.
For example... I know that bitcoin-qt is running on 8332... so, netstat -aon | findstr "8332" gives: TCP 127.0.0.1:8332 0.0.0.0:0 LISTENING 15412
and then tasklist | findstr "15412" gives: bitcoin-qt.exe 15412 Console 1 331,156 K
Also, my ArmoryDB seems to pick "random" port numbers... do you have 9001 hardcoded in your Armory config file? |
|
|
|
To be honest, I am not getting the exact point on their additional terms for second week.
It was pretty simple... In the first week, a lot of users had just signed up to the various forums, added the signature to their account and then never actually used any of the forums... so, no "free" signature advertising for blender.io as there were no posts So they added in the additional requirement that if you wanted stakes from having forum signatures, you had to post at least 10 messages on each of the forums... otherwise no forum stakes. This seems to have been too much work (I guess no one wanted to spam 10 messages on 10 different forums) for most people... so only two people qualified for forum stakes... blenderio then apparently decided that wasn't enough free advertising and just called the whole thing off. |
|
|
|
Then try shutting everything down and rebooting your PC and ten seeing if Armory will load up... if it doesn't, you will need to post the contents of both armorylog.txt and dbLog.txt. I recommend you use pastebin.com to avoid running into "max post size" errors (it also helps keep the thread tidy  ) |
|
|
|
|
It's quite possible that one of the Armory components (likely ArmoryDB) is still running in the background. The easy solution is to shut everything down and reboot your computer to guarantee all the processes have been killed properly. Then try running Armory again.
Alternatively, you can look in Task Manager and make sure there are no Armory related processes running (you maybe need to click the "more details" button to see ALL processes).
If that doesn't work and Armory is still stopping...
What version of Bitcoin Core do you have installed?
Is your wallet.dat and "blocks" folder in "E:\Bitcoin\Bitcoin Core" directory? If not, what directory are your wallet.dat and "blocks" folder in?
|
|
|
|
...but then it pops up this messege and says: Wallet file corruption detected. Please restore your wallet from seed, and compare the addresse…
This means that your wallet file is corrupted and could possibly be creating addresses that are not backed up by your recovery seed. There was an old issue that was fixed whereby you could end up with a situation like this: When creating a new wallet, the path would be set to the path of an existing wallet, as due to os.path.exists failing, the wizard would think there is no file there yet. However in the wallet storage constructor, os.path.exists would suddenly work and the existing file would get opened. The wizard would then start modifying the existing file, thinking it's a new one. The wizard would put a new seed and xpub there. Then, the task that creates the addresses for the xpub (create_addresses) would be a no-op, as it would find that there are already "enough" addresses generated in the file (corresponding to the old wallet!).
When the wizard finished, the wallet would then get opened as normally. The wallet file would contain the new seed, new xpub, but old addresses. It would appear that you might have had something similar happen... You should create a new wallet ("File -> New\Restore -> NEW_WALLET_NAME -> Standard wallet -> I already have a seed"), as suggested by nc50lc... and see if it generates the same addresses as the wallet that is giving you the corruption warning. If it does not, then your seed will not be able to restore your wallet file. You should immediately create a new wallet (with new seed) and send all your Bitcoins from "corrupt" wallet to new wallet. |
|
|
|
I uninstalled Electrum and plugged in a external hard drive that has the version of Electrum that the wallet was on before.
Does that external hard drive also have a copy of the actual wallet file (not just a copy of the application) on it? If so, make a copy of the wallet file and then try and open that copy with the new version of Electrum. |
|
|
|
Tried what exactly? Using the Repair feature? And you didn't answer my question... If you disconnect the device and then reconnect it (without holding any buttons), is it going straight to Bootloader? |
|
|
|
He is now going to have those tags and his sig is gone likely for a long time. Even worse now every thread he starts will show a THIS THREAD IS STARTED BY A SCAMMER (thanks theymos ffs a dreadful and disgraceful implementation without ensuring only scammers have red tags)
OBSERVABLE FACT #1: The warning is only shown when the person viewing the thread is not logged in. Any user that is currently logged into the system does not see that warning. Logged in: Not Logged in:
OBSERVABLE FACT #2: It doesn't say "THIS THREAD IS STARTED BY A SCAMMER" at all... That is perhaps your (incorrect) interpretation of the warning, but in fact, that's not even close to what it says. What it actually says is: Warning: One or more bitcointalk.org users have reported that they strongly believe that the creator of this topic is a scammer. (Login to see the detailed trust ratings.) While the bitcointalk.org administration does not verify such claims, you should proceed with extreme caution. Kindly stick to fact... and not your wild (and often incorrect) interpretation of reality. #kthxbye |
|
|
|
In my opinion, at face value, it reads that you need to make 10 posts for your forum links to be counted. It doesn't say that forum posts are required for other tasks to count. For the Week 2 we have the additional requirement: you will need to post at least 10 messages before the next round for each of your forum's links, otherwise those will not be counted.
The original requirements never specified that you must have "forum links" to participate... they were just one option of many... like tweets/retweets/blog posts etc. So, if all you did was use Twitter, you should still have been given the appropriate number of stakes (ie. Like a post: 1 stake; Retweet a post: 1 stake. etc) If that is not want blenderio meant, then the requirements (original or additional) should have clearly stated that you needed to complete ALL the tasks to be eligible... or at least that forum posting was a "compulsory" task and if it wasn't done, then none of your tasks would count. As QS has mentioned, it might just be a language issue and failure to communicate clearly... but it certainly does seem that they just decided that they didn't get the advertising they wanted (10 posts per user per forum) so they decided to cancel it... Which, seems a bit unfair to those who did complete the non-forum posting tasks in good faith. |
|
|
|
Ok I wasn't aware of that. After a month of this thread why wasn't this told and warned earlier? Is there anything else I should know about before continuing?
This isn't "official" support... and we can't possibly foresee every single eventually. We have no idea what you're actually doing when you run off and start downloading things, plugging things in and clicking things, nor what exact hardware you have or the configurations you've set... So, effectively, everything you do is at your own risk. Ok I managed to get the ledger live app working.
That's a good start... for the record I've installed the 1.8.1 AppImage on a Ubuntu 16.04 VM running in VirtualBox 6.0.8. I installed the vbox "extensions" in Windows Host (which was needed to make USB 2&3 work in the VM). I've managed to connect my Ledger Nano S to Ledger Live (even installed a coin app using the Manager) and also connected it to Electrum 3.3.6 running in the VM. Repair feature is my last is my last resort.
What does the device actually do when you plug it in? Is it just stuck at "Bootloader" even after disconnecting and reconnecting? If so, then you'll definitely need to use the "repair" feature. |
|
|
|
Is it possible the client generate 2 same adresses with 2 identical seeds?
The possibility of randomly generating the same seed as another wallet, while technically "non-zero", is so incredibly small that it's regarded as being "impossible". For reference, Electrum generates a random 128bit seed... That's 2^128 or 340,282,366,920,938,463,463,374,607,431,768,211,456 different values that are possible (then you get the checksum added on for good measure). |
|
|
|
This is of great concern: some of the words in my phrase are in that big master list, but others arent.
ALL of the words should be in the BIP39 wordlist... Electrum uses only words from this list to generate seeds... it is in the source code. So if you have words that aren't in that list, then you either copied them down incorrectly, or it wasn't generated by Electrum. I have retried with older version (3.03 which i think is what the wallet was originally generated with) and 3.01 but they wont get past the synchronising stage..
Did those older versions actually accept the words? Did it allow you to click "next"? If it did and it opened the wallet but was stuck on synchronising, then you should be able to simply open the created wallet file in the new version of Electrum and it should sync. |
|
|
|
When you try to connect the device in BootLoader mode... the system will see it as a different device (Note the different "name"), so you will need to reattach it:  Can't help with Ledger Live not running... I've not had any issues with the .appImage, but I'm using Ubuntu 16.04 on VirtualBox. Maybe try starting it from a Terminal window instead of simply clicking on the .AppImage icon... that way you might get to see any error messages generated. Or you could try and use the browser in Linux Mint and just redownload the 1.8.1 .AppImage directly instead of trying to use the "update" feature: https://download-live.ledger.com/releases/latest/download/linuxAlso, have you tried connecting to Ledger Live in Windows now? Does it do anything? It might be possible to use the "Repair" feature (settings -> help -> "Repair your ledger device"). Make sure that VirtualBox is shutdown before you use Ledger Live in Windows to prevent any conflicts with accessing the device. |
|
|
|
|
Unfortunately, it doesn't happen automatically... mostly because there is no back-end system link between alt accounts. That requires "humans" to identify alts (generally self admitted or linked from same BTC addresses being used etc)
But using alts is considered ban evasion, so if you get caught and reported, then the alt account will also be banned.
|
|
|
|
Hi I setup virtualbox with linux mint however the problem is my 8gb usb stick is not recognised in the virtual guest linux mint.
Did you right click the little USB icon in the bottom right corner? It'll show you a list of USB devices attached to the Host which you can "pass through" to the Virtual Machine:  By default, they're not "connected" to the VM. You need to select the one(s) you want to be able to be available in the virtual machine and then the VM should "see" the device has been plugged in. EDIT: Note, I also had to follow the instructions for Linux here: https://support.ledger.com/hc/en-us/articles/115005165269-Fix-connection-issues to get it to recognise the Ledger Nano S correctly in VirtualBox with Ubuntu 16.04 The "plugdev" group seemed OK, it was point #2 with the udev rules that seemed to fix it. I |
|
|
|
|
Show Posts
