|
Notice: this procedure is for "normal" paper wallets... you know, the kind of paper wallet that shows an address and a private key... If your paper wallet is actually a seed phrase, there is a different procedure for you...
to transfer your paper wallet to a native segwit ledger, i'd personally suggest to:
1) couple your ledger with electrum, verify the first couple of addresses (they should match between electrum and ledger)
2) in electrum go to the following menu: "wallet" => "private keys" => "sweep"
3) enter the private key from your paper wallet (it might be necessary to decrypt the private key using the tool you used to generate the paper wallet)
4) there is no step 4... It's done
Electrum's history tab will show the unconfirmed sweeping transaction, to answer the second part of your question: right click on said transaction and chose "view on block explorer" in order to track the transaction.
Last point: this procedure isn't exactly what you asked for... But it's what you need (IMHO). This procedure WILL move your funds from the paper wallet onto your ledger device, the balance on your paper wallet will be "0" after this procedure. Odds are small your paper wallet is native segwit, and even then, you can ONLY sweep your paper wallet when using a HD wallet like ledger, AFAIK you cannot import private key(s) into an electrum HD wallet, especially not if said HD wallet is coupled to a hardware wallet.
You could, theoretically, create a non-HD electrum wallet and import the private key from your paper wallet into this non-HD wallet so you can manage your paper wallet as if it were a desktop wallet. This way your wallet is NOT coupled to your ledger, it is NOT as secure as a hardware wallet... Even worse: i'd consider it compromised since setting it up required a lot of manipulations with the private key...
A "default" electrum wallet is a HD wallet, a ledger wallet is ALWAYS a HD wallet. HD basically means that all private keys are derived from a master private key. This also means there is no way to add your own private keys to the wallet... This also means you cannot import your private keys from paper wallet(s) onto a ledger (unless your paper wallet is actually a HD wallet to??? Which IS possible but uncommon... If this is the case, let us know).
|
|
|
|
--snip--
Can you also post a link for this product or specify what model it is [looks like a Russian product but I can't figure out those parts]?
running it by google search, i end up here: https://solnyshco24.com/catalog/kvarcevye-i-baktericidnye-lampy-obluchateli/oufd-01-solnyshko-obluchatel-ultrafioletovyyI'm not Russian, so i can only guess here, but does 2090 reflect the price in roebles? In that case, the price is ~24€, or $28 Offcourse, not being Russian, I have no idear if the site i linked is true, or if it's a scam, nor do i have any idear what the S&H and import costs are, nor do i know anything about the guarantee or the manual... |
|
|
|
I'm kind of speaking outside of my comfort zone here, cause i know little about ETH... But i did start my own ETH network a long long time ago for testing purposes. IIRC, it was basically just downloading ETH's binary, adapting some parameters and start mining the new genesis block... You basically had to do 0 changes in the sourcecode, just adapt some parameters and: voila, an ETH clone  That's why ETH has several testnets, compared to BTC clones which only have one... This is just from memory tough, but i just mean it's possible you can clone ETH without editing a single line in the sourcecode, which would make your enterprise more feasible. Still, NeuroticFish gives a warning similar to mine: even a wellmade coin with distinct features is destined to fail if there is no real usecase, no real usebase, no services and no maintenance... |
|
|
|
|
What kind of hardware? Last time i cloned a coin as a learning experience, i just installed 2 virtual machines on my laptop to serve as 2 nodes... That's about it...
In the beginning, the diff will be so low that you can easily cpu mine the first couple of blocks, and in order to compile the sourcecode you don't need an expensive machine, any recent desktop/laptop will probably do.
If you want to start an actual network, you might think about renting out 2 super cheap VPS's to serve as initial nodes... You can have a VPS to serve as a node for $5/month (or even less if you put you put a lot of effort into your search).
If you want a block explorer, a pool and a project website, you might want to throw in one or 2 extra VPS's (eventough those services could just aswell run on your 2 nodes).
Cloning a coin is not hard. Maintaining it, giving it value, creating a community and finding an actual pupose for your coin on the other hand are tough (i guess). Wouldn't it be better to use an existing project? Or if you really want your niche to have it's own "coin", maybe an ETH token will work aswell? Those contracts are readily available, setting up an ETH token costs (quite literally) a couple bucks, and you don't need to worry about pools, explorers and miners...
Just a last thing to think about: the current crypto ecosystem is completely flooded with crapcoins/tokens. It might be a good idear to find out if anybody is actually interested in such a project before you push the next coin/token online... Personally, things like ICO, IPO,... give me the shivers. It has a negative connotation in my mind.
|
|
|
|
--snip--
Thank you, that's what I wanted. I'm going to make some tweaking.
I apologize for the late reply. I travel a lot these days so I don't have much time left.
no problem It's a really basic framework... There are many things you could do... Like for example, import "net/smtp", add the following function and invoke it after line "if responseObject.Fastfee < triggerfee {" func mail() {
from := "--your mail--"
password := "--your password--"
to := []string{
"--your mail--",
}
smtpHost := "--an smpt server--"
smtpPort := "--an smpt port--"
message := []byte("Fee currently low")
auth := smtp.PlainAuth("", from, password, smtpHost)
err := smtp.SendMail(smtpHost+":"+smtpPort, auth, from, to, message)
if err != nil {
fmt.Println(err)
return
}
}
or, you could download irfanview portable and make an image with a big red text "fee currently low" and just replace L41-42 with app := "c:\\irfanview.exe"
arg := "c:\\alertimage.jpg"
or, you can have a look at https://github.com/faiface/beepI picked go because it's so easy to create binaries and crosscompile... But a python, perl or php version should also only take 10 minutes to create in case you want a different language |
|
|
|
So, the walktrough is perfectly valid IF you're planning to migrate from electrum to core, and never use electrum again... I don't want to be presumptive, but I'm almost sure what mocacinno meant is that you should not use Electrum with the same wallet again. You can still use both, but his warning is valid if you plan to keep using the same wallet in both clients. exactly yeah, i did not mean that the OP could never use electrum again, just not the wallet he tried to export from electrum to core I don't want to go on a tangent, and I think the answers given are the best method for the OP, but this brings up another question that isn't at all off topic; in this post HCP discusses using a tool designed to convert a mnemonic seed to a WIF private key which can be used as an HD seed by core. Here's a link to the tool: https://github.com/tekbe/wallet-toolsI haven't used this method myself, and I'm not promoting the tool, but I'm curious if it can be used to obtain the WIF HD seed that correlates to the Master Private Key generated by an Electrum mnemonic seed. A rainy day experiment, perhaps. I might be mistaking, but i think that tool converts a mnemonic to a seed, but the result of using the mnemonic into electrum and using said mnemonic together with this tool to create a seed will result in two completely different wallets... Not 100% sure tough. Simply put: it's a tool to make simpler backups of your core wallet (since we're all used to backup seed phrases by now), but using electrum's seed with this tool and importing the output into core is not the same as restoring an electrum wallet into core. |
|
|
|
I'm not a fan of unmerged double posting, but since my last post was several days ago, and i'm actually replying to myself here: I did a quick-and-dirty 10 minute sollution for your problem in go... No fancy clean code, just a quick and dirty code that should do the job... https://github.com/mocacinno/autofeecheckerYou'll need go (which is available for most platforms) It'll need some tweaking from YOU in order to work properly tough... You'll need to edit lines: https://github.com/mocacinno/autofeechecker/blob/main/checker.go#L41https://github.com/mocacinno/autofeechecker/blob/main/checker.go#L42(replace "ls" by the command you want to see executed if the feerate drops, and "-ltrh" by the parameters for this command... I don't know, play a sound, open an image with irfanview, send a mail... whatever gets your attention) Then build (how-to is in the README.md) Then add checker (or checker.exe) with parameter "-altertfee xx" in your systems cron (or task sheduler). Once the fee drops below the alertfee, the command you entered on line 41 with parameter on line 42 will be executed. If you want to, you can add a loop and a sleep around line 25-51 to continue running it in the background |
|
|
|
--snip--
I'm a firm believer that people will be better off if we answer their questions then and there, else they could lose interest in crypto for not understanding how it works.
I agree with you, but only up untill a certain degree. In this case, the OP seems to be learning by understanding only a very little bit of the technical details, forming a conclusion based on nothing but assumptions, then making propositions that are based on his wrong assumtions and posting them in a public forum. Then other people (like us) have to take the time to debunk these propositions, and the OP might feel hurt because we seem to be doing nothing but disagreeing with him. I just think this is a way of learning that's not efficient, not for him, not for us... So it would be better if he just read a good book, a whitepaper or watched one of those in-depth youtube videos... That way he could start with a better background understanding and ask questions that are more to the point. It would be less frustrating for him and a lot faster for everyone. I think most people that know me, know that in general i'm not the worst guy around here (when it comes to newbie-friendlyness)... I usually try to give newbies a hand.. In this particular case i just think the OP has to change his strategy from "posting things he knows little about" to "reading before posting". It's not only about this thread tough... OP has been here for exactly 8 posts, and already he has made numerous completely wrong assumptions AND even promoted using bank's custodial wallets to hold your funds as the ideal sollution: https://bitcointalk.org/index.php?topic=5318971.msg56403261#msg56403261It seems like every time he starts a thread, people jump in and contradict him at every turn because he lacks the basics... Can't be fun for him either.. Just my 2 satoshi's tough... You're welcome to keep on answering questions if you want to, obviously you're free to do so |
|
|
|
1. So when it takes 20 minutes to produce one transaction, this 20 minutes has nothing to do with the number of people trying to produce a transaction at the same time? Example: What if only one person vs 1 thousand people was trying to do a transaction at the same time?
This ^^ is what i was talking about in my previous post... I don't mean to offend you, but you're talking about technical details based on wrong assumptions. You really need to read the whitepaper, or at least a decent book or a series of blogposts by knowledgeable people before you continue on your quest for answers It takes a very short time to produce a transaction. Transactions are created by your own wallet, and if your wallet would ever take 20 minutes to create a transaction, something must be wrong on your end. Creating a transaction and broadcasting it are two different things (eventough, some wallets make it look like it's just one procedure). An unlimited amount of people can create and broadcast an unlimited amount of transactions (well, from a physical point of view, there are limitations to the hardware and network connectivity). This doesn't mean all these transactions can fit in the mempool of most of the nodes in the network, nor does it mean that all these transactions will end up in a block (blocksize is limited, the average time between 2 blocks is ~10 minutes which is regulated by the difficulty retargets) But, i feel like answering these questions won't do you any good... you really need to brush up on the basics before you go any further... We're happy to answer your questions and applaud new people to enter our community, but we cannot give you private education on the basic principles, especially not in the very inefficient form of answering these questions... you need to do that by yourself, and if you have questions that aren't readily found in books, whitepapers and youtube video's: please ask them. Good luck. |
|
|
|
|
It's important to note that, following the walktrough to export private keys from electrum and importing them into bitcoin core, you will only export private keys that are currently derived from the xprv. It's possible unused addresses's private keys are also exported, but defenatly not past the gap limit (you should check this for yourself)
This basically means that: if you follow this tutorial AND keep using electrum and core seperately, there'll be a point where your bitcoin core wallet will no longer have all private keys that are derived by electrum, and your core and electrum will diverge. Also, when creating a new address in core, this address will not be managed by electrum!
So, the walktrough is perfectly valid IF you're planning to migrate from electrum to core, and never use electrum again... It's not valid if you plan on using electrum and core next to eachother. By the way: don't forget to make backups from your core wallet...
|
|
|
|
2,5 million/BTC seems a bit unrealistic to me... But still... Let's assume that in a couple of years, about 20.000.000 exist. Satoshi isn't around anymore, so at least 1.000.000 BTC are lost. Let's (for the sake of argument) say that most of those oldtime holders decide to sell their holdings, and 15.000.000 BTC are in circulation (this is a big stretch). The monetary value of those 15.000.000 BTC would be 15.000.000 x 2.500.000 = 37.500.000.000.000 There are 8.000.000.000 people in the world. That's ~4700 USD worth of BTC for each inhabitant of earth. If you assume only half of the population holds btc, that's still only $9400 worth of BTC/person. This wouldn't make half of the earth's population millionaires i'm afraid... Let's add the fact that i don't see 2.5 million/BTC exchange rate, and i don't see those longtime holders all selling their stash to get a circulation of 15.000.000... This tweet from glassnode is interesting: https://twitter.com/glassnode/status/1344020551942238212They estimate only ~5.000.000 BTC to be in circulation. This makes the claim you sometimes see that guesses BTC might rise to $500.000 by the end of the year at least plausible: (5.000.000 x 500.000 ) / 8.000.000.000 = $312 worth of BTC/inhabitant of earth. Even if only 1% of the population holds btc, it would only be $31.200 worth of BTC/holder. I see this as overly optimistic, but not completely inpossible. |
|
|
|
|
if you find a free or public api, or if you run your own node, this is pretty trivial (especially since you say you have python experience)
basically importing requests, and adding a little bit of logic would be sufficient...
If i have some spare time, i'll see if i can whip something up in python or go (no promises tough, but i think it would be finished in 15 minutes)
|
|
|
|
--snip-- 1. Can the protocol be changed? What if changing the protocol solves the above 3 problems which are limiting bitcoin as a currency for regular transactions? 2. If you have a limited number of networks say 10,000 to process a transaction this should reduce transaction time? And/or how many miners does it usually take to process a transaction? Not every miner right?  @OP Without digging into these questions (#2 was actually answered in my previous reply), i wanted to tell you that it's clear to me you've done some reading about bitcoin and it's protocol, but it's also pretty clear you're not there yet... There's a lot you've missed. I'm treating this thread as a learning thread... You've read some things and drew some wrong conclusions. Now, based on these wrong conclusions you're asking stuff that actually makes little sense, but you're digging deeper and deeper into questions that make little technical sense and people keep answering them on a techical level without pointing out your initial assumptions are just based on the wrong conclusions... This is the point were i'd urge you to go back to the drawing board... Read up on bitcoin and it's protocol, and then come back and read our answers... By the time you understand where you drew the wrong conclusions, you can actually tell yourself you've learned something new Once again: bitcoin has a steep learning curve, especially if you want to know the nitty-gritty technical details. It's perfectly normal you don't understand everything at your first try. Asking questions is perfectly fine... Good luck! |
|
|
|
|
that is, in fact, a good question.... To be honest, i've never tried to import modules from electrum's console.
When trying right now, i had a similar experience, so you're probably correct in saying you cannot import external modules in electrum's console... Maybe we can leave this thread open to see if ThomasV has some additional info about this?
|
|
|
|
Where did you get the console function random_key()? It doesn't seems to be a function from electrum... https://github.com/spesmilo/electrum/search?q=random_key>>>commands()
"add_lightning_request add_peer add_request addtransaction broadcast changegaplimit clear_invoices clear_ln_blacklist clear_requests close_channel close_wallet commands convert_xkey create createmultisig createnewaddress decode_invoice decrypt deserialize dumpgraph dumpprivkeys enable_htlc_settle encrypt export_channel_backup freeze get get_channel_ctx get_ssl_domain get_tx_status get_watchtower_ctn getaddressbalance getaddresshistory getaddressunspent getalias getbalance getconfig getfeerate getinfo getmasterprivate getmerkle getminacceptablegap getmpk getprivatekeyforpath getprivatekeys getpubkeys getrequest getseed getservers gettransaction getunusedaddress help import_channel_backup importprivkey inject_fees is_synchronized ismine lightning_history list_channels list_invoices list_peers list_requests list_wallets listaddresses listcontacts listunspent lnpay load_wallet make_seed nodeid normal_swap notify onchain_history open_channel password payto paytomany removelocaltx restore reverse_swap rmrequest searchcontacts serialize setconfig setlabel signmessage signrequest signtransaction stop sweep unfreeze validateaddress verifymessage version"
|
|
|
|
|
euhm..... Nope....
If you reduce the number of miners (not that that's technically possible the way the network is currently designed), the only thing that would happen is that the network hashrate would drop.
This would make the time between two blocks longer untill the next retarget.
Longer time between 2 blocks => more unconfirmed tx in the mempool => higher fees
So, even if it was theoretically possible to limit the amount of miners, doing so would increase the fees, not lower them (at least, untill the next retarget, at that point you would have just made the network less secure with no impact on the fees)...
|
|
|
|
did you go off on opensuse leap or tumbleweed? Leap is a pretty good OS. I have about 200 SLES (suse linux enterprise) machines running without a hitch for many, many years... They're churning huge workloads (sap application servers, opentext, hana, oracle,...) and they run smoothly. And (eventough i've never ever run leap, only sles),leap is marketed as the free version of the enterprise OS. If you want something stable, you might want to stay away from tumbleweed... This is why i asked you witch version: it's perfectly possible you were running tumbleweed, and it turned you off of opensuse, whilst leap might be a perfect fit for you On the other hand, privately, i sometimes go with CentOS (eventough it seems they're currently rethinking their model) since it's basically the free version of redhat, like opensuse leap is the free version of SLES. If i need a system i'll be messing with extensively, i usually go for a good'ol debian... And in the past i used to be a big fan of freebsd: use the port system to compile what you need, exactly how you need it... Nothing more, nothing less. But you asked linux distros, and freebsd is technically unix, not linux  But it usually boils down to preference: if you ask 100 linux users which distro is best, you'll get at least 10 different answers, each with perfectly valid arguments... The same argument can be a "pro" for one person and a "con" for a different one btw Truth be told, if you know what you're doing, it shouldn't actually matter: opensuse leap, centos, debian, fedora, gentoo, tails, bsd... even ubuntu can be ok for a crypto laptop if you properly manage it. Just stay away from those "mom and pop" distros with a small userbase and infrequent updates, stick to the bigger ones and learn how to harden your setup properly... And if you have questions: ask them, your money is at stake. Good luck! |
|
|
|
--snip--
But "nV" isn't part of it, otherwise the number of characters fits indeed:
--snip--
Oops... missed that part... You're right |
|
|
|
|
64 characters... Probably hexadecimal...
You can use bitaddress.org's sourcecode and run it from an OFFLINE machine, go to the last tab (wallet details), paste it there, and get the private key in WIF format.
WIF = wallet import format... It should be importable in electrum.
This being said: it's still possible you enabled bip38 encryption, in this case you'll need to enter the password in the last tab of bitaddress.org's tool.
|
|
|
|
|
back in the days, i remember playing around with those swf's... IIRC, there used to be tools to decompile them and look at the sourcecode? Maybe you can find a hint therein?
|
|
|
|
|
Show Posts
