 Show Posts
|
|
Pages: [1]
|
|
Thanks for the answers! And also thanks for suggesting the easy way but.. hey! The whole point of this is experimenting and learning something new; if it was just about transferring funds, i could just send an on-chain transaction (about the exchange fees: i have already withdrawn the amount, paid a reasonable one).
I've seen there are some services who offer to open a channel back to you as long as you open one to them; maybe is there any who can open a channel to a 3rd party instead? Also, which software is best suited for this sort of transactions at the moment? I've had a look into Electrum but it looks like they only support a simplified subset of the lightning network features.
|
|
|
|
|
Hey there!
I owe a friend a few bucks and, since we would like to experiment with Bitcoin, he agreed to have them sent over the Lightning Network. I went to an exchange and bought 0.003 BTC, I now would like to send 0.001 BTC to him.
After reading some articles, I have probably realized that there is no use in opening a direct channel between him and me, since channels are made for recurring transactions and we are unlikely to have any in the future.
So i figured out what i need instead to do is:
- open a channel to a "famous" well connected node and fund 0.001 BTC into it
- have such "famous" node open a channel to my friend and fund the same amount into it
- finally send the LN payment to my friend, routing through such node
As a result, we will both end up with a channel opened with that node, me having a 0.001 inbound capacity, and him having 0.001 spending capacity, that we will be able to use in the future to send/receive to/from anyone connected to that node.
Is this correct? If yes, how can I accomplish it in practice?
|
|
|
|
|
Oh, thanks.
I see it works under NFS. I am planning to use it meanwhile (if I can manage to set it up in a safe way).
|
|
|
|
So following your hints I've found these links: https://github.com/bitcoin/bitcoin/issues/4276https://github.com/smira/aptly/issues/317No, this is LevelDB reporting that an internal system call returned with an error status indicating that an invalid argument was passed.
I assume that the samba filesystem does not offer certain functionality that LevelDB requires of its databases, such a certain types of locking, syncing or mmaping.
Long story short, BitCoin uses LevelDB from Google, that seems to have some "undfined" issues with cifs. They could most probably be fixed/worked around, but that would require me to report the problem to the Bitcoin devs, then they to report it upstream, wait for Google to fix it, then update the LevelDB version in Bitcoin. I bet it could take years  I am now exploring different solutions. At least, the image file works. Thank you |
|
|
|
Thank you for the explanations. I have tried doing something very weird: I have created big image file inside the network share, then mounted it. Goods news: it works. Bad news: it is incredibly slow, as expected. So the network itself is definitely not a problem. Could be a permissions problem? here is the debug.log: 2016-04-30 22:11:04 Bitcoin version v0.12.1.0-g9779e1e (Mon, 11 Apr 2016 13:01:43 +0200)
2016-04-30 22:11:04 InitParameterInteraction: parameter interaction: -listen=0 -> setting -upnp=0
2016-04-30 22:11:04 InitParameterInteraction: parameter interaction: -listen=0 -> setting -discover=0
2016-04-30 22:11:04 InitParameterInteraction: parameter interaction: -listen=0 -> setting -listenonion=0
2016-04-30 22:11:04 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2016-04-30 22:11:04 GUI: Bus::open: Can not get ibus-daemon's address.
2016-04-30 22:11:04 GUI: "sni-qt/26696" WARN 00:11:04.636 void StatusNotifierItemFactory::connectToSnw() Invalid interface to SNW_SERVICE
2016-04-30 22:11:04 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
2016-04-30 22:11:04 Default data directory /home/bodom/.bitcoin
2016-04-30 22:11:04 Using data directory /home/bodom/.bitcoin
2016-04-30 22:11:04 Using config file /home/bodom/.bitcoin/bitcoin.conf
2016-04-30 22:11:04 Using at most 125 connections (1024 file descriptors available)
2016-04-30 22:11:04 Using 4 threads for script verification
2016-04-30 22:11:04 Using wallet wallet.dat
2016-04-30 22:11:04 init message: Verifying wallet...
2016-04-30 22:11:04 scheduler thread start
2016-04-30 22:11:04 CDBEnv::Open: LogDir=/home/bodom/.bitcoin/database ErrorFile=/home/bodom/.bitcoin/db.log
2016-04-30 22:11:04 Cache configuration:
2016-04-30 22:11:04 * Using 12.5MiB for block index database
2016-04-30 22:11:04 * Using 29.9MiB for chain state database
2016-04-30 22:11:04 * Using 57.6MiB for in-memory UTXO set
2016-04-30 22:11:04 init message: Loading block index...
2016-04-30 22:11:04 Opening LevelDB in /home/bodom/.bitcoin/blocks/index
2016-04-30 22:11:04 IO error: /home/bodom/.bitcoin/blocks/index: Invalid argument
2016-04-30 22:11:06 init message: Loading block index...
2016-04-30 22:11:06 Wiping LevelDB in /home/bodom/.bitcoin/blocks/index
2016-04-30 22:11:06 Opening LevelDB in /home/bodom/.bitcoin/blocks/index
2016-04-30 22:11:06 IO error: /home/bodom/.bitcoin/blocks/index: Invalid argument
2016-04-30 22:11:07 scheduler thread interrupt
2016-04-30 22:11:07 Shutdown: In progress...
2016-04-30 22:11:07 StopNode()
2016-04-30 22:11:07 Shutdown: done The folder giving an I/O error exists: $stat /home/bodom/.bitcoin/blocks/index
File: '/home/bodom/.bitcoin/blocks/index'
Size: 0 Blocks: 0 IO Block: 16384 directory
Device: 32h/50d Inode: 74186757 Links: 2
Access: (0700/drwx------) Uid: ( 1000/ bodom) Gid: ( 1000/ bodom)
Access: 2016-05-01 00:11:06.264941600 +0200
Modify: 2016-05-01 00:11:06.268941500 +0200
Change: 2016-05-01 00:11:06.268941500 +0200
Birth: - |
|
|
|
|
In theory, there should be no way for the Bitcoin software to distinguish between a local and a network drive. That's why I do not see why it should not work.
Is there a way to have a more precise error message saying what is wrong?
Is this the right place to ask support for that software?
|
|
|
|
Why aren't network drivers ok?  |
|
|
|
|
Hi there!
I have installed the Bitcoin client for Linux (bitcoin-qt).
I have started it, and it started synchronizing blocks. After a while, my disk got full.
I have then moved the ~/.bitcoin/blocks and ~/.bitcoin/chainstate to a different partition and created symlinks. The client started again and downloaded blocks for some hours, then also that partition got full.
I have a NAS mounted via cifs (smbfs) with huge disk space. If I move the blocks and chainstate folders there and symlink them, exactly in the same way i did with the other partition, I get an error opening blocks database. It asks me if I want to rebuild it. If I answer yes, it then says the same error again and exits.
Any ideas?
Thank you
|
|
|
|
|
