Thanks for your reply but I think normally Bitcoind should start no ? When you notice the Tutorial of the Youtube Video: https://www.youtube.com/watch?v=W54aRszkEOI, we notice that after the installation of Bitcoind and its launch, we see a message of the kind : " Bitcoin server starting". So why in my case I do not get the same message (bitcoin server starting) ?Thank you for replying and if possible give me another directive regarding why I do not get the message "bitcoin server starting".You do not get that message because you do not have the -daemon option in the command line args or have daemon=1 in your bitcoin.conf. Without those, bitcoind will not be in daemon mode so there will be no messages to the terminal and it will appear to hang. However, it is not hanging, it is in fact starting. |
|
|
|
|
What are the specs of your machine?
Bitcoin Core is very resource intensive and will often make hardware issues much more obvious. It sounds like you have a hardware issue, probably one of your drives is bad. Do a full hardware diagnostic to see if it finds anything wrong with your hardware.
|
|
|
|
Now I try to run "bitcoind" in the Linux Terminal but nothing appears
That is what is supposed to happen. Bitcoind is not supposed to output anything to the terminal, if it does, something has gone wrong. Bitcoind has started when you see it "hang". Check in the processes list, you will see it there. In order to interact with it, you need to use bitcoin-cli in a different terminal. Or you can run bitcoind with -daemon so you can use bitcoin-cli in the same terminal. |
|
|
|
Bitcoin Core version v0.14.1 (64-bit)
Yes and Yes..
Armory 0.95.1 will have issues with Bitcoin Core 0.14.0+. You either need to downgrade Bitcoin Core to 0.13.2 or upgrade Armory to the 0.96 testing build. Once you get the versions sorted out, in Armory, go to Help > Rebuild and Rescan databases then restart it. |
|
|
|
|
Any sort of referral or affiliate link is against forum rules. You are not allowed to post any such links here. If you make a post containing one, it will be deleted. If you do it multiple times, you will be banned.
|
|
|
|
TBH, I dont know any interesting projects I can work on. Most of them are way too complex for me.
They may be complex, but you don't necessarily have to work on the complex stuff. There are always simple things and small changes that can be made in every project. Not all parts of the project are linked to other parts so you don't need to understand everything. There are Bitcoin projects in nearly all popular programming languages. Just search around and I'm sure that you will find one that has simple enough issues that you can fix to get your foot in the door. |
|
|
|
Makes sense. More straightforward than I would have guessed. It is basically a blockchain tranx that enables 0 time exchange of coins that both parties signed off on instead of the network signing off on the transx.
Is there any interest in applications that have LN enabled that parties can make an agreement based on set conditions lined out? Similar to smart contracts on ETH, but instead of the blockchain enforcing the contract, the LN regulates the conditions. When both parties sign the contract(actually sign each condition met,) then coins are exchanged. Correct?
I don't think LN will facilitate smart contracts like that. The limitations of that are due to transaction scripts since LN is really just a different way to make Bitcoin transactions. What about "multi-party" transactions. Say I want to send 1 BTC to Alice, Bob, and Charlie. 0.4 to Alice, 0.5 to Bob, and 0.1 to Charlie. The current implementation does not allow this does it? Could this be alleviate with multiple keys signing off on my transx with a contract? Of course, if one of the third-parties refuses to sign, then the transx cannot commence, unless conditions say otherwise.
It is possible to have more than 2 parties in a payment channel, but it can get very messy very quickly due to the number of possible outcomes that could happen. The current lightning spec does not allow for more than 2 parties in a channel. |
|
|
|
|
Asking for people to give you money (aka begging) is against forum rules, regardless of the supposed circumstances. You are not allowed to make any such thread asking for people to donate money to you.
|
|
|
|
1.) What exactly does the LN transx accomplish that a general transx fails to do?
LN allows two parties to transact between each other without having to make an on chain (and thus costly due to fees) transactions for each transaction that they want to perform. If two people were to make 5 transactions on an LN channel, instead of paying 5 transactions worth of transaction fees, they would only need to pay 2 transactions of transaction fees (opening and closing transaction). 2.) ELI5 the mechanics of LN and the transx that occur.
Two people decide to make a LN payment channel. They make a transaction that sends Bitcoin to a 2-of-2 multisig address. Then they make another transaction which spends from the multisig address and sends Bitcoin to their own addresses. This second transaction is not broadcast. When one person in that channel pays the other person, they remake the second transaction and change the amount that their address will receive. Again, this transaction is not broadcast. They repeat that step as long as they want. When both people decide they no longer want to continue transacting with each other, the last transaction that they had created will be broadcast to the network and they will receive the Bitcoin back to their addresses to be used elsewhere. How is the transaction validated onto the blockchain after coins are moved?
LN transactions don't touch the blockchain until the channel is closed. 3.) What are channels? How does one "open/close" one? Can you create one?
Channels are opened by both people in the channel sending some amount of Bitcoin to a 2-of-2 multisig address. Channels are closed by broadcasting a transaction which spends from the multisig address and sends some agreed upon amount of Bitcoin back to the addresses of the people in the channel. If any payments over the channel had occurred, then when the channel is closed, both people will likely have a different amount of Bitcoin coming out of the channel than they had put into the channel. 4.) What incentives are there for miners/nodes on the network?
Miners and nodes are not directly involved in LN. However there can be LN nodes, i.e. people who have lots of channels open with other people so payments can be routed through him. 5.) Is there simply a single LN, or can there be several networks running concurrently alongside the blockchain?
LN is one specification of a payment channel network. There can be others as well, and you can have LN payment channels without actually being connected to any other channel in "the network". 6.) What is the bridge between LN and applications running alongside the blockchain?
LN transactions are still Bitcoin transactions. |
|
|
|
|
You can contribute to existing open source projects. Find bugs or look at what people are reporting as issues and then fix those and submit pull requests.
|
|
|
|
There is no such thing as a "standard transaction fee". That just means that you are either using a fixed fee (which is what looks like happened) or a fixed fee rate. Neither of those things are good, you should always use a dynamic fee rate that adjusts based upon the current network state. The transaction fee is also dependent on the size in bytes of your transaction, not the amount being transacted. Telling us the amount being transacted (especially saying it in fiat and not Bitcoin) is useless. The reason your transaction is still unconfirmed is because its fee rate is much too low. It only pays a fee rate of ~26 sat/byte whereas the current recommended fee rate is ~180 sat/byte according to https://bitcoinfees.21.co/. Read https://bitcointalk.org/index.php?topic=1802212.0 for what you can do about the transaction. |
|
|
|
|
What version of Bitcoin Core are you using? Is Bitcoin Core fully synced? Is Armory fully synced?
|
|
|
|
I've been complacent with stuff that just works and it's been so long that I barely even remember how I first installed Armory and bitcoind but I think it's time that I upgrade.... I've been going through the forum trying to piece together the best practices and best routes to take in doing this but I'd like some advice. Currently I am running Armory 0.93.3 on Ubuntu 15.10 along with Bicoin Core 0.13 (v0.13.0.0-ga402396).
My first question is a confirmation that what we're essentially doing is reinstalling Armory (not bitcoind) and restoring the wallet from a backup. Am I correct on this?
There is no need to restore the wallet from a backup. Upgrading does not touch any of the data which is stored in a separate location from the install itself. Secondly, what are the compatible bitcoind versions for each Armory version? Can any newer version of Armory always support an older version of bitcoind? My main reason for asking this is I don't like to change too much in one shot.... if I can update on component and run it for a while and then later update the next component it makes me feel a little better so I don't bury myself with problems.
You won't be able to use Core 0.14.0+ with any Armory version <0.95.1 (inclusive). This has been fixed for 0.96. Other than that, there shouldn't be any compatibility issues. I think my last question is what version should I upgrade to? Does it make sense to first upgrade to 0.94.1 and then step up from there or should I just go directly to 0.95.1..... I saw some references to 0.95.1 having some issues but it seems that was only with bitcoind 0.14 so if I'm going to stay at 0.13.0 for right now that issue wouldn't apply to me I assume?
Just upgrade directly to 0.95.1. When you do so, you will need to go to the Armory data folder and delete the folder named "databases" inside of it since 0.95.1 has a completely different and incompatible database format from 0.93.3. |
|
|
|
i didnt notice it before but there is a way to allow remote connection based on a ip range? like 192.168.1.*, because rotation like 192.168.1.0/24 or 192.168.1.0/255.255.255.0 don't work
The 192.168.1.0/24 and 192.168.1.0/255.255.255.0 notation should work. According to the command line option help: -rpcallowip=<ip>
Allow JSON-RPC connections from specified source. Valid for <ip> are a single IP (e.g. 1.2.3.4), a network/netmask (e.g. 1.2.3.4/255.255.255.0) or a network/CIDR (e.g. 1.2.3.4/24). This option can be specified multiple times
why is the xxx.xxx.x.* not allowed? i understand that =* is dangerous, but the rotation with 192.168.1.* is still about private address and should not do any harm in theory, what i'm missing? Using the * wildcard is not part of the standard CIDR notation. Core supports the standard CIDR notation and not other non-standard notation. Notation like 1xxx.xxx.xxx.* is not standard. There is no standard which defines what * means in an IP address. |
|
|
|
|
You are using Core 0.13.2, yes? Is it fully synced?
The db engine (which does the rescanning and rebuilding) did not finish rescanning and rebuilding. It only got to block #320757 before something caused it to exit, so any transactions made and confirmed after that block will not be known.
|
|
|
|
Just did it, with core physically open, and still nothing. I am stumped.  Post the armorylog.txt and dblog.txt files which can be found in the Armory data folder. |
|
|
|
Is this the same C Shrem that was find guilty and went to prison?
Yes. IIRC he was released a few months ago. Thanks, so how does all this work?
I can see the xd detail looking at the wallet peers. Does it need to be activated or is it automatic?
It depends on the software that you are running. Different software will support different services. Additionally if you have pruning enabled you will be disabling NODE_NETWORK for your node. If you run Bitcoin Core 0.13.1+, your node will be xd. Earlier versions should be x5 and even older ones will be x1. |
|
|
|
Thanks!
Just tried that. Armory starts up instantly and doesn't seem to be rebuilding anything. Balance still 0. I remember doing that option in the past and it took a while to rebuild and rescan.
If it matters I have "run bitcoin core in the background" unchecked.
Is Bitcoin Core also running? It cannot do anything without Bitcoin Core running. |
|
|
|
Thank you for the perfect reply. With datadir you mean the "Bitcoin" folder in %appData%?
Yes. That folder, is compatible with Linux wallet?
Yes. |
|
|
|
|
Show Posts
