Veel geluk met je website...

Heb wel een klein vraagje:
Heb je aan de intellectuele eigendom van de images die je in je design gebruikt hebt gedacht? Ik had namelijk het gevoel dat ik een aantal van die images in het verleden tegengekomen ben op de website van een bank, het voelde allemaal wat te bekend aan voor me. Dus heb ik eens 3 random images uitgekozen en onder de loep genomen:

Image: https://www.getbittr.com/images/index/image-1.png
(mogelijk) Origineel (gedeeltelijk) te vinden op: https://www.rtlnieuws.nl/economie/artikel/4294886/bitcoin-maakt-grote-sprong-weer-bijna-7500-dollar-waard

Image: https://www.getbittr.com/images/backgrounds/bg-1.jpg
(mogelijk) Origineel te vinden op: https://www.valuejagers.com/blog/de-drie-elementen-voor-succes-op-de-beurs/

Image: https://www.getbittr.com/images/index/image-2.jpg
Origineel gevonden op een royalty free stock photo site, dus OK

Pas wel op: dit is zeker geen beschuldiging, het kan mijns inziens perfect zijn dat alle gebruikte images allemaal royalty free zijn, of dat er betaald werd voor het gebruik. Ik wil je echter behoeden voor een vette rekening van één of ander advocatenkantoor voor het onrechtmatig gebruik van foto's

 Zoals ik al zei: de reden dat ik me hierin verdiept heb is omdat ik dacht dat één van de beelden van de website van een bekende bank kwamen, en dat ik niet kon geloven dat die bank gebruik gemaakt zou hebben van stock photos (maar ik bleek het verkeerd te hebben).

Well, that's more or less what i meanth by my post (i might have worded it wrong, was a bit tired and english is not my native language)... That doesn't mean i'm comfortable installing the .net SDK on any non-sandbox machine. AFAIK, it's closed source, released by microsoft and it clearly states they can actually collect data and send it back to microsoft when you read the TOS...
I don't think it'll ever be included in popular linux distros because of these parameters (closed source, propriatary, data collection).

I know electrum needs python3, but i'm far more comfortable installing an open source python binary on my machines compared to some closed source microsoft framework that clearly tells you they'll probably be sending data back to microsoft.

But that's just my personal gut feeling... Everybody has to decide this for their own, and it has little to do with this wallet

I'm just a unix sysadmin who develops as a hobby so i'm not really proficient in all these testing standards, but these steps you posted in your previous post sound about right

no problem
I was still editing my respons while you were already quoting it (a bad habit of me).
I guess the answer was given in my previous post:

- regtest mode is a local environment, you start a bitcoin (or altcoin) daemon in regtest mode and immediately generate one or more blocks. These coins are 100% local, and can be used to test out application. You need to connect to the daemon that was started in regtest mode in order to run your tests.

- the testnet is a real network. Most existing coins have several people running a testnet node, there are a couple of miners that mine testnet blocks. The testnet usually behaves exactly like the main net, except it's usually a bit less predicatable due to fluctuating hashrate and other people using it for their own tests. Testnet coins are worthless to

I prefer testing on the testnet, since it mimics the main net much closer than running a daemon in regtest mode.

When you're talking about "testing the blockchain". Do you mean you've created your own blockchain from scratch, or do you mean testing an application that used one of the existing crypto currencies  to accept payments, store smart contracts in a blockchain or store data in a blockchain?

If it's the first case (built your own blockchain): If you developed your own blockchain from scratch, this question should be very easy for you...

If it's the second case (using an existing blockchain): Most establised crypto currencies have a main net, a testnet and regtest mode. The testnet and regtest are usually used for testing new software applications.

Since i like testing out open source wallets, i cloned your github repo and i've built this wallet on a sandbox system.

I haven't vetted the code, so don't take this post as a vouch for this wallet! I just wanted to give you an opinion of the wallet running on my sandbox system. There are many positive points, but i decided to give some feedback on the things i'd personally change if it were my project. That way you might get some feedback that can help you in improving your project.

