Bitcoin Wallet (BTC). Erstellen Sie eine Bitcoin Wallet ...

Lots of reports stating bitcoin wallets can be ID'd from a known tx, is this fud? /r/btc

Lots of reports stating bitcoin wallets can be ID'd from a known tx, is this fud? /btc submitted by BitcoinAllBot to BitcoinAll [link] [comments]

[OWL WATCH] Waiting for "IOTA TIME" 27;

Disclaimer: This is my editing, so there could be always some misunderstandings and exaggerations, plus many convos are from 'spec channel', so take it with a grain of salt, pls.
+ I added some recent convos afterward.
--------------------------------------------------​
📷
Luigi Vigneri [IF]어제 오후 8:26
Giving the opportunity to everybody to set up/run nodes is one of IOTA's priority. A minimum amount of resources is obviously required to prevent easy attacks, but we are making sure that being active part of the IOTA network can be possible without crazy investments.
we are building our solution in such a way that the protocol is fair and lightweight.

📷
Hans Moog [IF]어제 오후 11:24
IOTA is not "free to use" but it's - fee-less
you have tokens? you can send them around for free
📷
Hans Moog [IF]어제 오후 11:25
you have no tokens? you have to pay to use the network
📷
lekanovic어제 오후 11:25
I think it is a smart way to avoid the spamming network problem
📷
Hans Moog [IF]어제 오후 11:26
owning tokens is essentially like owning a share of the actual network
and the throughput it can process
📷
Hans Moog [IF]어제 오후 11:26****​
if you don't need all of that yourself, you can rent it out to people and earn money
📷
Hans Moog [IF]어제 오후 11:27
mana = tokens * time since you own them
simplified
📷
Hans Moog [IF]어제 오후 11:27
the longer you hold your tokens and the more you have, the more mana you have
but every now and then you have to move them to "realize" that mana
📷
lekanovic어제 오후 11:28
Is there any other project that is using a Mana solution to the network fee problem ?
📷
Hans Moog [IF]어제 오후 11:28
nah
the problem with current protocol is that they are leader based
📷
Hans Moog [IF]어제 오후 11:29
you need absolute consensus on who the current leaders are and what their influence in the network is
that's how blockchains works
📷
Hans Moog [IF]어제 오후 11:29
if two block producers produce 2 blocks at the same time, then you have to choose which one wins
and where everybody attaches their next block to
IOTA works differently and doesn't need to choose a single leader
we therefore have a much bigger flexibility of designing our sybil protection mechanisms
in a way, mana is also supposed to solve the problem of "rewarding" the infrastructure instead of the validators
in blockchain only the miners get all the money
running a node and even if it's one that is used by a lot of people will only cost
you won't get anything back
no fees, nothing
the miners get it all
📷
Hans Moog [IF]어제 오후 11:31
in IOTA, the node operators receive the mana
which gives them a share of the network throughput
📷
Hans Moog [IF]어제 오후 11:32
because in blockchain you need to decide whose txs become part of the blocks
and it's not really based on networking protocols like AIMD
📷
lekanovic어제 오후 11:33
And the more Mana your node have, the more trust your node has and you have more to say in the FPC, is that correct?
📷
Hans Moog [IF]어제 오후 11:33
yeah
a node that has processed a lot of txs of its users will have more mana than other nodes
and therefore a bigger say in deciding conflicts
its a direct measure of "trust" by its users
📷
lekanovic어제 오후 11:34
And choosing committee for dRNG would be done on L1 protocol level?
Everything regarding Mana will be L1 level, right?
📷
Hans Moog [IF]어제 오후 11:35
Yeah
Mana is layer1, but will also be used as weight in L2 solutions like smart contracts
📷
lekanovic어제 오후 11:35
And you are not dependant on using SC to implement this
📷
Hans Moog [IF]어제 오후 11:35
No, you don't need smart contracts
That's all the base layer
📷
Hans Moog [IF]어제 오후 11:37
'Time' actually takes into account things like decay
So it doesn't just increase forever
It's close to "Demurrage" in monetary theory
📷
lekanovic어제 오후 11:36
For projects to be able to connect to Polkadot or Cosmos, you need to get the state of the ledger.
Will it be possible to get the Tangle state?
If this would be possible, then I think it would be SUPER good for IOTA
📷
Hans Moog [IF]어제 오후 11:38
Yeah but polkadot is not connecting other dlts
Just inhouse stuff
📷
Hyperware어제 오후 11:39
Is there still a cap on mana so that the rich don't get richer?
📷
Hans Moog [IF]어제 오후 11:39
Yes mana is capped
📷
TangleAccountant어제 오후 11:39
u/Hans Moog [IF] My first thought is that the evolution of this renting system will lead to several big mana renting companies that pool together tons of token holders mana. That way businesses looking to rent mana just need to deal with a reliable mana renting company for years instead of a new individual every couple of months (because life happens and you don't know if that individual will need to sell their IOTAs due to personal reasons). Any thoughts on this?
📷
Hans Moog [IF]어제 오후 11:41
u/TangleAccountant yes that is likely - but also not a bad thing - token holders will have a place to get their monthly payout and the companies that want to use the tangle without having tokens have a place to pay
📷
TangleAccountant어제 오후 11:42
Oh I completely agree. That's really cool. I'll take a stab at creating one of those companies in the US.
📷
Hans Moog [IF]어제 오후 11:42
And everybody who wants to run a node themselves or has tokens and wants use the tangle for free can do so
But "leachers" that would want to use the network for free won't be able to do so
I mean ultimately there will always be "fees", as there is no "free lunch".
You have a certain amount of resources that a network can process and you have a certain demand.
And that will naturally result in fees based on supply / demand
what you can do however is to build a system where the actual users of that system that legitimately want to use it can do so for free,
just because they already "invest" enough by having tokens
or running infrastructure
they are already contributing to the well-being of the network through these two aspects alone
it would be stupid to ask those guys for additional fees
and mana essentially tries to be such a measure of honesty among the users
📷
Hyperware어제 오후 11:47
It's interesting from an investment perspective that having tokens/mana is like owning a portion of the network.
📷
Hans Moog [IF]어제 오후 11:48
Yeah, you are owning a certain % of the throughput and whatever the price will ultimately be to execute on this network - you will earn proportionally
but you have to keep in mind that we are trying to build the most efficient DLT that you could possibly ever build
📷
semibaron어제 오후 11:48
The whole mana (tokens) = share of network throuput sounds very much like EOS tbh
Just that EOS uses DPoS
📷
Hans Moog [IF]어제 오후 11:50
yeah i mean there is really not too many new things under the sun - you can just tweak a few things here and there, when it comes to distributing resources
DPoS is simply not very nice from a centralization aspect
📷
Hans Moog [IF]어제 오후 11:50
at least not the way EOS does it
delegating weights is 1 thing
but assuming that the weight will always be in a way that 21 "identities" run the whole network is bad
in the current world you see a centralization of power
but ultimately we want to build a future where the wealth is more evenly distributed
and the same goes for voting power
📷
Hans Moog [IF]어제 오후 11:52
blockchain needs leader selection
it only works with such a centralizing component
IOTA doesn't need that
it's delusional to say that IOTA wouldn't have any such centralization
but maybe we get better than just a handselected nodes 📷
📷
Phantom3D어제 오후 11:52
How would this affect a regular hodler without a node. Should i keep my tokens elsewere to generate mana and put the tokens to use?
📷
Hans Moog [IF]어제 오후 11:53
you can do whatever you want with your mana
just make an account at a node you regularly use and use it to build up a reputation with that node
to be able to use your funds for free
or run a node yourself
or rent it out to companies if you just hodl
📷
semibaron어제 오후 11:54
Will there be a build-in function into the node software / wallet to delegate ("sell") my mana?
📷
Hans Moog [IF]어제 오후 11:55
u/semibaron not from the start - that would happen on a 2nd layer
------------------------------------------------------------------------------------------------------------
📷
dom어제 오후 9:49
suddenly be incentive to hold iota?
to generate Mana
📷
Hyperware오늘 오전 4:21
The only thing I can really do, is believe that the IF have smart answers and are still building the best solutions they can for the sake of the vision
📷
dom오늘 오전 4:43
100% - which is why we're spending so much effort to communicate it more clearly now
we'll do an AMA on this topic very soon
📷
M [s2]오늘 오전 4:54
u/dom​ please accept my question for the AMA: will IOTA remain a permissionless system and if so, how?
📷
dom오늘 오전 4:57
of course it remains permissionless
📷
dom오늘 오전 5:20
what is permissioned about it?
is ETH or Bitcoin permissioned because you have to pay a transaction fee in their native token?
📷
Gerrit오늘 오전 5:24
How did your industry partners think about the mana solution and the fact they need to hold the token to ensure network throughput?
📷
dom오늘 오전 5:26
u/Gerrit considering how the infrastructure, legal and regulatory frameworks are improving around the adoption and usage of crypto-currencies within large companies, I really think that we are introducing this concept exactly at the right time. It should make enterprise partners comfortable in using the permissionless network without much of a hurdle. They can always launch their own network if they want to ...
📷
Gerrit오늘 오전 5:27
Launching their own network can’t be what you want
📷
dom오늘 오전 5:27
exactly
but that is what's happening with Ethereum and all the other networks
they don't hold Ether tokens either.
📷
Gerrit오늘 오전 5:32
Will be very exciting to see if ongoing regulation will „allow“ companies to invest and hold the tokens. With upcoming custody solutions that would be a fantastic play.
📷
Hans Moog [IF]오늘 오전 5:34
It's still possible to send transactions even without mana - mana is only used in times of congestion to give the people that have more mana more priority
there will still be sharding to keep the network free most of the time
📷
Hans Moog [IF]오늘 오전 5:35
but without a protection mechanism, somebody could just spam a lot of bullshit and you could break the network(수정됨)
you need some form of protection from this
📷
M [s2]오늘 오전 5:36
u/Hans Moog [IF] so when I have 0 Mana, I can still send transactions? This is actually the point where it got strange...
📷
Hans Moog [IF]오늘 오전 5:37
yes you can
unless the network is close to its processing capabilities / being attacked by spammers
then the nodes will favor the mana holders
📷
Hans Moog [IF]오늘 오전 5:37
but having mana is not a requirement for many years to come
currently even people having fpgas can't spam that many tps
and we will also have sharding implemented by then
📷
M [s2]오늘 오전 5:39
Thank you u/Hans Moog [IF] ! This is the actually important piece of info!
📷
Basha오늘 오전 5:38
ok, i thought it was communicated that you need at least 1 mana to process a transaction.
from the blogpost: "... a node with 0 mana can issue no transactions."
maybe they meant during the congestion**, but if that's the case maybe you should add that**
📷
Hans Moog [IF]오늘 오전 5:42
its under the point "Congestion control:"
yeah this only applies to spam attacks
network not overloaded = no mana needed
📷
Hans Moog [IF]오늘 오전 5:43
if congested => favor txs from people who have the most skin in the game
but sharding will try to keep the network non-congested most of the time - but there might be short periods of time where an attacker might bring the network close to its limits
and of course its going to take a while to add this, so we need a protection mechanism till sharding is supported(수정됨)
📷
Hans Moog [IF]오늘 오전 6:36
I don't have a particular problem with EOS or their amount of validators - the reason why I think blockchain is inferior has really nothing to do with the way you do sybil protection
and with validators I mean "voting nodes"
I mean even bitcoin has less mining pools
and you could compare mining pools to dpos in some sense
where people assign their weight (in that case hashing power) to the corresponding mining pools
so EOS is definitely not less decentralized than any other tech
but having more identities having weight in the decision process definitely makes it harder to corrupt a reasonable fraction of the system and makes it easier to shard
so its desirable to have this property(수정됨)

-------------------------------------------------

📷
Antonio Nardella [IF]오늘 오전 3:36
https://twitter.com/cmcanalytics/status/1310866311929647104?s=19
u/C3PO [92% Cooless] They could also add more git repos instead of the wallet one, and we would probably be #1 there too..
----------------------------------------------------------------------------------
Disclaimer:
I'm sorry, maybe I'm fueling some confusion through posting this mana-thing too soon,
but, instead of erasing this posting, I'm adding recent convos.
Certain things about mana seem to be not clear, yet.
It would be better to wait for some official clarification.
But, I hope the community gives its full support to IF, 'cause
there could be always some bumps along the untouched, unchartered way.
--------------------------------------------------------------------------------------
Recent Addition;

Billy Sanders [IF]오늘 오후 1:36

It's still possible to send transactions even without mana - mana is only used in times of congestion to give the people that have more mana more priority
u/Hans Moog [IF] Im sorry Hans, but this is false in the current congestion control algorithm. No mana = no transactions. To be honest, we havent really tried to make it work so that you can sent transactions with no mana during ties with no congestion, but I dont see how you can enable this and still maintain the sybil protection required. u/Luigi Vigneri [IF] What do you think?📷

Dave [EF]오늘 오후 2:19

Suggestion: Sidebar, then get back to us with the verdict.(수정됨)📷2📷

dom오늘 오후 2:27

No Mana no tx will definitely not be the case(수정됨)📷5📷7***[오후 2:28]***Billy probably means the previous rate control paper as it was written by Luigi. I'll clarify with them📷

Hans Moog [IF]오늘 오후 2:29

When was this decided u/Billy Sanders [IF] and by whom? Was this discussed at last resum when I wasnt there? The last info that I had was that the congestion control should only kick in when there is congestion?!?***[오후 2:29]***📷 📷 📷📷

Navin Ramachandran [IF]오늘 오후 2:30

Let's sidebar this discussion and return when we have agreement. Dave has the right idea

submitted by btlkhs to Iota [link] [comments]

Private key mining problem

It's not a secret anymore that people are trying to mine private keys.
Even if chances are astronomically low to find the right key, there is a chance. With a graphic card mining rig, a miner, with an investment of a few hundred $, can produce more than 300MH/s. Now imagine if someone is dedicating even more resources to find a private key.
As I said, chances are low to achieve that. That's the beauty of mathematics. But there is a chance, and right now, people are trying to do so.
There should be a way to prevent such behavior.
I was thinking of a solution to this problem:
A wallet should have a "wallet token/coin". When a user wants to make a transaction, let's say with Bitcoin, at first, it would need to make a transaction using the "wallet token". The "wallet token" has a private key of its own. The private key is a hash generated using a username, password, pin, and timestamp. The transaction would be automatically directed to the connected node if it's not specified differently. This transaction would produce a tx id. Just as now, when the user wants to make the Bitcoin transaction, the user would need to insert his private key. In this case, besides the private key, the wallet would ask for the tx id done with the "wallet token". Those two hashes would produce a unique, more extended, and one-time use, private key. This last private key would enable the wanted transaction.
The private key miner would need to make countless transactions before even being able to find out if he got the right private key. Economically, it would not be profitable, unlike now, when he can effortlessly guess and try if the private key "fits" until it succeds.
The "wallet token" would be created with some of these mechanisms:
  1. Proof of work - mining like BTC
  2. Proof of ownership - every wallet would produce small amounts of tokens over time.
  3. Proof of transaction - Every transaction you do, you generate a new token for future transactions.
This is not a light and user-friendly solution. Its sole purpose is enhanced security.
PS
I'm not a techy guy. I don't know if this would require a completely new blockchain or it could be implemented in already existing wallets, coins, and protocols.
Even if enormous numbers are reliable enough to keep our cryptocurrencies safe, faster and more efficient computers are being built every day. At this rate of progress, it not hard to imagine a super ASIC that could be able to mine a private key if left a few years to do its job. Not to mention the threat that quantum computers represent.
I hope this will open a discussion in the crypto community to find the best solution to this problem. Or at least someone could explain why this is not an option or is a bad idea.
Thank you Satoshi!
submitted by BlueBloodStrawberry to SatoshisPhilosophy [link] [comments]

hodlmon.sh: a UTXO monitoring methodology and script for true connoisseurs of security, paranoia and BTC maximalism

EDIT:
Disclaimer: the below script is provided for example purposes only. You're responsible for your own security. Don't trust, verify.
tldr: the script is literally just an example wrapper to call "gettxout" on your own node via cron to check if your own utxo has been spent yet
OK, since there are a few questions on security below, let me clarify: this script is only for people who are 1) already running their own nodes and 2) can understand the bash script below. And obviously, don't trust some random person on the internet, always verify. I provided this as an example for a way to monitor your own UTXOs with your existing node. Those of you who understand what the below script does will see it's painfully simple and obviously harmless. Those of you who don't understand it, just ignore this post, or better yet, research what the below means until you do understand it. What's important is the idea of monitoring your own UTXO, and this script is an example of how to do that with gettxout.
ORIGINAL POST:
Submitting this to help strengthen the community, and for review:
hodlmon.sh: a UTXO monitoring methodology and script for true connoisseurs of security, paranoia and BTC maximalism
Monitor canary UTXOs for early detection of compromised private keys BEFORE funds are lost, using your own full node for maximum privacy and trustlessness. Note that you will need to implement your own notification strategy (email, push, sms, etc). This script is intended to run on your full node, but can be run from any machine with RPC access to your full node.
hodlmon.sh is designed to check if a given UTXO (i.e. a specific output of a specific btc transaction) has been spent or not. This can be used for early and proactive detection if a seed phrase or private key has been compromised, so you have time to move your btc before full compromise happens. In order for this to work, a small amount of btc should be sent to an address controlled only by a given seedphrase, with that seedphrase being part of a multisig wallet or a seedphrase+passphrase wallet, and the majority of your funds controlled in the seedphrase+passphrase or multisig wallet. The idea is to leave the small amount of btc (the canary utxo) in the address, so that it never moves unless the seedphrase that controls it has been compromised and all funds in the wallet swept. In this way, you use those compromised sats to buy information about the current security status of your wallet(s).
Example usage:Set up a cron job to run hodlmon.sh every 30 min to check if transaction output at index "0" for transaction with id "123" has been spent already. Use "my_utxo_nickname" as a friendly name for the UTXO (to differentiate between multiple wallets)
*/30 * * * * /path/to/hodlmon.sh 123 0 my_utxo_nickname > /tmp/hodlmon_log 2> /tmp/hodlmon_err_log
Usage scenario #1: Seedphrase (A) + passphrase (A')Majority of funds are held in a wallet controlled by both the seedphrase and passphrase, A and A'. A token amount of btc is controlled only by seedphrase A.
A + A': majority of funds
A: canary UTXO
hodlmon.sh is used to monitor the canary funds locked by A, so that if it is discovered that A has been compromised, the funds locked by A and A' can be moved to a new wallet before the passphrase A' can be cracked and all your funds exfiltrated.
Usage scenario #2: multisig e.g. 2 of 3, with seed phrases A, B and CMajority of funds held in a multisig wallet controlled by 3 seedphrases A, B, and C. 3 small canary UTXOs are held in wallets each controlled by A, B or C, respectively.
A + B + C: majority of funds
A: canary UTXO 1
B: canary UTXO 2
C: canary UTXO 3
One benefit of multisig (e.g. 2 of 3) is that even if 1 key is compromised, your funds are safe, since at least 2 keys are needed to release funds. But how do you that none of the keys has yet been compromised? If you create separate wallets controlled each by only 1 of the individual keys, and use hodlmon.sh to monitor whether those UTXOs have been exfiltrated, then you can detect partial compromise of your setup before a full exfiltration event takes place, so you can move your funds to a new multisig wallet with freshly generated and uncompromised keys.
Example of 3 cronjobs to monitor all 3 canary UTXOs:
*/30 * * * * /path/to/hodlmon.sh 123 0 key1 > /tmp/hodlmon_log_1 2> /tmp/hodlmon_err_log_1
*/30 * * * * /path/to/hodlmon.sh 456 0 key2 > /tmp/hodlmon_log_2 2> /tmp/hodlmon_err_log_2
*/30 * * * * /path/to/hodlmon.sh 789 0 key3 > /tmp/hodlmon_log_3 2> /tmp/hodlmon_err_log_3

