|
To have the least costs, you should set up your own node and write your own software to manage everything.
Give every customer an account and the function to request a new address for them to accept BTC transaction.
Upon receiving a TX -> give a confirmation to your customer so that they can handle any orders etc.
Then you can simply subtract your cut when they withdraw their BTC.
Another option is to simply just credit them 100% - your cut to their account upon receiving a transaction.
|
|
|
|
2. First of all, compress JPG/PNG images without losing quality by using [...]
JPG already is a compression which deletes parts of the image (irreversible). With the JPG compression, you are keeping all the information regarding the brightness of the pixel and shrink the color channels. Afterwards a discrete cosinus transformation (DCT) is applied. Depending on the quality level (80-90 is usually chosen) you then further compress the tables containing the coefficients. Long story short, you can not compress a JPG image without losing information -> without reducing the quality. |
|
|
|
Don't you have to option to send it to her via mail? Sending an encrypted paper wallet by mail and the password via email / phone would be the more secure option. You obviously also have to take all precautions when creating a paper wallet (i.e. on an offline computer and preferably without using a website). 1. Let her download a reputable wallet like BlueWallet.
Excuse me? Downloading a reputable wallet or BlueWallet? |
|
|
|
Considering that the guy that reported the vulnerability about Ledger didn’t even mention Trezor, I also assume #2 is correct. Trezor also only fixed the issue after the report, so he would certainly also call them out.
This makes sense, but i wonder why he didn't also report the vulnerability to trezor. He might have been able to get another bounty reward. It probably wouldn't be too much additional work to test it on a trezor. I guess he maybe didn't have a trezor lying around  |
|
|
|
They did release an update (to the Trezor One) to address issues related to this vulnerability: https://blog.trezor.io/firmware-updates-for-trezor-model-t-version-2-3-2-and-trezor-model-one-version-1-9-2-f4f9c0f1ed7cMissing path isolation check
We have amended our Trezor One code to include a missing path isolation check, which is already in place for the Trezor Model T. This check prevents a user from spending coins from known paths (BIP44, BIP49, BIP84), if the coin type does not match the path. Without this check, an attacker could trick the user into signing a Bitcoin transaction while thinking they are signing a testnet or altcoin transaction.
Yes, that's the quote i have posted. But the question was whether there was a bug bounty from trezor (just like with ledger) through which they received the information regarding this or whether they just checked their HW wallet after seeing ledgers being vulnerable to that. And in this case i'd guess its #2 because their bug bounty page doesn't show anything related to this vulnerability. |
|
|
|
So I am stuck - Without the transaction code I cant pay services to help process it.
Payed transaction accelerators are mostly scam. You shouldn't bother with them. Upgrading core to the latest version would probably the best idea. Is there any specific reason you are using an old version and don't want to upgrade? If so, you might want to try to delete the transaction from core (i.e. using -zapwallettxes) Is it shown in the history tab as an unconfirmed transaction ? Before doing anything, make sure to have a backup of your wallet.dat file. |
|
|
|
I attempted to send bitcoin from my Electrum account, but the coins in the Electrum account were cash.
Cash? Bitcoin cash, or what do you mean? Please clarify. It now shows sent & the money is gone from my account.
Yes, that's how transactions work. You send something, it gets deducted from your wallet. That's expected behavior. The recipient is of course showing the transaction, but it's showing zero received.
How can he see a transaction but receiving nothing? Could you clarify this please? Can I cancel the transaction? Is there anything I can do to get the coins back?
No. Your transaction got confirmed. Is the receiving address the wrong one? Or what exactly is the issue? |
|
|
|
|
If your mobile is indeed compromised, chances are high that it still is.
Unfortunately there is no way for your to get your BTC back.
However, you should definitely find out how that happened. Was your smartphone compromised, your email account, easy password, ...
Your BTC are gone, but there might be other sensitive data which should be checked (e.g. other accounts, CC, .. ), depending on what data you have stored on your mobile.
|
|
|
|
[...]
Aktuell gibt es die Möglichkeit die MCOs für einen festen Betrag in CRO zu tauschen. Dieser gilt bis einschließlich 03. November. Wer bis zum 03.09. seine MCOs swapped, bekommt 20% extra auf der Exchange.
[...]
Anzumerken ist hierbei noch, dass der Swap nicht automatisch stattfindet. Wer also bis Anfang November nicht tauscht, bleibt mit wertlosen MCO zurück, welche keine Utility o.Ä. haben. Zudem wird der oben erwähnte Bonus, dem aktuellen "Stake" auf dem Exchange hinzugefügt und verlängert diesen damit wieder auf 180 Tage. Wer also bereits einen Stake dort hat und das nicht möchte, muss ~1 Monat warten und dann tauschen (ohne einen Bonus zu erhalten). |
|
|
|
Is there any suggestion that there was a similar bug bounty submitted to Trezor, or have they just seen the Ledger one, examined their own devices, and realized they were also susceptible?
I guess only Trezor knows. But according to https://trezor.io/security/, there hasn't been such a vulnerability reported and fixed. So i would assume, they checked their device upon seeing the vulnerability affecting Ledger. But only a guess tho. |
|
|
|
Glaub unter Linux ist sowieso alles einfacher als unter Windows  Nicht alles. Zum Beispiel: Sich mit Malware infizieren, geht unter Windows wesentlich einfacher  Heißt unter Windows "Gemeinsame Nutzung der Internetverbindung".
Einfach rechte Maustaste auf den Netzwerkadapter mit Internetverbindung > Freigabe > Häkchen bei "Anderen Benutzern im Netzwerk gestatten, diese Verbindung als Internetverbindung zu verwenden".
Da hätte ich vermutlich an alles andere gedacht, als an IP Forwarding  "Anderen Benutzern im Netzwerk.." impliziert ja, dass sich der Host schon im Netzwerk befindet.. das ist ja im Forwarding Beispiel nicht der Fall, da der Rechner ja quasi als Bridge zwischen 2 Netzwerken fungiert. Naja.. vielleicht interpretiert ich bei solchen Beschreibungen auch einfach zu viel hinein. |
|
|
|
Wasabi is excellent. However, they're under investigation by Europol. Chainalysis did an 3-week investigation for them and according to their findings, 30% of the funds washed come from the dark market. Remember, this is similar to what happened to bestmixer.io before they got shut down.
The thing is, they might be able to shut down wasabi's coordinator server which is managing the CoinJoin, but after all that is a decentralized protocol where no one learns anything about the other participants and no one can link other inputs/outputs together beside the one owning them. When (if) wasabi finally decides to allow others to run a coordinator server, the whole process is distributed and decentralized. Shutting that down won't be possible since there is no single instance. |
|
|
|
Ist sowas im Normalfall (im engl. Bereich) ein Löschgrund? Es gibt doch immer wieder Lizenzen die verkauft werden und bisher wäre mir das nie aufgefallen... möchte nur richtig informiert sein fürs nächste Mal.
So etwas wird im engl. Bereich nicht gelöscht. Da (bei den Digital Goods -> Invites/Accounts) gibt es eig. nur die zwei Regeln von theymos: You are only allowed to sell accounts/invites that you legally obtained yourself or through legitimate trades. If you did anything illegal in order to obtain an item, then you can't trade it on bitcointalk.org. Anyone found breaking this rule will be banned.
und These services have informed me that it is impossible, worldwide, to trade their accounts without breaking the law, and I find this claim plausible. Therefore, trading their accounts is not allowed.
N26 (a German bank)
Upwork
If you have a really strong argument for how you're legally selling these accounts, create a topic in Meta explaining in detail.
Ich denke, dass es "schwer" zu beweisen ist, dass diese Keys tatsächlich auf illegale Weise beschafft worden sind. Jedoch ist jedem mit Menschenverstand klar, dass das der Fall ist. Im internationalen Bereich werden diese Threads nicht entfernt. |
|
|
|
It seems that my bech32 address was the fault. I will never generate one similar again. Only segwits.
No, not bech32 / segwit is at fault, but the wallet provider who didn't update his software for more than 2.5 years. I wouldn't use any software without such an important update for more than 2.5 years. Obviously you are not at fault in this case, but the person using a scammer website from someone trying to deceive people into believing the shitcoin BCH is the real bitcoin. All you can (or better: should) do is to tell the person that this website is a pure scam and he should either stop using web wallets at all (best) or at least switch to a more reputable one which received updates within the last 3 years. |
|
|
|
Funktioniert es auch den Antminer per Kabel mit dem PC zu verbinden und die Internetverbindung vom PC mit dem Antminer zu teilen?
Klar. Unter Linux wären die Schritte relativ einfach und schnell umzusetzen: 1) IP4 Forwarding aktivieren: echo 1 > /proc/sys/net/ipv4/ip_forward 2) IP Tables Einträge: sudo iptables -A FORWARD -o wlan0 -i eth0 -s 192.168.1.0/24 -m conntrack --ctstate NEW -j ACCEPT
sudo iptables -A FORWARD -m conntrack --ctstate ESTABLISHED,RELATED -j ACCEPT
sudo iptables -t nat -A POSTROUTING -o wlan0 -j MASQUERADE
ist hierbei durch das mit dem Router verbundenen Interface (i.d.R. wlan0 oder etwas wie wlp0s..) zu ersetzen. eth0 ist durch das Ethernet interface zu ersetzen (i.d.R. eth0 oder enp4s0 / enp6s0). 192.168.1.0/24 ist durch deine Netzwerkadresse zu ersetzten (i.d.R. 192.168.1.0/24 oder 192.168.0.0/24). Für Windows gibt es sicherlich auch Anleitungen im Internet. Das wird sich aber vermutlich etwas schwieriger gestalten, es sei denn es gibt dafür irgendwelche Tools (was durchaus sein könnte). Sonst einfach mal nach "IP forwarding windows" o.Ä. googlen. Einfacher wäre es aber vermutlich auf den bestellten Repeater zu warten  |
|
|
|
They don't market themselves as a mixer, but effectively that's what they offer. Their purpose is to obfuscate funds.
What "they" offer, is a privacy-orientated wallet. We have way too less of such wallets implementing new features and improvements. CoinJoin is a decentralized way to regain some level of anonymity by mixing funds with other participants. You are free to use your SPV wallet which communicates with a 3rd party server telling them all of your addresses, the amount of BTC you own, all your transactions, your IP address and therefore a relatively precise geo location. But not everyone has to use such a privacy-invading wallet. And IMO wasabi actually is the best privacy preserving SPV desktop wallet available. |
|
|
|
//edit: da finde ich eher die Vorgänge aus dem Jahr 2018 bedenklich. Da war es noch dein Account? Nicht nur bedenklich, sondern illegal. Mich wundert es, dass dieser User noch kein neg trust hatte. Die Keys, die er verkauft hat, sind illegal beschafft worden (ob erworben oder nicht sei mal dahin gestellt) und werden nicht lange funktionieren. |
|
|
|
The same vulnerability seems to have affected Trezor: Missing path isolation check
We have amended our Trezor One code to include a missing path isolation check, which is already in place for the Trezor Model T.
This check prevents a user from spending coins from known paths (BIP44, BIP49, BIP84), if the coin type does not match the path.
Without this check, an attacker could trick the user into signing a Bitcoin transaction while thinking they are signing a testnet or altcoin transaction.
While this vulnerability definitely poses some risk, it is not the worst one could imagine. Not using a compromised computer / fake version of a wallet or restraining from trading shitcoins for a while will keep you safe. |
|
|
|
Their major concern is not bitcoin or any other cryptocurrency but the pirate software that may be installed.
I heavily doubt that pirated software is what they are looking for when inspecting electronic devices at the border I wouldn't even be surprised if they didn't care at all about a cracked version of windows or whatsoever. That's definitely not what they are looking for. |
|
|
|
So r u saying that if I download Electrum it would be easier to open these files created by PYwallet (Jack Jack)?
is it a simple copy and paste or drag and drop?
or do I have to know coding, programming, or how to use CMD?
Please check HCP's post: A ".csv" file is simply text file in "comma separate values" format... You should be able to open it in any text editor to review the contents. [...]
And especially this: Even if you could import it back into Bitcoin Core (note: you can't), it wouldn't be much of much use in attempting to recover any funds... it's simply a list of transaction data (ie. transactionIDs and amounts etc)... it won't contain any private keys or anything like that.
You need your private keys to spend any coins. The transaction data simply does not contain this information. And it won't help you "recovering" it. Unfortunately it won't help you recovering any funds at all. |
|
|
|
|
Show Posts
