 Show Posts
|
|
Pages: [1]
|
You need a lot of things to prove that you are the owner of the land and the restaurant, but هin which country? so that we can compare it with the rest of the lands.
Another question, the price of bitcoin changes strongly, and I do not think that you will get buyers within 24 hours, so it is better to write the price in dollars and adjust it to the price of the bitcoin at the moment of selling.
You also need to verify tax laws and whether the country accepts Bitcoin as a payment broker.
I'm not interested in dollars and it's pair to bitcoin, if bitcoin price falls to 1k i will still ask for 20 bitcoin for this property. i can provide pictures and all the paperwork on demand. The restaurant has 2 employees is a really quite hill zone without struggling too much the restaurant brings an annual net worth of 30.000$, without taking in consideration the minimum7k liters of wine produced in the wineyard |
|
|
|
|
As said in the title i'm selling 6Ha(60000sqm) of wood 3Ha(30000sqm) of land which 1.3Ha are wine yard, full working restaurant of 120 people capacity, at the second floor has 2 apartments, in the court has 2 cottages and one big cellar, a tractor and all his equipment are include.
Picture to post later.
|
|
|
|
Unless you have some way of bundling a bitcoin.conf file with your installer... then it is something that needs to be manually created. Bitcoin Core doesn't create a bitcoin.conf when it is installed. I created my own "altcoin" (basically Bitcoin code with some minor edits) a while back when I was trying to help BlackHatCoiner when they were attempting to do the same... Now it seems that BlackHatCoiner has created a nice little tutorial with the basics covered: https://bitcointalk.org/index.php?topic=5309100.msg56085433#msg56085433As you can see, he mentions the fixed IP addresses in chainparams.cpp and the vSeeds/vFixedSeeds etc... So, modification of those in chainparams.cpp and replacing the values in chainparamsseed.cpp should allow you to create your own "fixed" seeds without requiring addnode entries in bitcoin.conf file. Note: that if you simply delete the lines and use vFixedSeeds.clear() as per his tutorial, you won't have any seeds and will need to use addnodeI did follow that guide, and also 4 different ones, it makes sense now i will give it a try, thank you very much |
|
|
|
AppArmor provides /etc/apparmor.d/local/ for rules to add to the main ones. (Although this can't be used to override an explicit deny like tcpdump's ban on using files in $HOME/bin.) We just need to add a rule for the *.gz, and while we're there, why not the *.bz2 version as well? /**.[pP][cC][aA][pP].[gG][zZ] rw,
/**.[pP][cC][aA][pP].[bB][zZ]2 rw, The trailing comma does not seem to be an issue for me. Note also that we don't need to specify the binary and braces, since the #include line in the system profile is already inside the braces. Ubuntu ships some files in the local directory already; we should be able to run sudo -e /etc/apparmor.d/local/usr.sbin.tcpdump and add the lines above to the existing file. Once the file is ready, we need to reload that profile to the kernel. Note that we use the system profile here, not the one we just edited: sudo apparmor_parser -r /etc/apparmor.d/usr.sbin.tcpdump . locate your core in usr/src/ use sudo commands and should be fine |
|
|
|
The instructions in build-windows.md seem to work OK... I didn't need to do any "scouring"  it was basically as simple as setup WSL, install Ubuntu 18.04 in WSL, copy/paste the commands from the readme to the terminal. Additionally, there are notes on how to build using Visual Studio here: https://github.com/bitcoin/bitcoin/blob/master/build_msvc/README.mdI just didn't do it that way because I don't have VS installed As you said, was pretty simple to build it, i just missed the part in which i had to choose the posix compiler on Mingw64, i achieved also to compile it throught VS so is not a big deal, i don't think asweel any "scouring" is needed, just follow the docs step by step and will be fine. Another thing: do you have any idea on how to preset the bitcoin.conf node before compiling the QT? both on windows and linux, cuz i have to set them manually, or is enough to add in chainparamsseed.cpp the DNS of the node in HEX and than add them also on vSeeds in the chain I'm using in chainparams.cpp |
|
|
|
When you say "fork"... did you actually make any edits at all to the source code? or did you simply clone the github repo and then attempt to compile it?  i actually tried to rebrand the bitcoin core node, i re-mined the genesis block for main/test/regtest block chain, i achieved to compile everything on linux, creating a new blockchain, i would like to build my own altcoin, that's why i started with the basics reading the documentation, but i got stuck there and you helped me a lot, now i'm running 2 full nodes, i just need to learn how to configure the bitcoin.conf before the compile, and to create a modded cpuminer that allows to mine it based on a yimpp pool |
|
|
|
|
Huh, I did not actually user the posix compiler but the default win 32 one, I'll try it now, thank you very much
|
|
|
|
Hello CryptoWorld, i tried to fork the bitcoin 0.21 and to compile it throught WSL and Ubuntu 18.04TLS. i followed the full doc/build.windows but when i run PATH=$(echo "$PATH" | sed -e 's/:\/mnt.*//g') # strip out problematic Windows %PATH% imported var
sudo bash -c "echo 0 > /proc/sys/fs/binfmt_misc/status" # Disable WSL support for Win32 applications.
cd depends
make HOST=x86_64-w64-mingw32
cd ..
./autogen.sh # not required when building from tarball
CONFIG_SITE=$PWD/depends/x86_64-w64-mingw32/share/config.site ./configure --prefix=$PWD/depends/x86_64-w64-mingw32/
make
sudo bash -c "echo 1 > /proc/sys/fs/binfmt_misc/status"
it just trow me an error compiling the bitcoind on line 21: In file included from ./logging.h:11:0,
from ./util/system.h:21,
from bitcoind.cpp:21:
./threadsafety.h:58:1: error: expected class-name before ‘{’ token
{
and as you know in the threadsecurity.h on line 57 the class is well definited. Is in here someone able to give me a good advice? |
|
|
|
|