Example hodlmon script:
#########################################################################
#!/bin/bash
touch /tmp/hodlmon_last_run
echo "Transaction ID: $1"
echo "Output #: $2"
echo "Nickname: $3"
NODE_IP=127.0.0.1 #TODO: use actual value
USER=user#TODO: use actual value
PASS=pass #TODO: use actual value
PORT=8332 #TODO: use actual value
CHECK_CMD="/uslocal/bin/bitcoin-cli -rpcconnect=$NODE_IP -rpcuser=$USER -rpcpassword=$PASS -rpcport=$PORT gettxout $1 $2"
RESULT="$($CHECK_CMD)"
echo "${RESULT}"
if [ "$RESULT" == "" ]
then
echo "UTXO HAS BEEN SPENT! RED ALERT!!"
MSG="The UTXO for $3 from tx $1 output $2 has moved!"
#TODO: ADD YOUR FAVORITE NOTIFICATION STRATEGY E.G. EMAIL, PUSH NOTIFICATION, SMS
else
echo "UTXO is still on ice"
fi
############################################

submitted by facepalm5000 to Bitcoin [link] [comments]

RiB Newsletter #16 – Secure Enclaves à la Crab

For the last few months we’ve been following new zero-knowledge proof projects in Rust. This month, with Secret Network upgrading their mainnet with secret contracts, it seems like a good opportunity to explore Rust blockchains that are using a completely different privacy-preserving technology: secure enclaves.
Secure enclaves are processes whose environment is protected from inspection by other processes, even the kernel, by special hardware. This protection particularly involves the encryption of a process’s memory. Software that wants to compute in secret can put those computations inside a secure enclave and, if everything works as expected, neither a local user, nor the hosting provider, can snoop on the computations being performed. The most notable implementation of secure enclaves is Intel’s SGX (Secure Guard Extensions).
Secure enclaves are an attractive way to perform private computation primarily because they don’t impose any limitations on what can be computed — code that runs inside SGX is more-or-less just regular x86 code, just running inside a special environment. But depending on SGX for privacy does have some special risks: software that runs in an SGX enclave must be signed (if transitively) by Intel’s own cryptographic keys, which means that Intel must approve of any software running in SGX, that Intel can revoke permission to use SGX, and that there is a risk of the signing keys being compromised; and it’s not obvious that secure enclaves are actually secure, there have already been a number of attacks against SGX. Regardless, as of now, hardware enclaves provide security features that aren’t feasible any other way.
There are two prominent Rust blockchains relying on SGX:
Outside of the blockchain world there are some other Rust projects using SGX, the most notable being:
Whether it’s secure enclaves or zk-SNARKs, Rust blockchains are walking the bleeding edge of privacy tech.
In unrelated RiB news, we recently received two donations,
Thanks so much to our anonymous donors. We don’t often receive donations, so this was a nice surprise! We intend to put all monetary contributions to use funding events or new contributors, and we’ll let you know what we do with the funds when we spend them.

Project Spotlight

Each month we like to shine a light on a notable Rust blockchain project. This month that project is…
Aleo.
Aleo is a zero-knowledge blockchain, with its own zero-knowledge programming language, Leo.
We don’t have a lot to say about it, but we think it looks cool. We hope they blog more.

Interesting Things

News

Blog Posts

Papers

Projects


Read more: https://rustinblockchain.org/newsletters/2020-09-30-secure-enclaves-a-la-crab/
submitted by Aimeedeer to rust [link] [comments]

Just how bad is Chainalysis?

I've read about how some guy got his account blocked in Binance because he sent a transaction from Wasabi wallet. I've read it goes deep into several iterations after the mix. For instance:
You send the coins into a mixer -> send it back to you to address A -> send it back to you to address B -> send it to an exchanger.
Chainalaysis will notice the coins are mixed even if you've send it to 2 "clean addresses" before that. This is insanity. It could put people into trouble since one could mix the coins, send it to someone else, then this person sends it to an exchange where he is identified with his real name, and he ends up in some money laundering investigation scheme. Just nuts.
Does it recognize all mixers? If you use helix, chipmixer or whatever else... how would it even know? Do they just keep adding more and more "blacklisted" addresses? In a long enough timeline the % of ending up in some "money laundering investigation" is increasingly higher.
Until we have proper fungibility in Bitcoin, I wouldn't send a single satoshi to an exchanger that doesn't come from:
1) Coins you've bought from an exchange that uses Chainalysis (whitelisted by default since they had it on their custody wallet, one would assume those are safe)
2) Mined coins with no tx history
These f*ckers are just developing an scheme to put people in trouble and confiscate coins. Use bisq outside of the above mentioned cases IMO. Just assume 0 privacy when dealing with your average big exchange. Better safe than sorry. Our only hope is smart devs crush their Chainalysis dreams where every coin has an ID.
submitted by cryptomann1 to Bitcoin [link] [comments]

Where's My Money? Deposits And Withdrawals At Blockfi, Celsius, Crypto.Com And Nexo Compared

Does your crypto show up in your account? And can you get it back? Looking through 100+ complaints about deposits and withdrawals, the insights are obvious but good to know...
- They require additional information like tags (XRP, XLM)
- Had major software changes (BCH, BNB, DAI / MCD, ADA)
So if you're going to move one of these coins, make sure to not forget the extra information or wait a few weeks after the change (to give these companies time to get caught up).
Raw data is below, organized by company and whether it seems the complaint was resolved. Some important notes to consider
  1. Posts about waiting a few hours for a transaction to complete were not counted. Many times (most of the time?) when it takes more than 20 minutes, nothing is broken. E.g. High gas fees on the ethereum network will mean slower processing times for stable coins and other ERC-20 tokens. Less popular tokens, like GUSD, might require people manually going into cold storage. Large (> $30,000 USD) transactions require additional verification. If it takes > 8 hours then yes something is not right. And you should email support and start posting. Otherwise sit tight.
  2. Comments from different people on the same post saying they have the same problem were not counted for "scores". Most of these comments don't add useful information and make it harder to collect the data.
  3. Posts about fiat belong to a different category because a very different set of skills and software features are needed to safely move around dollars, euros, etc. This post is about whether or not your coins are likely to get lost or be unreachable.
  4. I asked "Did this get fixed?" to a lot of people who posted about problems. Not only to see how things turned out. Also to generate a possible data point about the quality of the post. I.e. Trolls and other "special" people venting online can be identified by not bothering to follow up or respond to questions. I also hope this encourages people to not forget to follow up a few weeks later and share a final outcome - good or bad.