• build process: i must say i wasn't a fan of an open source wallet for which i needed to download .net's SDK on my linux box... I would have preferred a different language. However, i must say the build process ran smoothly. For my main system, i don't think i'll be downloading .net in order to run this wallet tough
• initialisation of the wallet: I'd personally prefer it if you forced the users to repeat the mnemonic words and their pass after the initialisation... That way you're more or less sure they did take some kind of backup (clear the clipboard between these steps so the user can't copy/paste the mnemonic)
• Overall look: a bit to dark for me, but that's my personal preference
• Coinjoin feature: i found it strange to see the minimum amount to register for a coinjoin session is 0.05007 BTC... I for one am not going to risk >$300 (in fiat) to take a testrun of this wallet
• Ease of use: i think anybody who has used a wallet in the past will be able to use this one...
• Wallet features: i'm missing coin controll features, multisig, signing of messages, export features (like the xpub or unsigned tx's), address controll, signing of unsigned transactions,...
• I also browsed your documentation, and did find how to setup a backend node on the testnet, however i could not find the configuration parameter i need to run the wallet itself on the testnet... I must admit i didn't read everything thoroughly... => ~/.walletwasabi/client/Config.json

All in all, without reviewing the codebase for backdoors or flaws in any other part of the code, i must say that it's a nice looking wallet with most of the basic features one would need... However, i think you'll have to work on adding additional features and lowering the minimum amount to enter a coinjoin sesssion. It might also be a good idear to let the user pick a different color scheme to make things a bit less dark.

I disagree..

What if the exchange locks your account?
What if the exchange gets hacked?
What if the exchange turns scam?
What about a mitm attack?
What if you fall for a phising link?
What if your pc gets infected with a password stealing virus?

If you are not the only one in controll of your private keys, you are not in controll of your funds.

Do not store your funds on an exchange longer than you need to complete a trade... 2fa authentication or unique passords will not save you from these attack vectors (except the last one)

I had never heared about this one, did some research... It turns out aml bitcoin is just some altcoin. This has nothing to do with the discussion about bitcoin wallets.
Edit: but then i went trough your posthistory, and found out 100% of your post are promoting this altcoin, leading me to believe you are just a payed shill so you are not really in here for bitcoin discussion, but merely to spam for your employer

That's an urban legend: https://www.linux.com/learn/myth-busting-linux-immune-viruses
Linux is not immune to virusses, however it's security model is built in a different way than window's security model, next to this the amount of desktops running linux is smaller than the amount of desktops running windows (so a virus writer will be tempted to write a windows virus instead of a linux one because a windows virus can do more damage due to the amount of potential victims)

Also, AFAIK, both sandboxie and malwarebytes only have windows binaries available, it's no use to tell somebody to switch to linux AND use sandboxie or malwarebytes

I'm a longtime member, and even i have 3 or 4 electrum wallets on my PC (i seldomly use them tough, i've switched to hardware wallets a long time ago)... I guess it all depends on you:

• Do you run a recent version of your OS
• Do you download unknown programs from unknown sources
• Do you open email attachments
• Do you have a recent firewall installed
• Do you have an up-to-data virusscanner
• Do you install OS updates/patches on a regular basis
• Do you tell other people you hold BTC?

In general, if you keep a small amount of BTC on a pc with an up-to-date OS, virusscanner and well configured firewall, and you don't install unknown programs or open unkown emails, you should be relatively* fine... Even if you have multiple wallets on your pc.
There is a bit of a discussion about which OS is the safest. Personally, i think that *nix OS's are safer out-of-the box AND are safer if they're hardened by a seasoned user. But in case you don't know anything about *nix and you do have some experience managing windoze boxes, you might be better off sticking to microsoft products instead of trying to configure an OS you're unfamiliar with...

If you hold a bigger value in crypto currencies and/or you don't think you have the experience/will to run a tight system, you might be better off with one of the following methods:

• A hardware wallet
• A properly generated (bip38 encrypted) paper wallet
• An (encrypted) offline/cold wallet on an airgapped PC

*relatively fine: in the past, security flaws have been found in popular, opensource wallets... So as long as you run your wallet on a pc that is connected to the internet, you're never 99.9% safe.

If I was setting up a hidden service i wouldn't touch a thirth party payment provider with a ten foot pole (or a 3 meter pole if you're from a country that uses the metric system like me ).
It isn't hard to run bitcoind or a monero daemon on tor and use the json rpc interface to generate new addresses, monitor incoming funds, create new transactions, sign messages,...