Company Resolved Total complaints
BlockFi 50% 2 resolved, 2 not resolved
CDC 58% 29 resolved, 21 not resolved
Celsius 61% 23 resolved, 15 not resolved
Nexo 67% 8 resolved, 4 not resolved
BlockFi (Resolved)
https://www.reddit.com/blockfi/comments/hbcxqq/withdrawal_pending/
https://www.reddit.com/blockfi/comments/dkpy38/tx_confirmed_but_no_deposit/
BlockFi (Not resolved)
https://www.reddit.com/blockfi/comments/gvnbz0/withdrawal_of_large_requires_id_and_facial_scan/
https://www.reddit.com/blockfi/comments/hwqin8/refused_withdrawal_due_to_kyc/

CDC (Resolved)
https://www.reddit.com/Crypto_com/comments/grjphd/is_the_wallet_app_buggy_for_anyone_else_crashes/
https://www.reddit.com/Crypto_com/comments/gkduf8/unable_to_add_a_wallet_to_withdraw_funds/
https://www.reddit.com/Crypto_com/comments/cpaj2y/issues_with_crypto_invest_portfolio_and/
https://www.reddit.com/Crypto_com/comments/ceu0vd/1130pm_hkt_update_withdrawals_and_deposits_are/
https://www.reddit.com/Crypto_com/comments/gi62j3/missing_cro_sending_to_the_exchange/
https://www.reddit.com/Crypto_com/comments/d6qjtb/thank_you/
https://www.reddit.com/Crypto_com/comments/gjx3xp/where_are_my_coins/
https://www.reddit.com/Crypto_com/comments/ffiz9x/transfer_bch/
https://www.reddit.com/Crypto_com/comments/f7se85/usdt_delisted_on_cryptocom/
https://www.reddit.com/Crypto_com/comments/dw8vmn/my_funds_are_being_held_hostage_by_cryptocom_yes/
https://www.reddit.com/Crypto_com/comments/clg9r2/cryptocom_is_just_a_regular_bank_be_awared/
https://www.reddit.com/Crypto_com/comments/hqa0pm/btc_withdrawal_delay_5_hrs/
https://www.reddit.com/Crypto_com/comments/hmjq69/withdrawals_and_deposits_back_online/
https://www.reddit.com/Crypto_com/comments/hlro5y/ada_withdraw_erro
https://www.reddit.com/Crypto_com/comments/hlud4t/issues_since_app_update/
https://www.reddit.com/Crypto_com/comments/hlukqc/how_long_does_it_usually_take/
https://www.reddit.com/Crypto_com/comments/hm66xm/withdrawal_impossible/
https://www.reddit.com/Crypto_com/comments/hm81fj/no_bitcoin_withdrawals_since_saturday/
https://www.reddit.com/Crypto_com/comments/hm8irg/issue_with_withdrawing_eth/
https://www.reddit.com/Crypto_com/comments/hm8kn2/communication_near_to_0/
https://www.reddit.com/Crypto_com/comments/hmbo5a/cant_withdraw_any_bitcoin/
https://www.reddit.com/Crypto_com/comments/hikkx6/withdrawal_pending/
https://www.reddit.com/Crypto_com/comments/h91u4i/issues_on_cryptocom_app/
https://www.reddit.com/Crypto_com/comments/hb5fpusdt_withdrawal_from_exchange_doesnt_work_claims/
https://www.reddit.com/Crypto_com/comments/hdjrmz/keep_getting_a_withdrawal_erro
https://www.reddit.com/Crypto_com/comments/hebtyf/withdrawal_pending_taking_over_16_hours/
https://www.reddit.com/Crypto_com/comments/hgt61j/one_exchange_withdrawal_two_app_deposits/
https://www.reddit.com/Crypto_com/comments/htf578/withdrawal_dia_is_taking_8_hrs/
https://www.reddit.com/Crypto_com/comments/he151z/btc_withdrawal_delay/
CDC (Not resolved)
https://www.reddit.com/Crypto_com/comments/gx2oyo/pending_withdrawal/
https://www.reddit.com/Crypto_com/comments/gk8wlc/wont_let_me_buy_or_withdraw/
https://www.reddit.com/Crypto_com/comments/gh6v2c/usdc_withdrawing_to_external_address/
https://www.reddit.com/Crypto_com/comments/ggk51x/cryptocom_withdrawal/
https://www.reddit.com/Crypto_com/comments/g925xg/withdraw_blocked/
https://www.reddit.com/Crypto_com/comments/cfjess/withdraw_is_in_progress_from_23h/
https://www.reddit.com/Crypto_com/comments/gk8wlc/wont_let_me_buy_or_withdraw/
https://www.reddit.com/Crypto_com/comments/9xbi1c/withdrawals_delayed/
https://www.reddit.com/Crypto_com/comments/cga2eq/delayed_transfe
https://www.reddit.com/Crypto_com/comments/hd1to7/missing_funds_from_the_exchange_after_the/
https://www.reddit.com/Crypto_com/comments/grr4vh/crypto_wallet_scammed_me_beware/
https://www.reddit.com/Crypto_com/comments/cg5zfj/helpbnb_wallet_address_in_app_is_still_old_eth/
https://www.reddit.com/Crypto_com/comments/hrwpsq/btc_withdrawl_pending_for_24_hours_zero_custome
https://www.reddit.com/Crypto_com/comments/hpteje/how_to_withdraw_cro_from_the_exchange/
https://www.reddit.com/Crypto_com/comments/hottg4/cryptocom_app_is_not_working/
https://www.reddit.com/Crypto_com/comments/ha8o7v/problem_with_the_2fa_need_help_pls/
https://www.reddit.com/Crypto_com/comments/he3qco/btc_withdraw_pending_post_7_hours/
https://www.reddit.com/Crypto_com/comments/he45kj/withdrawal_stuck/
https://www.reddit.com/Crypto_com/comments/heb85q/btc_withdraw_pending_72_hours_now/
https://www.reddit.com/Crypto_com/comments/hhqruv/withdrawal_from_cryptocom_wallet_to_cryptocom_app/
https://www.reddit.com/Crypto_com/comments/hihl04/i_cant_withdraw_whats_happening/

Celsius (Resolved)
https://www.reddit.com/CelsiusNetwork/comments/gantb4/withdraw_delay/fp11iut/?context=3
https://www.reddit.com/CelsiusNetwork/comments/gb7c4t/withdrawal_still_pending_only_for_btc/fp4wmc3/?context=3
https://www.reddit.com/CelsiusNetwork/comments/gncvj9/my_withdraw_experience_with_celsius_network/
https://www.reddit.com/CelsiusNetwork/comments/fk844a/over_20k_withdrawals_processing_time/
https://www.reddit.com/CelsiusNetwork/comments/fhftgh/where_do_i_find_pending_or_past_withdrawals/
https://www.reddit.com/CelsiusNetwork/comments/epl29a/cant_withdraw_my_deposited_sai_as_a_texas_resident/
https://www.reddit.com/CelsiusNetwork/comments/dn0vg2/problem_withdrawing_eth_from_celsius_account/
https://www.reddit.com/CelsiusNetwork/comments/cw00t5/not_receiving_withdrawal_confirmation_email/
https://www.reddit.com/CelsiusNetwork/comments/ci3h6w/eth_withdrawal_appears_as_an_internal_transaction/
https://www.reddit.com/CelsiusNetwork/comments/c2w5gk/unable_to_withdraw_anything_from_the_app/
https://www.reddit.com/CelsiusNetwork/comments/br2v75/how_do_i_withdraw_the_interest/
https://www.reddit.com/CelsiusNetwork/comments/bqynbv/unable_to_withdraw_full_account_balance/
https://www.reddit.com/CelsiusNetwork/comments/a9d2vj/withdrawals_of_any_currency_are_not_currently/
https://www.reddit.com/CelsiusNetwork/comments/gfby9l/celsius_fixed_my_deposit_issue/fpw51u3/?context=3
https://www.reddit.com/CelsiusNetwork/comments/g9oiea/deposit_missing/
https://www.reddit.com/CelsiusNetwork/comments/dkb55t/deposit_not_showing_up/
https://www.reddit.com/CelsiusNetwork/comments/eudo3n/not_receiving_deposited_bitcoin/
https://www.reddit.com/CelsiusNetwork/comments/gepzpp/all_good_all_fix/
https://www.reddit.com/CelsiusNetwork/comments/hf334d/withdrawal_issue_trueusd_tusd_stable_coin/
https://www.reddit.com/CelsiusNetwork/comments/hiriqz/celsius_is_witholding_my_crypto/
https://www.reddit.com/CelsiusNetwork/comments/hjv0io/dai_withdrawal_pending_for_24hrs_subsequently/
https://www.reddit.com/CelsiusNetwork/comments/hme5xm/its_been_more_than_3_days_of_withdrawing_my_usdc/
https://www.reddit.com/CelsiusNetwork/comments/hvi45o/eth_and_cel_good_on_etherscan_not_show_in_app/
Celsius (Not resolved)
https://www.reddit.com/CelsiusNetwork/comments/fbpnw4/why_this_app_shutdown_when_we_try_to_change/
https://www.reddit.com/CelsiusNetwork/comments/f7i2f3/withdrawal_issues/
https://www.reddit.com/CelsiusNetwork/comments/f4ptd7/cant_get_my_crypto_not_getting_withdrawal_emails/
https://www.reddit.com/CelsiusNetwork/comments/ea3hi5/eth_withdrawal_made_from_a_smart_contract/
https://www.reddit.com/CelsiusNetwork/comments/cb08he/can_you_withdraw_to_a_bech32_btc_address/
https://www.reddit.com/CelsiusNetwork/comments/c8yovc/minimum_withdraws/
https://www.reddit.com/CelsiusNetwork/comments/bqqiqg/i_cant_withdraw_my_eth/
https://www.reddit.com/CelsiusNetwork/comments/askghy/what_is_the_withdrawal_fees_service_told_me_there/
https://www.reddit.com/CelsiusNetwork/comments/gtjoc9/btc_withdraw_transaction_still_pensing_after_1_day/
https://www.reddit.com/CelsiusNetwork/comments/g9f7ym/stolen_or_lost_deposits_hold_off_on_transferring/
https://www.reddit.com/CelsiusNetwork/comments/gf8v3i/mcdai_deposit_pending_for_days/
https://www.reddit.com/CelsiusNetwork/comments/d1sc3q/eth_deposit_address_is_a_contract_address/
https://www.reddit.com/CelsiusNetwork/comments/ca2wpd/warning_celsius_does_lock_up_your_funds/
https://www.reddit.com/CelsiusNetwork/comments/hnu53f/is_anyone_else_having_trouble_withdrawing_xrp/
https://www.reddit.com/CelsiusNetwork/comments/hv2czp/celsius_received_thousands_of_dollars_of_my_funds/

Nexo (Resolved)
https://www.reddit.com/Nexo/comments/gixzgu/cant_deposit_or_withdraw_stablecoins_right_now/
https://www.reddit.com/Nexo/comments/flshbb/my_withdraw_was_rejected/
https://www.reddit.com/Nexo/comments/fiit3u/nexo_withdrawal/
https://www.reddit.com/Nexo/comments/e2ij06/withdrawal_problems/
https://www.reddit.com/Nexo/comments/fhgmxg/missing_deposit/
https://www.reddit.com/Nexo/comments/f3z9kq/account_showing_no_balance/
https://www.reddit.com/Nexo/comments/gj3ub0/bnb_withdrawals/
https://www.reddit.com/Nexo/comments/hlxpnd/i_made_an_eth_deposit_36_hours_ago_the_txid_shows/
Nexo (Not resolved)
https://www.reddit.com/Nexo/comments/dpvrgj/nexo_withdrawal_pending_1_day/
https://www.reddit.com/Nexo/comments/dno3up/withdrawal_email_confirmation/
https://www.reddit.com/Nexo/comments/dm6nn9/withdraw_from_binance_dex/
https://www.reddit.com/Nexo/comments/c67gis/anyone_else_having_problems_with_loan_withdrawals/
submitted by thegoldlust to Crypto_com [link] [comments]

Where's My Money? Deposits And Withdrawals At Blockfi, Celsius, Crypto.Com And Nexo Compared

Does your crypto show up in your account? And can you get it back? Looking through 100+ complaints about deposits and withdrawals, the insights are obvious but good to know...
- They require additional information like tags (XRP, XLM)
- Had major software changes (BCH, BNB, DAI / MCD, ADA)
So if you're going to move one of these coins, make sure to not forget the extra information or wait a few weeks after the change (to give these companies time to get caught up).
Raw data is below, organized by company and whether it seems the complaint was resolved. Some important notes to consider
  1. Posts about waiting a few hours for a transaction to complete were not counted. Many times (most of the time?) when it takes more than 20 minutes, nothing is broken. E.g. High gas fees on the ethereum network will mean slower processing times for stable coins and other ERC-20 tokens. Less popular tokens, like GUSD, might require people manually going into cold storage. Large (> $30,000 USD) transactions require additional verification. If it takes > 8 hours then yes something is not right. And you should email support and start posting. Otherwise sit tight.
  2. Comments from different people on the same post saying they have the same problem were not counted for "scores". Most of these comments don't add useful information and make it harder to collect the data.
  3. Posts about fiat belong to a different category because a very different set of skills and software features are needed to safely move around dollars, euros, etc. This post is about whether or not your coins are likely to get lost or be unreachable.
  4. I asked "Did this get fixed?" to a lot of people who posted about problems. Not only to see how things turned out. Also to generate a possible data point about the quality of the post. I.e. Trolls and other "special" people venting online can be identified by not bothering to follow up or respond to questions. I also hope this encourages people to not forget to follow up a few weeks later and share a final outcome - good or bad.
Company Resolved Total complaints
BlockFi 50% 2 resolved, 2 not resolved
CDC 58% 29 resolved, 21 not resolved
Celsius 61% 23 resolved, 15 not resolved
Nexo 67% 8 resolved, 4 not resolved
BlockFi (Resolved)
https://www.reddit.com/blockfi/comments/hbcxqq/withdrawal_pending/
https://www.reddit.com/blockfi/comments/dkpy38/tx_confirmed_but_no_deposit/
BlockFi (Not resolved)
https://www.reddit.com/blockfi/comments/gvnbz0/withdrawal_of_large_requires_id_and_facial_scan/
https://www.reddit.com/blockfi/comments/hwqin8/refused_withdrawal_due_to_kyc/

CDC (Resolved)
https://www.reddit.com/Crypto_com/comments/grjphd/is_the_wallet_app_buggy_for_anyone_else_crashes/
https://www.reddit.com/Crypto_com/comments/gkduf8/unable_to_add_a_wallet_to_withdraw_funds/
https://www.reddit.com/Crypto_com/comments/cpaj2y/issues_with_crypto_invest_portfolio_and/
https://www.reddit.com/Crypto_com/comments/ceu0vd/1130pm_hkt_update_withdrawals_and_deposits_are/
https://www.reddit.com/Crypto_com/comments/gi62j3/missing_cro_sending_to_the_exchange/
https://www.reddit.com/Crypto_com/comments/d6qjtb/thank_you/
https://www.reddit.com/Crypto_com/comments/gjx3xp/where_are_my_coins/
https://www.reddit.com/Crypto_com/comments/ffiz9x/transfer_bch/
https://www.reddit.com/Crypto_com/comments/f7se85/usdt_delisted_on_cryptocom/
https://www.reddit.com/Crypto_com/comments/dw8vmn/my_funds_are_being_held_hostage_by_cryptocom_yes/
https://www.reddit.com/Crypto_com/comments/clg9r2/cryptocom_is_just_a_regular_bank_be_awared/
https://www.reddit.com/Crypto_com/comments/hqa0pm/btc_withdrawal_delay_5_hrs/
https://www.reddit.com/Crypto_com/comments/hmjq69/withdrawals_and_deposits_back_online/
https://www.reddit.com/Crypto_com/comments/hlro5y/ada_withdraw_erro
https://www.reddit.com/Crypto_com/comments/hlud4t/issues_since_app_update/
https://www.reddit.com/Crypto_com/comments/hlukqc/how_long_does_it_usually_take/
https://www.reddit.com/Crypto_com/comments/hm66xm/withdrawal_impossible/
https://www.reddit.com/Crypto_com/comments/hm81fj/no_bitcoin_withdrawals_since_saturday/
https://www.reddit.com/Crypto_com/comments/hm8irg/issue_with_withdrawing_eth/
https://www.reddit.com/Crypto_com/comments/hm8kn2/communication_near_to_0/
https://www.reddit.com/Crypto_com/comments/hmbo5a/cant_withdraw_any_bitcoin/
https://www.reddit.com/Crypto_com/comments/hikkx6/withdrawal_pending/
https://www.reddit.com/Crypto_com/comments/h91u4i/issues_on_cryptocom_app/
https://www.reddit.com/Crypto_com/comments/hb5fpusdt_withdrawal_from_exchange_doesnt_work_claims/
https://www.reddit.com/Crypto_com/comments/hdjrmz/keep_getting_a_withdrawal_erro
https://www.reddit.com/Crypto_com/comments/hebtyf/withdrawal_pending_taking_over_16_hours/
https://www.reddit.com/Crypto_com/comments/hgt61j/one_exchange_withdrawal_two_app_deposits/
https://www.reddit.com/Crypto_com/comments/htf578/withdrawal_dia_is_taking_8_hrs/
https://www.reddit.com/Crypto_com/comments/he151z/btc_withdrawal_delay/
CDC (Not resolved)
https://www.reddit.com/Crypto_com/comments/gx2oyo/pending_withdrawal/
https://www.reddit.com/Crypto_com/comments/gk8wlc/wont_let_me_buy_or_withdraw/
https://www.reddit.com/Crypto_com/comments/gh6v2c/usdc_withdrawing_to_external_address/
https://www.reddit.com/Crypto_com/comments/ggk51x/cryptocom_withdrawal/
https://www.reddit.com/Crypto_com/comments/g925xg/withdraw_blocked/
https://www.reddit.com/Crypto_com/comments/cfjess/withdraw_is_in_progress_from_23h/
https://www.reddit.com/Crypto_com/comments/gk8wlc/wont_let_me_buy_or_withdraw/
https://www.reddit.com/Crypto_com/comments/9xbi1c/withdrawals_delayed/
https://www.reddit.com/Crypto_com/comments/cga2eq/delayed_transfe
https://www.reddit.com/Crypto_com/comments/hd1to7/missing_funds_from_the_exchange_after_the/
https://www.reddit.com/Crypto_com/comments/grr4vh/crypto_wallet_scammed_me_beware/
https://www.reddit.com/Crypto_com/comments/cg5zfj/helpbnb_wallet_address_in_app_is_still_old_eth/
https://www.reddit.com/Crypto_com/comments/hrwpsq/btc_withdrawl_pending_for_24_hours_zero_custome
https://www.reddit.com/Crypto_com/comments/hpteje/how_to_withdraw_cro_from_the_exchange/
https://www.reddit.com/Crypto_com/comments/hottg4/cryptocom_app_is_not_working/
https://www.reddit.com/Crypto_com/comments/ha8o7v/problem_with_the_2fa_need_help_pls/
https://www.reddit.com/Crypto_com/comments/he3qco/btc_withdraw_pending_post_7_hours/
https://www.reddit.com/Crypto_com/comments/he45kj/withdrawal_stuck/
https://www.reddit.com/Crypto_com/comments/heb85q/btc_withdraw_pending_72_hours_now/
https://www.reddit.com/Crypto_com/comments/hhqruv/withdrawal_from_cryptocom_wallet_to_cryptocom_app/
https://www.reddit.com/Crypto_com/comments/hihl04/i_cant_withdraw_whats_happening/

Celsius (Resolved)
https://www.reddit.com/CelsiusNetwork/comments/gantb4/withdraw_delay/fp11iut/?context=3
https://www.reddit.com/CelsiusNetwork/comments/gb7c4t/withdrawal_still_pending_only_for_btc/fp4wmc3/?context=3
https://www.reddit.com/CelsiusNetwork/comments/gncvj9/my_withdraw_experience_with_celsius_network/
https://www.reddit.com/CelsiusNetwork/comments/fk844a/over_20k_withdrawals_processing_time/
https://www.reddit.com/CelsiusNetwork/comments/fhftgh/where_do_i_find_pending_or_past_withdrawals/
https://www.reddit.com/CelsiusNetwork/comments/epl29a/cant_withdraw_my_deposited_sai_as_a_texas_resident/
https://www.reddit.com/CelsiusNetwork/comments/dn0vg2/problem_withdrawing_eth_from_celsius_account/
https://www.reddit.com/CelsiusNetwork/comments/cw00t5/not_receiving_withdrawal_confirmation_email/
https://www.reddit.com/CelsiusNetwork/comments/ci3h6w/eth_withdrawal_appears_as_an_internal_transaction/
https://www.reddit.com/CelsiusNetwork/comments/c2w5gk/unable_to_withdraw_anything_from_the_app/
https://www.reddit.com/CelsiusNetwork/comments/br2v75/how_do_i_withdraw_the_interest/
https://www.reddit.com/CelsiusNetwork/comments/bqynbv/unable_to_withdraw_full_account_balance/
https://www.reddit.com/CelsiusNetwork/comments/a9d2vj/withdrawals_of_any_currency_are_not_currently/
https://www.reddit.com/CelsiusNetwork/comments/gfby9l/celsius_fixed_my_deposit_issue/fpw51u3/?context=3
https://www.reddit.com/CelsiusNetwork/comments/g9oiea/deposit_missing/
https://www.reddit.com/CelsiusNetwork/comments/dkb55t/deposit_not_showing_up/
https://www.reddit.com/CelsiusNetwork/comments/eudo3n/not_receiving_deposited_bitcoin/
https://www.reddit.com/CelsiusNetwork/comments/gepzpp/all_good_all_fix/
https://www.reddit.com/CelsiusNetwork/comments/hf334d/withdrawal_issue_trueusd_tusd_stable_coin/
https://www.reddit.com/CelsiusNetwork/comments/hiriqz/celsius_is_witholding_my_crypto/
https://www.reddit.com/CelsiusNetwork/comments/hjv0io/dai_withdrawal_pending_for_24hrs_subsequently/
https://www.reddit.com/CelsiusNetwork/comments/hme5xm/its_been_more_than_3_days_of_withdrawing_my_usdc/
https://www.reddit.com/CelsiusNetwork/comments/hvi45o/eth_and_cel_good_on_etherscan_not_show_in_app/
Celsius (Not resolved)
https://www.reddit.com/CelsiusNetwork/comments/fbpnw4/why_this_app_shutdown_when_we_try_to_change/
https://www.reddit.com/CelsiusNetwork/comments/f7i2f3/withdrawal_issues/
https://www.reddit.com/CelsiusNetwork/comments/f4ptd7/cant_get_my_crypto_not_getting_withdrawal_emails/
https://www.reddit.com/CelsiusNetwork/comments/ea3hi5/eth_withdrawal_made_from_a_smart_contract/
https://www.reddit.com/CelsiusNetwork/comments/cb08he/can_you_withdraw_to_a_bech32_btc_address/
https://www.reddit.com/CelsiusNetwork/comments/c8yovc/minimum_withdraws/
https://www.reddit.com/CelsiusNetwork/comments/bqqiqg/i_cant_withdraw_my_eth/
https://www.reddit.com/CelsiusNetwork/comments/askghy/what_is_the_withdrawal_fees_service_told_me_there/
https://www.reddit.com/CelsiusNetwork/comments/gtjoc9/btc_withdraw_transaction_still_pensing_after_1_day/
https://www.reddit.com/CelsiusNetwork/comments/g9f7ym/stolen_or_lost_deposits_hold_off_on_transferring/
https://www.reddit.com/CelsiusNetwork/comments/gf8v3i/mcdai_deposit_pending_for_days/
https://www.reddit.com/CelsiusNetwork/comments/d1sc3q/eth_deposit_address_is_a_contract_address/
https://www.reddit.com/CelsiusNetwork/comments/ca2wpd/warning_celsius_does_lock_up_your_funds/
https://www.reddit.com/CelsiusNetwork/comments/hnu53f/is_anyone_else_having_trouble_withdrawing_xrp/
https://www.reddit.com/CelsiusNetwork/comments/hv2czp/celsius_received_thousands_of_dollars_of_my_funds/

Nexo (Resolved)
https://www.reddit.com/Nexo/comments/gixzgu/cant_deposit_or_withdraw_stablecoins_right_now/
https://www.reddit.com/Nexo/comments/flshbb/my_withdraw_was_rejected/
https://www.reddit.com/Nexo/comments/fiit3u/nexo_withdrawal/
https://www.reddit.com/Nexo/comments/e2ij06/withdrawal_problems/
https://www.reddit.com/Nexo/comments/fhgmxg/missing_deposit/
https://www.reddit.com/Nexo/comments/f3z9kq/account_showing_no_balance/
https://www.reddit.com/Nexo/comments/gj3ub0/bnb_withdrawals/
https://www.reddit.com/Nexo/comments/hlxpnd/i_made_an_eth_deposit_36_hours_ago_the_txid_shows/
Nexo (Not resolved)
https://www.reddit.com/Nexo/comments/dpvrgj/nexo_withdrawal_pending_1_day/
https://www.reddit.com/Nexo/comments/dno3up/withdrawal_email_confirmation/
https://www.reddit.com/Nexo/comments/dm6nn9/withdraw_from_binance_dex/
https://www.reddit.com/Nexo/comments/c67gis/anyone_else_having_problems_with_loan_withdrawals/
submitted by thegoldlust to CelsiusNetwork [link] [comments]

Binance scammed me 1516 USDT with unethical verification requests! Stay Away from this Scam Exchance!

Binance scammed me 1516 USDT with unethical verification requests! Stay Away from this Scam Exchance!
I woud like here to point how BINANCE scammed me 1516 USD with some bullshit and unethical requests.
What happened?
On 2019-12-20 I registered a binance account. I choosed to not verify my account as the limits of 2 BTC were more than enough for me!
I deposited same day 0.21 BTC and sold it for USDT.
Since I didn't use my account. On March 30 I logged in from a new computer. The system sent me an email to authorize the new device. This was done successfully.
Later I tried to withdraw around 700 USD worth of BTC. The request was cancelled an the sytem asked me to verify my identiy. What???? What's the purpose of using unverified account????? So whenever I change my machine and login, I will have to submit my documents??
Meanwhile I had some discussion with live support, who tried to help. Finally, I have been told that I have no other choice than doing the full verification. I decided then to do the verification which was done finally successfully.
You can see here:

https://preview.redd.it/pkqhioutdfs41.png?width=493&format=png&auto=webp&s=fe4b632deb7d6d133d0894f6dfe1ac39b458b463