If you want to use a thirth party payment provider, you'll probably need to find one that also runs a hidden service, otherwise your customers will be shown an invoice on the clearnet... I doubt they'll be happy about this. I actually doubt your customers will feel safe and secure if you'd use any kind of thirth party payment provider at all... Why involve more people than you strictly have to involve?

This being said: i personally don't like darknet marketplaces... But it's up to you to make sure you follow all laws and rules that apply in your country...

1) verify on an independant blockchain explorer (like blockchain.info): enter the deposit address you generated using electrum in their search field, and see if there is a CONFIRMED transaction funding this address

IF this is the case, the problem is on your end... If it's not the case, it's on the sender's end

IF the problem is on your end:
1) check if the button on the right hand side of the electrum screen is green
2) check if the electrum version you have is the latest version
3) try to restart your electrum wallet
4) double-check if the address you gave to the sender was indeed generated by your wallet... (since electrum doesn't see an incoming transaction, the address should still be the address that's being shown in the receive-tab of electrum).
5) by clicking on the green (or red/brown) dot on the bottom right corner, you can manually switch electrum servers... You can try a couple and see if it changes anything (not likely if the button is green tough... A lagging electrum server is indicated by a brown button, a red button means no connection.. IIRC)
6) if everything else fails, you can always try to re-install a fresh copy of the latest version of electrum on a clean pc that is defenately able to connect to the internet, restore your wallet using the seedphrase you initially got and see if it is able to detect an incoming transaction

One other potential thing i can think of: are you 100% positive the person paying you sent BTC, not BCH or some other altcoin?

Technically, since segwit, a block can theoretically be 4Mb (on disk), however 3Mb is reserved for the witness data in order to keep backwards compatibility for the "old" nodes that still have the 1Mb limit. Offcourse, in reality, a block will almost never reach the 4Mb limit, but will probably be very close to the 1Mb limit after you disregard the witness data.


I haven't done the math, but my gut feeling tells me that if you'd only take the average amount of transactions per block for the last year, you'll get a lot more than 500 tx/block on average... Offcourse, if you take the all-time average, it'll probably be a lot lower (possibly around the ~500tx/block range... idk)

Sorry for the fact that i quoted so many posts, but i felt it was necessary to make the following observation:
1) you were banned
2) you opened a thread in meta to discuss your ban
3) you were told that you were banned for copy/pasting
4) you acknowledge this fact, but still keep on posting

Did you read the rules after you were banned? If you continue posting in more than 1 thread or outside meta while being banned, this is  called ban evasion. This is a bannable offence...

It might be a good idear if you start by reading this sticky post:
https://bitcointalk.org/index.php?topic=497545.0

btw: it seems like theymos and cyrus are waaaaay behind on account recovery... You might have to wait weeks/months/years before your account gets recovered, so don't get your hopes up.

However, if you post the signed message (as explained in the post i mentioned) in this thread, one of the mods can probably lock your account, so the hacker can't abuse it and get it banned/tagged...

Last note, a bit offtopic but still: satoshi dissapeared a long, long, long time ago... So don't ask him to help you...

I'm going to talk about how i personally see things... This might not be the same reasoning the moderators followed when they banned your account.

I've been here for a long while, and it seems a lot of "bounty hunters" don't see this forum for what it really is: a BITCOIN TALK forum. This forum was created to discuss and promote bitcoin. If it's primary purpose was to spam ico bounties it would have been called icospam.org instead of bitcointalk.org.

Now, you say things like: "i only joined an ico bounty and it forced me to post 10 times a week", and you think it's unfair you got banned because of it, but in reality, the ico bounty doesn't really belong on this forum. You've joined a thirth party service that is a big nuicance to this forum... For most longtime members, those bounty thingies are a grey area, they're frowned upon to say the least... So if you join such an ico bounty, and then produce crap posts just to meet your 10 posts/week criterium, you're going to get banned sooner or later.

Last (fair) heads up: IIRC, you only get 2 or 3 temp bans before a permaban... So since you were banned 2 times before, you're heading for a permaban right now... Once you're permabanned, it's you (as a person) and not your account that is banned... If you continue down this path, you'll soon be no longer permitted to use this forum alltogether...

Normaal gezien gebruiken ze de bitcoin: URI