I spoke again with the support, they told me that I can try again, now that I'm fully verified, I can withdraw my funds.

https://preview.redd.it/v0gddx81efs41.png?width=488&format=png&auto=webp&s=fbe27450f5a0a6247080be59d0c0f064c736eb55
So I tried again to withdraw some BTC, first the status for "Waiting for approval" then later it changed "Rejected" with the info "Withdraw rejected. Risk control". What???
I contacted again the support and I have been told that I will receive an email from Binance within few hours.
Almost 20hrs passed, nothing from Binance. So I opened a Ticket.
u/ilir_binance 2821529 # is Ticket number for reference! Ticket was opened on 03/31/2020 (12 days ago by the time of writing this post).
Next day I received an answer from Binance support. And look what these people are asking me:
Dear user,
Thanks for reaching out,
We apologize for the delay in response due to the high volume of requests. As per checking, we found that the withdraw function was suspended due to the withdrawal risk control. We are willing to help you resume the withdrawal of your account. However, we may need some information to make progress.
Security questions:
  1. Account registration date
  2. Account registration IP
  3. Device information
So far this is not a problem to provide. I already provided this.
Furthermore, they asked me to record a video :
A video of the first deposit you made to your Binance account. The video would contain the login process (do NOT show password) of the platform/wallet where you made this transaction to your Binance account, find the transaction and show us the full TxID, date and amount information.
Seriously?????? These were parts of my answer to them, same day:
Hello guys,
Thank you for your reply, but I'm sorry to say that what you are asking is absolutely unethical, but it's okay. Your Kingdom, Your rules. I'm happy to solve this issue, take out my money out and never use again your terrible exchange.
[...]
  1. You wrote:
", please provide your withdrawal records and communication records with Binance CS"
Where the hell should I get communication records?? I had some chat with your support when my account got locked.
But where the hell should I get these communications?? Are you kidding me?
You asked for my withdrawal records? Which ones??? One was rejected, the other was cancelled.
So there was no withdrawal so far. So why are you asking something that does not exist??
[...]
  1. And finally you wrote:
"A video of the first deposit you made to your Binance account. The video would contain the login process (do NOT show password) of the platform/wallet where you made this transaction to your Binance account, find the transaction and show us the full TxID, date and amount information. "
My account was opened on the 20th December 2019!
I made my first deposit on the same day, 0.21.. BTC.
This has been now now more than 4 months!!!! How should I remember now which wallet I used by that time and what Transaction ID?
Are you kidding me??????
It was not a platform, I remember I used a wallet, but I dont remember which one anymore. I checked all my current wallets and I couldn't find this transaction.
It was this transaction based on my deposit history:https://www.blockchain.com/btc/tx/....

So they basically are asking me things that they know I can't provide and so would get a way to keep my money.

I asked them if it will be enough to provide anything else and close this case.
I will request then to withdraw all my coins and after that I will request you to close my account.
I will never use again your service.
I look forward to reading you soon, as we can close this case.

Since there have been no answer from their support! I sent few email to remind them, there was simply no answer!
So this was my last email to them, 5 days ago:

https://preview.redd.it/hryd3ghsefs41.png?width=474&format=png&auto=webp&s=bd853ce43499946e225dcbd2101fbc60c7efc24d
Still today, I didn't get any answer.
I want to let everyone know about this. If this company is not a scam, I'm asking them to let me withdraw my money simply.

Bitcoin BinanceExchange CryptoCurrency CryptoCurrencyTrading CryptoScam CryptoScamAlert CryptoScamsVictims
submitted by churgercold to binance [link] [comments]

Can I boost the tx fee with a different wallet?

Let's say I send from wallet 1 a bitcoin tx to address blalba. The fee used was too low so the tx is stuck in the mempool for some time. Can I use a separate Bitcoin wallet to bump up the fee? For example, by sending a small amount with a higher fee, to the same address (blabla). Will it bump up the fee of the first tx, or does it create a separate tx ID? How would an increase of tx fee from a different wallet be possible, if at all, otherwise?
submitted by MuliBoy to Bitcoin [link] [comments]

FAQ for Beginners

What is Bitcoin?

Bitcoin is scarce, decentralized, and global digital money that cannot be censored.

Quick Advice

  • Do not respond to strangers messaging you with investment advice or offers and read how to avoid being scammed from the posts below.
  • Do not invest in Bitcoin until you do basic research, paid off all high interest debt, and have a emergency savings account of a stable fiat currency.
  • If investing do not expect to get rich quickly. You should expect to wait at least 1-2 years before taking profits. Bitcoin is currently very volatile. In the interim spend and replace Bitcoin because its a useful currency.
  • Beginners should avoid all mining and day trading until at least very familiar with Bitcoin. Mining is very professional(You cannot efficiently mine with your computer and need to buy special ASIC machines) and most people lose money day trading.
  • Never store your Bitcoins on an exchange or web wallet. Buy your bitcoins and withdraw it to your personal wallet where you actually own them instead of IOUs. Services like Robinhood and Revoult should be avoided because you cannot withdraw or use Bitcoin.
  • Make sure you make a backup of your wallet(software holding keys to your BTC) and preferably keep it offline and physical and private. Typically 12 to 24 words you write down on paper or metal. This onetime backup will restore all your keys, addresses , and Bitcoins on a new wallet if you lose your old wallet.
  • Beginners should avoid altcoins, tokens, and ICOs at least initially until they learn about Bitcoin. Most of these are scams and you should be familiar with the basics first. Bitcoin is referred to as BTC or XBT.

Exchanges Requiring ID Verification

Bitcoin = BTC or XBT on exchanges
Exchange Buy fee* Withdraw BTC Notes
Cash App Sliding ~2.2% to 1% 0 BTC Instant Withdraw, USA only
Coinbase Debit3.99% ACH1.49% 1-4USD ~7Day hold BTC withdraw
CoinbasePro 0.5% 1-4USD ~7Day hold free ACH Deposit or €0.15 EUR SEPA fee
Gemini 1.49% to 0.25%ATrader 0 BTC 10 free BTC withdraws w/ActiveTrader
Kraken 0.16% 0.0005 BTC Deposit Fiat=USwire+5USD or SEPA free
Bitstamp 0.50% 0.0005 BTC Deposit Fiat=0 SEPA or 5% card fee
Note: Exchanges all have unique market prices and spreads so fees alone will not tell you the best rates. Best way is to directly compare the rates between exchanges. Buy fees above are for normal trading volumes. Verification and hold times can vary based upon lack of history, verification level or credit.
More exchanges per location
For a secure Decentralized Exchange (DEX) use https://bisq.network

Recommended Wallets

Best wallets for securing small amounts of BTC
electrum For Desktop and Android
Pros= Great Desktop and Android wallet with advanced functionality like coin control
Cons= UX is not as polished as some other wallets, make sure you only upgrade from official sources like play store or https://electrum.org as malicious servers or adverts can tell you to upgrade malware from other sites
https://www.youtube.com/watch?v=E4EhZg5QslI
Phoenix LN wallets for Android
Pros- Lightning network integration(as well as onchain) allowing you to spend with LN merchants for instant confirmations and much lower fees. Easiest lightning wallet to use
Cons- Lightning is still somewhat experimental and less merchants accept it.
https://phoenix.acinq.co/
https://www.youtube.com/watch?v=Cx5PK1H5OR0
Breez LN wallet for Android and IOS
https://breez.technology
https://www.youtube.com/watch?v=t_4b-y4T8bY
Pros- Lightning network integration(as well as onchain) allowing you to spend with LN merchants for instant confirmations and much lower fees
Cons- Lightning is still somewhat experimental and less merchants accept it.
Other Lightning wallets - http://lightningnetworkstores.com/wallets
Blockstream Green Wallet IOS and android wallet
Pros- Great UX, easy hardware wallet and full node integration, RBF, HW wallet support and advanced 2fa options Cons- Until single signature is released 2 of 2 multisig means that one must depend upon blockstream’s server for tx signing. Other light wallets are dependent upon other servers as well but light wallets like electrum allow you to swap servers.
https://www.youtube.com/watch?v=uO3Zi9D5b0Y
https://blockstream.com/green/
Securing Larger amounts of Bitcoin
ledger nano S wallet = ~68 USD https://shop.ledger.com/products/ledger-nano-s
https://www.youtube.com/watch?v=YI1OntWB7wc
https://www.youtube.com/watch?v=AGe2GgfkO64
trezor one wallet = ~54 USD https://shop.trezor.io
https://www.youtube.com/watch?v=pT1j_kbZBEo
Trezor Model T = ~164 USD https://shop.trezor.io
https://www.youtube.com/watch?v=i3BIo5Ac_n4
Cold Card Hardware wallet = 119.97 USD https://store.coinkite.com/store/coldcard
https://www.youtube.com/watch?v=kocEpndQcsg
https://www.youtube.com/watch?v=f8dBNrlwJ0k
Digital Bitbox 02 = 109 USD https://shiftcrypto.ch/bitbox02/
https://www.youtube.com/watch?v=tdP_7LgZw7s
https://www.youtube.com/watch?v=z7nRq2OEhiw
https://www.youtube.com/watch?v=6D4FgJo3j64
Best Advanced Bitcoin Wallet= Bitcoin Core
Pros= Great privacy and security
Cons= UX is for more experienced users, takes ~week to sync and requires ~5GB minimum disk space if prunned
https://bitcoincore.org/en/download/
Best High Privacy Bitcoin Wallet = Wasabi
Pros= Best Privacy with Chaumian CoinJoin built in
Cons= mixing coins costs more fees and for more advanced users
https://www.wasabiwallet.io/#download
https://www.youtube.com/watch?v=ECQHAzSckK0
https://www.youtube.com/watch?v=zPKpC9cRcZo&list=PLmoQ11MXEmahCG1nkbKK6DiAwVx9giJCi
https://www.youtube.com/watch?v=y8wQK-Ndl3Q&list=PLPj3KCksGbSaEmjU0sywoTYDVYYSu8LsS

Further Resources

https://www.lopp.net/bitcoin-information.html
https://www.lopp.net/lightning-information.html
https://10hoursofbitcoin.com/
http://bitcoinrabbithole.org/
https://bitcoin-resources.com
https://www.bitcoin101.club
https://21lessons.com
submitted by bitusher to BitcoinBeginners [link] [comments]

CashFusion SALE: 75% OFF for a limited time (~48 hours)! Yes, I will match your donation and bitcoin.com will match them again!

time's up! I will not double any more
I think fungibility is a very important property for cash to have. CashFusion is currently our best shot at ensuring it in BCH.
Now, the great team behind CashFusion is in need of some funding to get the product out of the door in safe way and I think the community should have no issues funding it.
Many donations (large and small) have already happened and I thank everyone who contributed and especially bitcoin.com for matching (hopefully) those donations once the goal of 50kUSD is reached.
Now I want to get it done and reach the goal of 100,000 USD asap. That's why I decided to match anyones donation to the Cash Fusion Fund setup by bitcoin.com up to 21 BCH for a period of roughly 48 hours.
In the future, thanks to projects like flipstarter, we'll probably be able to do this kind of thing in a more trustless manner, but for now you'll have to trust me to double your donations and all of us will have to trust bitcoin.com to double our contributions again.
TERMS
For any transaction (called "original tx") that matches the following criteria:
I will
Additional restrictions and conditions:
One last thing: please don't tip me here any substantial amount. I wont pass on any tips. I will have to pay income tax on tips
So go ahead: milk my wallet and let's get this thing funded!
EDITS / UPDATES
final stats
21 transactions matched, 7.46 BCH total, 35% of my 21 BCH used up
Thanks to everyone for participating!!! you guys are great!
time's up! I will not double any more
submitted by moleccc to btc [link] [comments]

Bread wallet malware on a Mac? Transaction went to wrong address.

So I sent my friend some Bitcoin , to her bread wallet. When she sent it out from there it went to a strange address, not where she wanted to send it. Here is the tx ID. I sent her just over 0.074 BTC. https://live.blockcypher.com/btc/tx/9f2a4b5b2d572491a79ff0ee7637215b7432ea954c7445d3f170ed22a8bb6fc7/ Is there some known malware?
Does anyone have any idea of what happened,
submitted by gregisanasshat 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]

Wrong send BCH to BTC wallet please HELP

Please I need help.
Yesterday I sent some BTC coin and then BCH coin from coinbase wallet to my Kraken account, Unfortunately by mistake in one some wallet which is only for bitcoin and naively hoping that the bitcoin cash would magically appear on my Kraken account.
Well, the BTC did appear, but no BCH bitcoin cash so far. I contacted the Kraken support team and here's what they told me.
We will review the details of your transaction and contact you as soon as possible. Thank you for your patience as we work to resolve this matter.
So I'm waiting for a solution and I'm worried about losing bitcoin cash.
My TX ID 921833ec1bd4fd3abdd5b39c516ae6720483d415b40bd89b9f53c07d34aada64
Would anyone be able to help me out on this one using the transaction ID in bold?
Thank you
submitted by RICHARDPIPEK to BitcoinCashTalk [link] [comments]

Bitcoin Server Mining for Android

I downloaded a bitcoin miner last year that seems to be Russian. It was an apk download and it gives you .005 BTC to start. You buy a 'miner' and let it run. It lets you withdraw at .05 BTC. The wallet address is linked to a CashApp account. I even got some kind of confirmation number that starts with "TxId:"
Anyone know anything that would help?
submitted by partyatwalmart to BitcoinBeginners [link] [comments]

[UPDATE][M] Ryo Currency 0.5.0.0 "Fermi Paradox"

[UPDATE][M] Ryo Currency 0.5.0.0
https://preview.redd.it/o6o6y8g9rwi41.jpg?width=1920&format=pjpg&auto=webp&s=fe52faff108d163f476907e004cac1ef47aaa1a9
[M] - Mandatory. The update contains security fixes or contains fork update (wallet will stop working after some height reach).
IMPORTANT: The latest version is 0.5.0.1 (contains minor update after 0.5.0.1)
Meet Ryo Currency 0.5.0.0 update - Fermi Paradox. In this update we will discuss 3 updates and do one announcement in the source code, 2 of them will be the first among any Cryptonote projects:
  • Wallet Scan speedup thanks to ECC and multi-threading library. Increased wallet scan speed when processing blockchain. New Elliptic Curve Cryptography library combined with implemented multi-threading that ustilises user's CPU results in reduced block verification up to 5x times compared with previous modes.
  • Plateau emission curve. Ryo's block reward changes every 6-months following a "Plateau Curve" distribution model. The modification of emission curve was initiated and debated with Ryo community. The following fork will finalise and implement that change.Notice: the difference between previous and this model will take effect at block height 394470.Read more about Ryo plateau emission curve
  • Various code edits, refactoring and minor fixes. There are multiple code fixes and edits that could be considered minor when looked in particular, but when looked in general - result in more than 35.000 lines of code being changed making core code more clean, optimised and bugfixed.Check Ryo Github repository
https://preview.redd.it/qv27xxdarwi41.png?width=2000&format=png&auto=webp&s=34836461eb348619f37f75fbc91e94a58dc065f8
Research and studies of Ryo Dev team showed that current ring signature technology as it is - is obsolete and has too many flaws to be considered as a means for reaching the goal of the second level of of privacy. Therefore we will be replacing ring signatures with second generation ZK-proofs technology in observable future and temporarily downgrade privacy level to 1.
In general, you can consider privacy levels like that:
  • level 0 - everyone can look into your wallet and know your transactions (BTC level)
  • level 1 - nobody can see inside of your wallet, but each note has a serial number (yes, this is real life money level and in CN coins is implemented using stealth addresses)
  • level 2 - notes you have don't have a serial number to a guy that gave you one, and no-one can't know if you spent it later (In CN coins it is implemented using ring signatures - which are the failing ones)
What we are saying is over the past year or two, researches stripped ring signatures of their privacy properties so much, that we think it is no longer fair to say that we (or Monero, which is even worse since it has even smaller ring size compared to Ryo) or any other CN project that uses it - meet the level 2 of privacy.
So, summarising in non-tech words what does it mean - when you are doing a transaction and want to imagine how it looks like in system:
  • bitcoin - "I spent output 10, worth 1 BTC and output 22, worth 0.5 BTC"
  • ring signature (current CN coins) - "I spent output 10, 14, 18 or 20, and output 16, 18, 19, or 22"
  • zk-proof - "I spent something."

Fork is scheduled on block 362000: you can check fork countdown on Ryo Currency website

Please update your wallets before this block, or your previous wallet will stop synchronising after the block 362000:
  • Ryo Wallet Atom: download latest Atom installer when annouced update to version 1.5.0, start it and perform reinstall.
  • Ryo cli binaries: download or compile from source updated binaries from Github version 0.5.0.0 and unzip it, and place your wallet key files in new folder.
  • Pool owners and exchanges are notified about updating their nodes to the latest version before the fork.
Questions you might have regarding the fork:
  • What will happen with mining algorithm - will it change or what does "fork" mean - coin is split on 2? No, "fork" basically means major code update that is being activated on a specified block height. There will be no mining algorithm change or chainsplit.
  • Ryo roadmap indicates that you had in plans reaching 100x ring sizes. In light of future introduction of ZK-proofs does it mean that this is not aplicable? Yes, we eventually will be replacing ring signature technology on ZK-proofs, which is more fundamental change than trying to "beat dead horse" with ring signatures.
  • What about atomic swaps? Ryo roadmap indicates it being planned, is it still possible with introducing ZK-proofs? Yes it is! And we aim to implement this feature after all necessary updates in core code. It is important to have everything implemented and tested before adding that feature.
  • What is a ZK-proof? ZK stands for zero-knowledge. In cryptography, a zero-knowledge proof is a method by which one party (the prover) can prove to another party (the verifier) that they know a value x, without conveying any information apart from the fact that they know the value xYou can read more about zero-knowledge proof (with real life examples) here.
  • Will blockchain grow faster (what about tx size) when moving to ZK-proofs? Overall, transactions and blocks using ZK-proofs will be even smaller in size than pre-fork ring signatures with bulletproofs! Plus it enables transactions to be aggregated together - this is obviously a major scalability gain for Ryo Currency.
  • I heard or as far I understand that ZK-proofs are somewhat less private? Does it mean that you are not privacy-oriented project anymore? No, in short - we decided to do this change to second gen. ZK-proofs, because ring signatures as is are too weak on providing enough for us default level of privacy and overall are considered now as an obsolete technology. So we don't want to say that we have a privacy level of 2, when research shows that it is not.
  • Ok, after 0.5.0.0 fork - will we be using uniform payment ID-s to do transactions on exchanges? Yes. There are no changes regarding usage of payment ID-s and integrated addresses. We will be still using ring signatures, but also are announcing our goal on moving to ZK-proofs.
  • What else is there in plans/ideas you have in development of Ryo? Besides all plans and development ongoing with Ryo (wallets, infrastructure, core code and researches) we also developed and improve Mining platform RagerX. It is a all-in-one mining platform that unites a miner, pplns pool, OS, GUI flasher utillity, pool frontend and has advanced social features as well as 2 level affiliate program. In observable future we will add Cryptonight-GPU mining possibillity.We are implementing RagerX so people can mine CPU coins and Ryo simultaneously. Which means more eyes on Ryo, especially from fresh members.
  • Are the ring signature issues that have been discovered are applicable to other ring signature based coins like Monero? Yes.
https://preview.redd.it/x5jqtb8brwi41.png?width=1000&format=png&auto=webp&s=06a0de33b10014e0fdf1b847939718475cbe6fbe
submitted by RyocurrencyRu to ryocurrency [link] [comments]

Paper Wallet Vanity addresses.

EDIT 2/21/2020. I am no longer offering the service described below as I no longer have access to the necessary hardware.
~~~~~~~~~~
Hey all,
I have recently been messing around with vanity addresses for paper wallets. After a little tinkering I got the system working well and can generate wallets up to a certain complexity quite reliably.
I've been able to generate wallets like this one: 1Bitcoinjqekek8HwmT8Cp8ojH9b7Quhzi
This one: 1Satoshi3A43v3Jk9MpfJPUDrWadFUUP6
And this one: 1Genesisud7wjt8Lkto75ANupmviwC2wpW
I personally haven't been using paper wallets for cold storage until now, but with the value of BSV going up and also having read the following paper about the possibility (albeit very small) of compromise of private keys in HD wallets, that for the BSV I intend to sit on long term, it's probably not the worst idea ever to use a paper wallet for that. But hey, it would be nice if those addresses were a bit more recognizable than a random address, am I right? :)
In going through this exercise, I happened to notice that there are services out there that will generate these kinds of addresses, but they seem overly expensive!
e.g., At vanity.coin.dance they want 1 BTC(!!) to generate an address starting with "Satoshi" e.g., like the "1Satoshi3A43v3Jk9MpfJPUDrWadFUUP6" I generated above. That's day-light robbery!!
Furthermore, the above service treats split key generation (which seems necessary for security when having a third party generate the wallet) as an "advanced" feature only. Imagine paying 1 BTC for an address only to have the private key compromised! (Seems almost negligent).
So anyway, whilst I have this system set up and working, I was thinking I could extend a temporary offer to anyone who is interested in getting a vanity address (or addresses) for paper wallet cold storage.
So all that said, the procedure, following the secure split key approach, would be as follows.
  1. You would go to bitaddress.org and download a local copy of the web site (and validate it against provided signatures).
  2. Run that downloaded copy of web site on an off-line system.
  3. Click the Vanity Wallet Tab.
  4. Click the "Generate" button in Step 1.
  5. Copy the public key from Step 1 and PM me with that key (it's quite long so copy/paste is the way to go). Also indicate in the PM the address prefix that you want (can't include invalid characters; I will tell you if you included any). Be sure to keep a copy of the private key from Step 1 (or keep the web page open). If you lose this key the whole process will be for nothing. Do not lose (or compromise) it (and definitely do not PM it to me!).
  6. Send payment (as per the schedule below) to 1Satoshi3A43v3Jk9MpfJPUDrWadFUUP6 and PM me the TxID.
  7. When I receive payment, I will generate a partial private key that you need for Step 2 in the bitaddress.org page.
  8. You take the partial private key that you generated in Step 1 (that you keep secure and never shared with anyone) and paste it into the first box in Step 2 in the Bitaddress.org page (that you are still running locally and off-line).
  9. Finally, you paste the partial private key that I PM you back, into the text box where it says "Enter Pool Part Private Key (from Vanity Pool):" (Note: PMing this partial private key is fine; so long as you keep your partial private key secure (from Step 1), the process is still secure; the process is intended to work this way).
  10. Click "Calculate Vanity Wallet" et viola! A wallet will be produced that meets your prefix requirement and is 100% secure since the partial private key that you generated in Step 1 never left your control.
What you do with your new shiny address from that point on-wards is your prerogative, the same as any other paper wallet that you produce. Our deal is done.
The pricing schedule for this (temporary) service is as follows:
  1. 3 Characters (e.g.,) 1BSVxxxx....xxx 0.01 BSV.
  2. 4 Characters (e.g.,) 1Coinxxx....xxx 0.02 BSV.
  3. 5 Characters (e.g.,) 1Coinsxx....xxx 0.04 BSV.
  4. 6 Characters (e.g.,) 1BuyBSVx....xxx 0.1 BSV.
  5. 7 Characters (e.g.,) 1Satoshi....xxx 0.75 BSV1.
(Footnote 1: Turns out most 7 character combinations are pretty hard to generate and may take quite a while to generate. The prefix "1Bitcoin", however, is not as hard (higher chance of generating), and I can do that one for 0.25 BSV).
(Note: I can't guarantee that I can deliver anything longer than 7 characters, hence there is no price for this).
(Note: The reason for the steep increase in price as a function of number of prefix characters is the time it takes to generate the addresses as they become exponentially more complex and the fact the process is non deterministic).
Compare the above price for a 1Satoshi... address (0.75BSV) to vanity.coin.dance (1BTC!!!) and hopefully you'll see that I'm being pretty reasonable with this, though do note that the "1Satoshi" prefix, specifically, is a hard one to generate and I may not be able to do it unless you are willing to wait a while.
Anyway, I'm not sure if anyone will be interested in this, and you'll have to trust me as someone who has been in this sub since the total membership was only in double digits, that I'm not a fly by night scammer who is going to take your payment and run! To that end I advise that I have made posts in this sub with direct reference to my Australian based registered business that accepts BSV as payment, so it's not hard to track me down. If you go back far enough you'll also see that I was involved in running a Bitstagram competition and came good with the BSV prize in that case. That said, a small amount of trust will be required if this is going to work out. Test me with one of the cheaper options first, if you have doubts.
Terms and Conditions
  1. Any PM received with an "order" is an offer by you to purchase a vanity address. It's not binding until I accept the offer in writing (by PM).
  2. All "orders" will be processed in the order they are received; I will guarantee a 48 hour turn around for everything up to 6 characters and 1681 hours (7 days) for 7 characters. In reality most will be processed much quicker, but I have to cover my ass! If I get too many orders (unlikely!!) I reserve the right to reject any that I cannot meet in a timely manner (any payments that have been made will be refunded to the specified address, less any BSV Tx fees).
  3. This offer is on the table until I withdraw it. I may withdraw it at any time by making a follow up post to this sub edit to this post.
  4. The address that is generated is the address that you get and that is final. If there is something in the address that you don't like (like a random swear word; albeit very unlikely) we can discuss a discounted rate to have a second try at it. (I'd rather you go home happy, if possible).
  5. If there is some address that I cannot generate in the above guaranteed time frames (some are harder to produce than others), I will let you know by PM and refund your entire purchase price.
  6. The entire risk of the use of the generated vanity address lies with you. (I recommend you test it with a small amount and make sure you can withdraw it, before loading it up for real).
(T&C Footnote 1: Some 7 character combinations can take a long time to find (e.g., "1Satoshi") and may take up to two weeks or more! I reserve the right to not even attempt to generate any specific combination that could adversely affect my ability to turn it around in a reasonably timely manner. In that case you can choose a different prefix or I will refund your money, if at that stage you had already paid). For any potential prefix I can check the estimated time to generate and report back on whether it's reasonable, before we agree to go ahead.)
ps/ Here are two three addresses that I generated showing that funds are able to be deposited and withdrawn successfully.
https://blockchair.com/bitcoin-sv/address/1Satoshi3A43v3Jk9MpfJPUDrWadFUUP6
https://blockchair.com/bitcoin-sv/address/1Bitcoinjqekek8HwmT8Cp8ojH9b7Quhzi
https://blockchair.com/bitcoin-sv/address/1BuyBSVMHGx6dSTpLMhALXvEPVEDMStxoR
Both addresses accepted funds and both allowed the BSV to be successfully swept (in this case I used Simply Cash to deposit and sweep).
~~~~~~~~~~
EDIT 2/21/2020. I am no longer offering the service described below as I no longer have access to the necessary hardware.
submitted by PaidSockPuppet to bitcoincashSV [link] [comments]