Hier is een voorbeeldje (heb m'n eigen adres ingevuld, dus niet op klikken ):
bitcoin:1MocACiWLM8bYn8pCrYjy6uHq4U3CkxLaa?amount=0.001&label=Mocacinno&message=Fooi%20voor%20mocacinno

meer info: https://github.com/bitcoin/bips/blob/master/bip-0021.mediawiki

Als je electrum niet als portable of standalone draait, zal de bitcoin: uri normaal gezien door de installer gekoppeld zijn aan electrum, dus als je op de bovenstaande link zou klikken, zou normaal gezien electrum automatisch moeten opengaan, zou het label "Mocacinno" aan de betaling moeten hangen, zou m'n address automatisch moeten ingevuld zijn, zou de value 0.001 automatisch moeten ingevuld zijn, en zou de message "Fooi voor mocacinno" automatisch ingevuld moeten zijn... Moet je enkel nog op "send" klikken, en alle metadata word netjes in je wallet opgeslagen

most probably, yes...
Unless you used the persistence feature, or saved the wallet on a different medium, the wallet is gone. In other words: if you didn't take explicit action in order to save the wallet file persistently, it is gone... This feature is clearly documented in tail's documentation.

Source: https://tails.boum.org/

It has nothing to do with the hardware, you just chose to use a live OS that is configured not to leave a single trace.
You never explicitly said you didn't write down the seed, but i'm pretty sure that not answering this question is an answer on itself...


I hope you didn't fund the address generated by your wallet with to much... If it's just a couple bucks, you should probably consider it a tuition fee... Next time, make sure you understand the technology you're using, and read the messages that are printed on your screen... When you were generating a wallet, the seed must have been clearly shown to you, and in the next step of the wallet generation, you must have been asked to repeat the seed phrase that was shown to you... IIRC, the messages shown in this step clearly tell you you HAVE to save the seed on a piece of paper.
Electrum even goes as far as clearing the clipboard between the two steps, so you can't just copy the seed in the first step and paste it in the second step... There's a reason for this.

Sorry for your loss...

The recovery phrase should be generated by you... This is usually done when you initialse the hardware wallet. If you receive a hardware wallet that was already initialised, you shouldn't use it (IMHO). Hardware wallets are cheap, you shouldn't buy a used one, but instead buy a new one directly from the company itself, so in case it's initialised you can consider it to be compromised, and you have no idear if the person comprommising the hardware wallet messed with the hardware itself to.

If you don't trust the company itself, you can always use different (offline) tools to generate a seed phrase, and enter this independant seed phrase in your hardware wallet.

BTW: answering to a thread that has been inactive for 6 months is frowned upon. You did the right thing by using the search function and not creating a new thread, but in this case it might have been better if you found a more recent thread or created a new one anyways

I agree with the previous posters, but i did want to give a "formal" answer to your question:

No, if you only have the funded address and a password used to encrypt your wallet, there is no way to recover your wallet.

You need one of these:

• The seed phrase that was shown to you when you created the wallet (it should have been indicated quite clearly that you really NEEDED to save the seedphrase... IIRC, you even have to prove you wrote down the seed before you can continue the wallet creation wizard)
• The wallet file AND the encryption password (if you don't remember the password, but you chose a weak one, or you have a decent idear what the password might have looked like, there are ways to brute-force it IF you have the wallet file)
• A list of all the private keys whose public key hashes (addresses) were funded (but i guess it's a longshot, since you didn't seem to have saved your seed phrase, i doubt you have used the function to export private keys.... BTW: it's not a good idear to export private keys to begin with, just save the seed phrase next time)

Like LoyceV already said: stop using the disk, unplug it, put it in a different machine as secondary disk (don't boot from it), then use a tool like dd to clone the disk containing your wallet file... Then copy the disk image, and only after you have 2 copies of the image from the disk that was in the "crashed" pc, you can proceed with tools like recuva and try to restore the wallet file.

@LoyceV: great to see you take action against such a character ... Slightly offtopic, but still relevant: i can still read this guy's email address, even after you tried to blur it... If you were serious protecting his email, you might want to swith to a different blurring tool
I personally use greenshot on my work pc (windows), it's image editor has tools to completely remove any part of a screencap and/or securely blur any part of the text...