Possible another way to anonymize your Bitcoin

Possible another way to anonymize your Bitcoin
I have been thinking about another way of anonymizing on-chain Bitcoin beside using CoinJoin. Its basically by sending BTC through Lightning network over TOR and then back to on-chain BTC wallet. Does this make sense or I missing something?
hope the diagram clarifies... (different amounts sent each time so the amounts do not act as TX id)
https://preview.redd.it/old5vooouzd41.png?width=1537&format=png&auto=webp&s=7e01dbf8de366f9a4dca75801a6b4a6ab9d66e83
submitted by Iamme66 to Bitcoin [link] [comments]

FlowCards: A Declarative Framework for Development of Ergo dApps

FlowCards: A Declarative Framework for Development of Ergo dApps
Introduction
ErgoScript is the smart contract language used by the Ergo blockchain. While it has concise syntax adopted from Scala/Kotlin, it still may seem confusing at first because conceptually ErgoScript is quite different compared to conventional languages which we all know and love. This is because Ergo is a UTXO based blockchain, whereas smart contracts are traditionally associated with account based systems like Ethereum. However, Ergo's transaction model has many advantages over the account based model and with the right approach it can even be significantly easier to develop Ergo contracts than to write and debug Solidity code.
Below we will cover the key aspects of the Ergo contract model which makes it different:
Paradigm
The account model of Ethereum is imperative. This means that the typical task of sending coins from Alice to Bob requires changing the balances in storage as a series of operations. Ergo's UTXO based programming model on the other hand is declarative. ErgoScript contracts specify conditions for a transaction to be accepted by the blockchain (not changes to be made in the storage state as result of the contract execution).
Scalability
In the account model of Ethereum both storage changes and validity checks are performed on-chain during code execution. In contrast, Ergo transactions are created off-chain and only validation checks are performed on-chain thus reducing the amount of operations performed by every node on the network. In addition, due to immutability of the transaction graph, various optimization strategies are possible to improve throughput of transactions per second in the network. Light verifying nodes are also possible thus further facilitating scalability and accessibility of the network.
Shared state
The account-based model is reliant on shared mutable state which is known to lead to complex semantics (and subtle million dollar bugs) in the context of concurrent/ distributed computation. Ergo's model is based on an immutable graph of transactions. This approach, inherited from Bitcoin, plays well with the concurrent and distributed nature of blockchains and facilitates light trustless clients.
Expressive Power
Ethereum advocated execution of a turing-complete language on the blockchain. It theoretically promised unlimited potential, however in practice severe limitations came to light from excessive blockchain bloat, subtle multi-million dollar bugs, gas costs which limit contract complexity, and other such problems. Ergo on the flip side extends UTXO to enable turing-completeness while limiting the complexity of the ErgoScript language itself. The same expressive power is achieved in a different and more semantically sound way.
With the all of the above points, it should be clear that there are a lot of benefits to the model Ergo is using. In the rest of this article I will introduce you to the concept of FlowCards - a dApp developer component which allows for designing complex Ergo contracts in a declarative and visual way.

From Imperative to Declarative

In the imperative programming model of Ethereum a transaction is a sequence of operations executed by the Ethereum VM. The following Solidity function implements a transfer of tokens from sender to receiver . The transaction starts when sender calls this function on an instance of a contract and ends when the function returns.
// Sends an amount of existing coins from any caller to an address function send(address receiver, uint amount) public { require(amount <= balances[msg.sender], "Insufficient balance."); balances[msg.sender] -= amount; balances[receiver] += amount; emit Sent(msg.sender, receiver, amount); } 
The function first checks the pre-conditions, then updates the storage (i.e. balances) and finally publishes the post-condition as the Sent event. The gas which is consumed by the transaction is sent to the miner as a reward for executing this transaction.
Unlike Ethereum, a transaction in Ergo is a data structure holding a list of input coins which it spends and a list of output coins which it creates preserving the total balances of ERGs and tokens (in which Ergo is similar to Bitcoin).
Turning back to the example above, since Ergo natively supports tokens, therefore for this specific example of sending tokens we don't need to write any code in ErgoScript. Instead we need to create the ‘send’ transaction shown in the following figure, which describes the same token transfer but declaratively.
https://preview.redd.it/sxs3kesvrsv41.png?width=1348&format=png&auto=webp&s=582382bc26912ff79114d831d937d94b6988e69f
The picture visually describes the following steps, which the network user needs to perform:
  1. Select unspent sender's boxes, containing in total tB >= amount of tokens and B >= txFee + minErg ERGs.
  2. Create an output target box which is protected by the receiver public key with minErg ERGs and amount of T tokens.
  3. Create one fee output protected by the minerFee contract with txFee ERGs.
  4. Create one change output protected by the sender public key, containing B - minErg - txFee ERGs and tB - amount of T tokens.
  5. Create a new transaction, sign it using the sender's secret key and send to the Ergo network.
What is important to understand here is that all of these steps are preformed off-chain (for example using Appkit Transaction API) by the user's application. Ergo network nodes don't need to repeat this transaction creation process, they only need to validate the already formed transaction. ErgoScript contracts are stored in the inputs of the transaction and check spending conditions. The node executes the contracts on-chain when the transaction is validated. The transaction is valid if all of the conditions are satisfied.
Thus, in Ethereum when we “send amount from sender to recipient” we are literally editing balances and updating the storage with a concrete set of commands. This happens on-chain and thus a new transaction is also created on-chain as the result of this process.
In Ergo (as in Bitcoin) transactions are created off-chain and the network nodes only verify them. The effects of the transaction on the blockchain state is that input coins (or Boxes in Ergo's parlance) are removed and output boxes are added to the UTXO set.
In the example above we don't use an ErgoScript contract but instead assume a signature check is used as the spending pre-condition. However in more complex application scenarios we of course need to use ErgoScript which is what we are going to discuss next.

From Changing State to Checking Context

In the send function example we first checked the pre-condition (require(amount <= balances[msg.sender],...) ) and then changed the state (i.e. update balances balances[msg.sender] -= amount ). This is typical in Ethereum transactions. Before we change anything we need to check if it is valid to do so.
In Ergo, as we discussed previously, the state (i.e. UTXO set of boxes) is changed implicitly when a valid transaction is included in a block. Thus we only need to check the pre-conditions before the transaction can be added to the block. This is what ErgoScript contracts do.
It is not possible to “change the state” in ErgoScript because it is a language to check pre-conditions for spending coins. ErgoScript is a purely functional language without side effects that operates on immutable data values. This means all the inputs, outputs and other transaction parameters available in a script are immutable. This, among other things, makes ErgoScript a very simple language that is easy to learn and safe to use. Similar to Bitcoin, each input box contains a script, which should return the true value in order to 1) allow spending of the box (i.e. removing from the UTXO set) and 2) adding the transaction to the block.
If we are being pedantic, it is therefore incorrect (strictly speaking) to think of ErgoScript as the language of Ergo contracts, because it is the language of propositions (logical predicates, formulas, etc.) which protect boxes from “illegal” spending. Unlike Bitcoin, in Ergo the whole transaction and a part of the current blockchain context is available to every script. Therefore each script may check which outputs are created by the transaction, their ERG and token amounts (we will use this capability in our example DEX contracts), current block number etc.
In ErgoScript you define the conditions of whether changes (i.e. coin spending) are allowed to happen in a given context. This is in contrast to programming the changes imperatively in the code of a contract.
While Ergo's transaction model unlocks a whole range of applications like (DEX, DeFi Apps, LETS, etc), designing contracts as pre-conditions for coin spending (or guarding scripts) directly is not intuitive. In the next sections we will consider a useful graphical notation to design contracts declaratively using FlowCard Diagrams, which is a visual representation of executable components (FlowCards).
FlowCards aim to radically simplify dApp development on the Ergo platform by providing a high-level declarative language, execution runtime, storage format and a graphical notation.
We will start with a high level of diagrams and go down to FlowCard specification.

FlowCard Diagrams

The idea behind FlowCard diagrams is based on the following observations: 1) An Ergo box is immutable and can only be spent in the transaction which uses it as an input. 2) We therefore can draw a flow of boxes through transactions, so that boxes flowing in to the transaction are spent and those flowing out are created and added to the UTXO. 3) A transaction from this perspective is simply a transformer of old boxes to the new ones preserving the balances of ERGs and tokens involved.
The following figure shows the main elements of the Ergo transaction we've already seen previously (now under the name of FlowCard Diagram).
https://preview.redd.it/06aqkcd1ssv41.png?width=1304&format=png&auto=webp&s=106eda730e0526919aabd5af9596b97e45b69777
There is a strictly defined meaning (semantics) behind every element of the diagram, so that the diagram is a visual representation (or a view) of the underlying executable component (called FlowCard).
The FlowCard can be used as a reusable component of an Ergo dApp to create and initiate the transaction on the Ergo blockchain. We will discuss this in the coming sections.
Now let's look at the individual pieces of the FlowCard diagram one by one.
1. Name and Parameters
Each flow card is given a name and a list of typed parameters. This is similar to a template with parameters. In the above figure we can see the Send flow card which has five parameters. The parameters are used in the specification.
2. Contract Wallet
This is a key element of the flow card. Every box has a guarding script. Often it is the script that checks a signature against a public key. This script is trivial in ErgoScript and is defined like the def pk(pubkey: Address) = { pubkey } template where pubkey is a parameter of the type Address . In the figure, the script template is applied to the parameter pk(sender) and thus a concrete wallet contract is obtained. Therefore pk(sender) and pk(receiver) yield different scripts and represent different wallets on the diagram, even though they use the same template.
Contract Wallet contains a set of all UTXO boxes which have a given script derived from the given script template using flow card parameters. For example, in the figure, the template is pk and parameter pubkey is substituted with the `sender’ flow card parameter.
3. Contract
Even though a contract is a property of a box, on the diagram we group the boxes by their contracts, therefore it looks like the boxes belong to the contracts, rather than the contracts belong to the boxes. In the example, we have three instantiated contracts pk(sender) , pk(receiver) and minerFee . Note, that pk(sender) is the instantiation of the pk template with the concrete parameter sender and minerFee is the instantiation of the pre-defined contract which protects the miner reward boxes.
4. Box name
In the diagram we can give each box a name. Besides readability of the diagram, we also use the name as a synonym of a more complex indexed access to the box in the contract. For example, change is the name of the box, which can also be used in the ErgoScript conditions instead of OUTPUTS(2) . We also use box names to associate spending conditions with the boxes.
5. Boxes in the wallet
In the diagram, we show boxes (darker rectangles) as belonging to the contract wallets (lighter rectangles). Each such box rectangle is connected with a grey transaction rectangle by either orange or green arrows or both. An output box (with an incoming green arrow) may include many lines of text where each line specifies a condition which should be checked as part of the transaction. The first line specifies the condition on the amount of ERG which should be placed in the box. Other lines may take one of the following forms:
  1. amount: TOKEN - the box should contain the given amount of the given TOKEN
  2. R == value - the box should contain the given value of the given register R
  3. boxName ? condition - the box named boxName should check condition in its script.
We discuss these conditions in the sections below.
6. Amount of ERGs in the box
Each box should store a minimum amount of ERGs. This is checked when the creating transaction is validated. In the diagram the amount of ERGs is always shown as the first line (e.g. B: ERG or B - minErg - txFee ). The value type ascription B: ERG is optional and may be used for readability. When the value is given as a formula, then this formula should be respected by the transaction which creates the box.
It is important to understand that variables like amount and txFee are not named properties of the boxes. They are parameters of the whole diagram and representing some amounts. Or put it another way, they are shared parameters between transactions (e.g. Sell Order and Swap transactions from DEX example below share the tAmt parameter). So the same name is tied to the same value throughout the diagram (this is where the tooling would help a lot). However, when it comes to on-chain validation of those values, only explicit conditions which are marked with ? are transformed to ErgoScript. At the same time, all other conditions are ensured off-chain during transaction building (for example in an application using Appkit API) and transaction validation when it is added to the blockchain.
7. Amount of T token
A box can store values of many tokens. The tokens on the diagram are named and a value variable may be associated with the token T using value: T expression. The value may be given by formula. If the formula is prefixed with a box name like boxName ? formula , then it is should also be checked in the guarding script of the boxName box. This additional specification is very convenient because 1) it allows to validate the visual design automatically, and 2) the conditions specified in the boxes of a diagram are enough to synthesize the necessary guarding scripts. (more about this below at “From Diagrams To ErgoScript Contracts”)
8. Tx Inputs
Inputs are connected to the corresponding transaction by orange arrows. An input arrow may have a label of the following forms:
  1. [email protected] - optional name with an index i.e. [email protected] or u/2 . This is a property of the target endpoint of the arrow. The name is used in conditions of related boxes and the index is the position of the corresponding box in the INPUTS collection of the transaction.
  2. !action - is a property of the source of the arrow and gives a name for an alternative spending path of the box (we will see this in DEX example)
Because of alternative spending paths, a box may have many outgoing orange arrows, in which case they should be labeled with different actions.
9. Transaction
A transaction spends input boxes and creates output boxes. The input boxes are given by the orange arrows and the labels are expected to put inputs at the right indexes in INPUTS collection. The output boxes are given by the green arrows. Each transaction should preserve a strict balance of ERG values (sum of inputs == sum of outputs) and for each token the sum of inputs >= the sum of outputs. The design diagram requires an explicit specification of the ERG and token values for all of the output boxes to avoid implicit errors and ensure better readability.
10. Tx Outputs
Outputs are connected to the corresponding transaction by green arrows. An output arrow may have a label of the following [email protected] , where an optional name is accompanied with an index i.e. [email protected] or u/2 . This is a property of the source endpoint of the arrow. The name is used in conditions of the related boxes and the index is the position of the corresponding box in the OUTPUTS collection of the transaction.

Example: Decentralized Exchange (DEX)

Now let's use the above described notation to design a FlowCard for a DEX dApp. It is simple enough yet also illustrates all of the key features of FlowCard diagrams which we've introduced in the previous section.
The dApp scenario is shown in the figure below: There are three participants (buyer, seller and DEX) of the DEX dApp and five different transaction types, which are created by participants. The buyer wants to swap ergAmt of ERGs for tAmt of TID tokens (or vice versa, the seller wants to sell TID tokens for ERGs, who sends the order first doesn't matter). Both the buyer and the seller can cancel their orders any time. The DEX off-chain matching service can find matching orders and create the Swap transaction to complete the exchange.
The following diagram fully (and formally) specifies all of the five transactions that must be created off-chain by the DEX dApp. It also specifies all of the spending conditions that should be verified on-chain.

https://preview.redd.it/piogz0v9ssv41.png?width=1614&format=png&auto=webp&s=e1b503a635ad3d138ef91e2f0c3b726e78958646
Let's discuss the FlowCard diagram and the logic of each transaction in details:
Buy Order Transaction
A buyer creates a Buy Order transaction. The transaction spends E amount of ERGs (which we will write E: ERG ) from one or more boxes in the pk(buyer) wallet. The transaction creates a bid box with ergAmt: ERG protected by the buyOrder script. The buyOrder script is synthesized from the specification (see below at “From Diagrams To ErgoScript Contracts”) either manually or automatically by a tool. Even though we don't need to define the buyOrder script explicitly during designing, at run time the bid box should contain the buyOrder script as the guarding proposition (which checks the box spending conditions), otherwise the conditions specified in the diagram will not be checked.
The change box is created to make the input and output sums of the transaction balanced. The transaction fee box is omitted because it can be added automatically by the tools. In practice, however, the designer can add the fee box explicitly to the a diagram. It covers the cases of more complex transactions (like Swap) where there are many ways to pay the transaction fee.
Cancel Buy, Cancel Sell Transactions
At any time, the buyer can cancel the order by sending CancelBuy transaction. The transaction should satisfy the guarding buyOrder contract which protects the bid box. As you can see on the diagram, both the Cancel and the Swap transactions can spend the bid box. When a box has spending alternatives (or spending paths) then each alternative is identified by a unique name prefixed with ! (!cancel and !swap for the bid box). Each alternative path has specific spending conditions. In our example, when the Cancel Buy transaction spends the bid box the ?buyer condition should be satisfied, which we read as “the signature for the buyer address should be presented in the transaction”. Therefore, only buyer can cancel the buy order. This “signature” condition is only required for the !cancel alternative spending path and not required for !swap .
Sell Order Transaction
The Sell Order transaction is similar to the BuyOrder in that it deals with tokens in addition to ERGs. The transaction spends E: ERG and T: TID tokens from seller's wallet (specified as pk(seller) contract). The two outputs are ask and change . The change is a standard box to balance transaction. The ask box keeps tAmt: TID tokens for the exchange and minErg: ERG - the minimum amount of ERGs required in every box.
Swap Transaction
This is a key transaction in the DEX dApp scenario. The transaction has several spending conditions on the input boxes and those conditions are included in the buyOrder and sellOrder scripts (which are verified when the transaction is added to the blockchain). However, on the diagram those conditions are not specified in the bid and ask boxes, they are instead defined in the output boxes of the transaction.
This is a convention for improved usability because most of the conditions relate to the properties of the output boxes. We could specify those properties in the bid box, but then we would have to use more complex expressions.
Let's consider the output created by the arrow labeled with [email protected] . This label tells us that the output is at the index 0 in the OUTPUTS collection of the transaction and that in the diagram we can refer to this box by the buyerOut name. Thus we can label both the box itself and the arrow to give the box a name.
The conditions shown in the buyerOut box have the form bid ? condition , which means they should be verified on-chain in order to spend the bid box. The conditions have the following meaning:
  • tAmt: TID requires the box to have tAmt amount of TID token
  • R4 == bid.id requires R4 register in the box to be equal to id of the bid box.
  • script == buyer requires the buyerOut box to have the script of the wallet where it is located on the diagram, i.e. pk(buyer)
Similar properties are added to the sellerOut box, which is specified to be at index 1 and the name is given to it using the label on the box itself, rather than on the arrow.
The Swap transaction spends two boxes bid and ask using the !swap spending path on both, however unlike !cancel the conditions on the path are not specified. This is where the bid ? and ask ? prefixes come into play. They are used so that the conditions listed in the buyerOut and sellerOut boxes are moved to the !swap spending path of the bid and ask boxes correspondingly.
If you look at the conditions of the output boxes, you will see that they exactly specify the swap of values between seller's and buyer's wallets. The buyer gets the necessary amount of TID token and seller gets the corresponding amount of ERGs. The Swap transaction is created when there are two matching boxes with buyOrder and sellOrder contracts.

From Diagrams To ErgoScript Contracts

What is interesting about FlowCard specifications is that we can use them to automatically generate the necessary ErgoTree scripts. With the appropriate tooling support this can be done automatically, but with the lack of thereof, it can be done manually. Thus, the FlowCard allows us to capture and visually represent all of the design choices and semantic details of an Ergo dApp.
What we are going to do next is to mechanically create the buyOrder contract from the information given in the DEX flow card.
Recall that each script is a proposition (boolean valued expression) which should evaluate to true to allow spending of the box. When we have many conditions to be met at the same time we can combine them in a logical formula using the AND binary operation, and if we have alternatives (not necessarily exclusive) we can put them into the OR operation.
The buyOrder box has the alternative spending paths !cancel and !swap . Thus the ErgoScript code should have OR operation with two arguments - one for each spending path.
/** buyOrder contract */ { val cancelCondition = {} val swapCondition = {} cancelCondition || swapCondition } 
The formula for the cancelCondition expression is given in the !cancel spending path of the buyOrder box. We can directly include it in the script.
/** buyOrder contract */ { val cancelCondition = { buyer } val swapCondition = {} cancelCondition || swapCondition } 
For the !swap spending path of the buyOrder box the conditions are specified in the buyerOut output box of the Swap transaction. If we simply include them in the swapCondition then we get a syntactically incorrect script.
/** buyOrder contract */ { val cancelCondition = { buyer } val swapCondition = { tAmt: TID && R4 == bid.id && @contract } cancelCondition || swapCondition } 
We can however translate the conditions from the diagram syntax to ErgoScript expressions using the following simple rules
  1. [email protected] ==> val buyerOut = OUTPUTS(0)
  2. tAmt: TID ==> tid._2 == tAmt where tid = buyerOut.tokens(TID)
  3. R4 == bid.id ==> R4 == SELF.id where R4 = buyerOut.R4[Coll[Byte]].get
  4. script == buyer ==> buyerOut.propositionBytes == buyer.propBytes
Note, in the diagram TID represents a token id, but ErgoScript doesn't have access to the tokens by the ids so we cannot write tokens.getByKey(TID) . For this reason, when the diagram is translated into ErgoScript, TID becomes a named constant of the index in tokens collection of the box. The concrete value of the constant is assigned when the BuyOrder transaction with the buyOrder box is created. The correspondence and consistency between the actual tokenId, the TID constant and the actual tokens of the buyerOut box is ensured by the off-chain application code, which is completely possible since all of the transactions are created by the application using FlowCard as a guiding specification. This may sound too complicated, but this is part of the translation from diagram specification to actual executable application code, most of which can be automated.
After the transformation we can obtain a correct script which checks all the required preconditions for spending the buyOrder box.
/** buyOrder contract */ def DEX(buyer: Addrss, seller: Address, TID: Int, ergAmt: Long, tAmt: Long) { val cancelCondition: SigmaProp = { buyer } // verify buyer's sig (ProveDlog) val swapCondition = OUTPUTS.size > 0 && { // securing OUTPUTS access val buyerOut = OUTPUTS(0) // from [email protected] buyerOut.tokens.size > TID && { // securing tokens access val tid = buyerOut.tokens(TID) val regR4 = buyerOut.R4[Coll[Byte]] regR4.isDefined && { // securing R4 access val R4 = regR4.get tid._2 == tAmt && // from tAmt: TID R4 == SELF.id && // from R4 == bid.id buyerOut.propositionBytes == buyer.propBytes // from script == buyer } } } cancelCondition || swapCondition } 
A similar script for the sellOrder box can be obtained using the same translation rules. With the help of the tooling the code of contracts can be mechanically generated from the diagram specification.

Conclusions

Declarative programming models have already won the battle against imperative programming in many application domains like Big Data, Stream Processing, Deep Learning, Databases, etc. Ergo is pioneering the declarative model of dApp development as a better and safer alternative to the now popular imperative model of smart contracts.
The concept of FlowCard shifts the focus from writing ErgoScript contracts to the overall flow of values (hence the name), in such a way, that ErgoScript can always be generated from them. You will never need to look at the ErgoScript code once the tooling is in place.
Here are the possible next steps for future work:
  1. Storage format for FlowCard Spec and the corresponding EIP standardized file format (Json/XML/Protobuf). This will allow various tools (Diagram Editor, Runtime, dApps etc) to create and use *.flowcard files.
  2. FlowCard Viewer, which can generate the diagrams from *.flowcard files.
  3. FlowCard Runtime, which can run *.flowcard files, create and send transactions to Ergo network.
  4. FlowCard Designer Tool, which can simplify development of complex diagrams . This will make designing and validation of Ergo contracts a pleasant experience, more like drawing rather than coding. In addition, the correctness of the whole dApp scenario can be verified and controlled by the tooling.
submitted by eleanorcwhite to btc [link] [comments]

Bitcoin Basics - Get a Crypto Wallet How to find the transaction ID in your Blockchain.info ... Recover Bitcoin private key using hex editor - YouTube How to find your bitcoin address on Localbitcoins com ... Bittrex Bitcoin Withdrawal Transaction ID TXID.

Online Bitcoin Wallet (btc) Create a Bitcoin wallet online: no need to download and install applications. 6. Best Bitcoin Wallet for Android and IOS It doesn’t matter what’s in your mobile - Android or IOS. Bitcoin wallet is suitable for all devices and platforms, including Windows, Linux and Mac OS. 7. BrainWallet Generator You can use the wallet as a BrainWallet (Bitcoin Brain Wallet ... Bitcoin Wallet ist sicherer als die meisten anderen Bitcoin-Wallets, weil sie einen direkt mit dem Bitcoin-Netzwerk verbindet. Bitcoin Wallet hat ein simples Interface und genau die richtige Menge an Funktionen, die sie zu einer großartigen Wallet und einem großartigen Lernhilfsmittel für Bitcoin-Anfänger macht. Kapitel 5 Bitcoin Banken: 10 Mrd. USD durch Hacks verloren. Eine letzte Sache ... About open source bitcoin wallet. txid.io is a fork of Coinb.in Wallet. Compatible with bitcoin core. Wallet code itself cutted out, improved manual transaction processing, Double-spending tool added. Legacy, Segwit and Bech32 addresses are supported. txid.io has been updated at 2019-03-17, BCC and BTG removed and no longer supported. TXID can be displayed right away in a cryptocurrency wallet when a particular transaction is carried out by a user. In addition, you can find TXID using the services mentioned above. To do this, you will need a sender's cryptocurrency wallet address. For example, on blockchain.com it should be entered in the search box. The service will then show all transactions sent from this particular ... The console window in the Bitcoin Core Wallet. If you have been given a TXID by your bitcoin wallet, it’s probably already in its “searchable” format (reverse byte order).. 2. Spending outputs. You use a TXID when you want to use an existing output as an input in a new transaction.. To refer to an existing output, you use the txid it was created in, along with the vout number for that ...

[index] [7809] [32536] [17223] [26327] [47759] [8381] [44356] [23912] [19537] [37993]

Bitcoin Basics - Get a Crypto Wallet

Enjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube. How to find the transaction ID in your Blockchain.info Bitcoin wallet - Duration: 2:20. Hugh Broodryk 36,594 views. 2:20. Sicheres Bitcoin Wallet erstellen - Schritt-für-Schritt Anleitung - Electrum Deutsch Geldbeutel 🔒 - Duration: 9:07. Talerbox Invest Smart 140,646 views 9:07 Not on Coinbase Yet? Join Here: https://www.coinbase.com/join/5a0579e45698da00e3e10b86 A quick tutorial that shows you how to find a bitcoin transaction ID (... Enjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube.

#