Hi all, looking for a couple wallet recommendations here:
1) Looking for a daily use cross-platform wallet that I can sync across multiple devices - ideally Windows, Mac, and Android
Electrum is the only one I know running on all these platforms. Any combination of HD wallets with compatible seeds would do though. 2) Also looking for a long-term storage wallet for BTC I want to invest in (not looking for a cold-wallet, not yet at least)
Anyone with recommendations, thanks in advance!
Any, just make sure its a wallet, not a service where you have to trust someone else.
|
|
|
Well you told us how to sign a message .. But please tell me why it is needed to sign a message. What is it used for and why to sign a message?? As Coinlearn wrote, to prove you own a bitcoin address. Why prove that you may ask. You can use a signed message as proof of funds. Signing a message with an address that holds a certain amount of funds, shows that you held or hold that amount. You can use a signed message to prove to someone that you are still the same person as last year. Accounts here are traded often, bitcoin addresses almost never. Its possible though, so its not 100%. You can use a signed message to agree to a private agreement. Lets say you staked your address in the thread here[1] and want to make a deal with someone you both prefer to stay private for some reason. If you both sign the agreement with your staked addresses you can disclose the agreement if needed. This is often a requirement when bitcointalk accounts are sold. It gives security to the buyer, that the seller will not try to reclaim the account via a signed message to the admins. You can use a signed message to prove to the admins that you are the rightful owner of a hacked account. Its usually the only way to get a stolen account back. [1] https://bitcointalk.org/index.php?topic=996318.0
|
|
|
Alright. Thanks for your help. I have re-done the dumpprivkey function in Bitcoin core with another address and obtained a new private key. The new private key was inputed into the sweep function of Electrum. I then broadcasted the transaction. I now have a unconfirmed transaction in my Electrum history menu. Thanks for your help buddy.
You are welcome, make sure you sweep all keys.
|
|
|
OK my bad. I entered the wrong passphrase. I have obtained the private key. I tried to entire the private key into the sweep function of Electrum. I received a message stating that "No input found (Note inputs need to be confirmed)" What does this statement mean?
It means there are no coins on that address. Maybe they are on a change address now.
|
|
|
Hi, I am trying to transfer my bitcoins from Bitcoin Core on one computer and onto Electrum onto another computer. I am doing this because it is taking too long to download the entire all the blocks on bitcoin core. I tried to do the following walkthrough: https://en.bitcoin.it/wiki/Transferring_coins_from_Bitcoin-Qt_to_ElectrumOnce i did the dumpprivkey no other key popped up. I am wondering if this is normal? There is on private key per address. If you want to export more than one key, try dumpwallet[1] (you might have to update first). Your version detects that there are new rules in the network it does not know about. If you want to switch clients, you can ignore this. [1] https://bitcoin.org/en/developer-reference#dumpwallet
|
|
|
-snip- I will edit my posts connecting ferjhie with alts of Candystripes or will leave a note at bottom.
Here is some information pertaining to this. I have had control of feryjhie since September 20th when released to me for collateral in a loan: I need a signed message from 1JPxhCP6QDpT896Hxpj5keg33sAR6FFcmn Your password was changed on the 12th of this month, after 6 months of inactivity. Just have to be safe before I can fund this. Let me know.
here the signed message -----BEGIN BITCOIN SIGNED MESSAGE----- i'm feryjhie, Today September 20, 2016 i want to take a loan from knightkon with details below Loan Amount: 0.095 Interest Charged: 0.02 Payback: 0.115 Payback Date: October 8, 2016 Collateral: This Bitcointalk Account BTC address: 34WWNVg1fMfr35tM9R2RF6QrfY6Lgyw89T -----BEGIN SIGNATURE----- 1JPxhCP6QDpT896Hxpj5keg33sAR6FFcmn G2dpTn04bCgBM8b2lImCTwSib/L8B8/8D+HKT6j0S61lTLg78lY3XVkvD6Tz7nd3OtNdak+++OOiZGePKgF5/tk= -----END BITCOIN SIGNED MESSAGE----- hello here the account details username: feryjhie password: so all further info just sent to my email : feryjhie@gmail.comDo you think its a good practice to get negative ratings removed by defaulting on another loan? The user had several bad ratings when you accepted the deal. Anyway, Ill change the rating to neutral because I understand that you have to sell it in order to make up for the lost coins. Source of address (2014) for the signed message above: https://bitcointa.lk/threads/no-collateral-needed-up-to-1-month-loans-fast.345078/page-2https://bitcointa.lk/threads/luckyb-it-main-thread-0-2-btc-bonus-for-100-000th-bet-soon.182448/page-41
|
|
|
It's a non-standard transaction. Have a deep look to the transaction inputs. Don't you see there any scripts already discussed here? You are an alt of the OP, yes? edit: I am not sure why you ask these types of questions -- you already know the answer Sometimes these questions are helpful for others - willing and able - to find the answer on their own. To say it with a Goethe quote they recently posted themselves (IIRC). ...ein Teil von jener Kraft, die stets das Böse will und stets das Gute schafft.
You could say its a way of answering questions that is no longer common.
|
|
|
-snip- The spam attacks cause everyone to pay more to get their transaction confirmed. If the max block size were increased then the cost of these spam attacks would grow exponentially, and the effectiveness of these transactions to decline.
A mere inconvenience, same as having to wait for a confirmation in order to make sure you can trust the input. Both have a cost, one in time, the other in coins. -snip- No, its not fixed. We just ignore all transactions. This causes issues for users using old software. You can say the same thing about every soft fork. However users of non-full-node wallets should receive notification that their transactions have been rejected, which should hopefully get them to upgrade. They get messages alright, usually the message gives them no indication what to do though. You can blame that on bad error messages, its still a problem. Full node users tend to be more active in upgrading, however they can view their transactions (or that their transactions have been rejected) on one of many block explorers, which might get them to upgrade in addition to the warning message to upgrade.
38% are currently running the latest version -> https://bitnodes.21.co/dashboard/?days=90Old data are not shown (or only as other) so I cant say how long it exactly took until the network had upgraded to the mellability quick fix, but thats all it is. Im not inclined to believe that node operators are not more active in upgrading, unless you can show me data to support that statement. -snip- I am not sure what you are saying here? I am trying to describe the small number of businesses that are affected by malleability under current node rules.
SegWit is not needed, its not necessary, Bitcoin would still exist and work without it. SegWit however properly fixes a long term problem that keeps coming back and is currently crudely fixed. It also offeres many opportunities for a larger number of different transaction types. The increase in transactions per block doesnt hurt either.
|
|
|
In pretty much all cases, this was nothing more than a nuisance to end users. I have not read any reports of any entities losing money as a result of that attack (some may have lost potential revenue as a result of not being able to accept 0 confirmation transactions, but I would not consider that in the scope of 'losing money as a result of that attack') Same as the "spam attacks", yet somehow a lot of people think we need to do something about that in order to advance bitcoin. Subsequent to that 'attack' the majority of nodes have been "programmed" to not relay high s-value signature transactions, so malleability has more or less been fixed for the end-user.
No, its not fixed. We just ignore all transactions. This causes issues for users using old software. The only way that I am aware that a high s-value signature transaction to get confirmed is for a miner to accept such transaction directly and the only type of business that remains vulnerable to malleability are gambling establishments that allow for on-chain gambling (businesses that tentatively accept 0-confirmation transactions can ignore transactions in which there is an unconfirmed input to the funding transaction in order to prevent fraud).
Its working, yes. Is that the metric here?
|
|
|
Yes, full script: #!/bin/sh
############################################################################### # # install-full-node.sh # # This is an install script for Bitcoin full node based on Bitcoin Core. # # This script attempts to make your node automatically reachable by other nodes # in the network. This is done by using uPnP to open port 8333 on your router # to accept incoming connections to port 8333 and route the connections to your # node running inside your local network. # # For security reason, wallet functionality is not enabled by default. # # Supported OS: Linux, Mac OS X, BSD # Supported platforms: x86, x86_64, ARM # # Usage: # Open your terminal and type: # # curl https://bitnodes.21.co/install-full-node.sh | sh # # Bitcoin Core will built from source and installed into $HOME/bitcoin-core # directory. Layout of this directory after the installation is shown below: # # Source files: # $HOME/bitcoin-core/bitcoin/ # # Binaries: # $HOME/bitcoin-core/bin/ # # Configuration file: # $HOME/bitcoin-core/.bitcoin/bitcoin.conf # # Blockchain data files: # $HOME/bitcoin-core/.bitcoin/blocks # $HOME/bitcoin-core/.bitcoin/chainstate # ###############################################################################
REPO_URL="https://github.com/bitcoin/bitcoin.git"
# See https://github.com/bitcoin/bitcoin/tags for latest version. VERSION=v0.13.1
TARGET_DIR=$HOME/bitcoin-core PORT=8333
UNINSTALL=0
BLUE='\033[94m' GREEN='\033[32;1m' YELLOW='\033[33;1m' RED='\033[91;1m' RESET='\033[0m'
SYSTEM=$(uname -s) MAKE="make" if [ "$SYSTEM" = "FreeBSD" ]; then MAKE="gmake" fi
usage() { cat <<EOF
This is an install script for Bitcoin full node based on Bitcoin Core.
Usage: $0 [-h] [-v <version>] [-t <target_directory>] [-p <port>] [-u]
-h Print usage.
-v <version> Version of Bitcoin Core to install. Default: $VERSION
-t <target_directory> Target directory for source files and binaries. Default: $HOME/bitcoin-core
-p <port> Bitcoin Core listening port. Default: $PORT
-u Uninstall Bitcoin Core.
EOF }
print_info() { printf "$BLUE$1$RESET\n" }
print_success() { printf "$GREEN$1$RESET\n" sleep 1 }
print_warning() { printf "$YELLOW$1$RESET\n" }
print_error() { printf "$RED$1$RESET\n" sleep 1 }
print_start() { print_info "Start date: $(date)" }
print_end() { print_info "\nEnd date: $(date)" }
print_readme() { cat <<EOF
# README
To stop Bitcoin Core:
cd $TARGET_DIR/bin && ./stop.sh
To start Bitcoin Core again:
cd $TARGET_DIR/bin && ./start.sh
To use bitcoin-cli program:
cd $TARGET_DIR/bin && ./bitcoin-cli -conf=$TARGET_DIR/.bitcoin/bitcoin.conf getinfo
To view Bitcoin Core log file:
tail -f $TARGET_DIR/.bitcoin/debug.log
To uninstall Bitcoin Core:
./install-full-node.sh -u
EOF }
program_exists() { if ! type "$1" > /dev/null 2>&1; then return 1 else return 0 fi }
create_target_dir() { print_info "\nCreating target directory: $TARGET_DIR" mkdir -p $TARGET_DIR }
install_miniupnpc() { print_info "Installing miniupnpc from source.." rm -rf miniupnpc-2.0 miniupnpc-2.0.tar.gz && wget -q http://miniupnp.free.fr/files/download.php?file=miniupnpc-2.0.tar.gz -O miniupnpc-2.0.tar.gz && \ tar xzf miniupnpc-2.0.tar.gz && \ cd miniupnpc-2.0 && \ sudo $MAKE install > build.out 2>&1 && \ cd .. && \ rm -rf miniupnpc-2.0 miniupnpc-2.0.tar.gz }
install_debian_dependencies() { sudo apt-get update sudo apt-get install -y \ automake \ autotools-dev \ build-essential \ curl \ git \ libboost-all-dev \ libevent-dev \ libminiupnpc-dev \ libssl-dev \ libtool \ pkg-config }
install_fedora_dependencies() { sudo dnf install -y \ automake \ boost-devel \ curl \ gcc-c++ \ git \ libevent-devel \ libtool \ miniupnpc-devel \ openssl-devel }
install_centos_dependencies() { sudo yum install -y \ automake \ boost-devel \ curl \ gcc-c++ \ git \ libevent-devel \ libtool \ openssl-devel install_miniupnpc echo '/usr/lib' | sudo tee /etc/ld.so.conf.d/miniupnpc-x86.conf > /dev/null && sudo ldconfig }
install_archlinux_dependencies() { sudo pacman -S --noconfirm \ automake \ boost \ curl \ git \ libevent \ libtool \ miniupnpc \ openssl }
install_alpine_dependencies() { sudo apk update sudo apk add \ autoconf \ automake \ boost-dev \ build-base \ curl \ git \ libevent-dev \ libtool \ openssl-dev install_miniupnpc }
install_mac_dependencies() { if ! program_exists "gcc"; then print_info "When the popup appears, click 'Install' to install the XCode Command Line Tools." xcode-select --install fi
if ! program_exists "brew"; then /usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)" fi
brew install \ --c++11 \ automake \ boost \ libevent \ libtool \ miniupnpc \ openssl \ pkg-config }
install_freebsd_dependencies() { sudo pkg install -y \ autoconf \ automake \ boost-libs \ curl \ git \ gmake \ libevent2 \ libtool \ openssl \ pkgconf \ wget install_miniupnpc }
install_dependencies() { if program_exists "sudo"; then print_info "\nInstalling required system packages.." else print_error "\nsudo program is required to install system packages. Please install sudo as root and rerun this script as normal user." exit 1 fi
case "$SYSTEM" in Linux) if program_exists "apt-get"; then install_debian_dependencies elif program_exists "dnf"; then install_fedora_dependencies elif program_exists "yum"; then install_centos_dependencies elif program_exists "pacman"; then install_archlinux_dependencies elif program_exists "apk"; then install_alpine_dependencies else print_error "\nSorry, your system is not supported by this installer." exit 1 fi ;; Darwin) install_mac_dependencies ;; FreeBSD) install_freebsd_dependencies ;; *) print_error "\nSorry, your system is not supported by this installer." exit 1 ;; esac }
build_bitcoin_core() { cd $TARGET_DIR
if [ ! -d "$TARGET_DIR/bitcoin" ]; then print_info "\nDownloading Bitcoin Core source files.." git clone --quiet $REPO_URL fi
# Tune gcc to use less memory on single board computers. cxxflags="" if [ "$SYSTEM" = "Linux" ]; then ram_kb=$(grep MemTotal /proc/meminfo | awk '{print $2}') if [ $ram_kb -lt 1500000 ]; then cxxflags="--param ggc-min-expand=1 --param ggc-min-heapsize=32768" fi fi
print_info "\nBuilding Bitcoin Core $VERSION" print_info "Build output: $TARGET_DIR/bitcoin/build.out" print_info "This can take up to an hour or more.." rm -f build.out cd bitcoin && git fetch > build.out 2>&1 && git checkout $VERSION 1>> build.out 2>&1 && git clean -f -d -x 1>> build.out 2>&1 && ./autogen.sh 1>> build.out 2>&1 && ./configure \ CXXFLAGS="$cxxflags" \ --without-gui \ --with-miniupnpc \ --disable-wallet \ --disable-tests \ --enable-upnp-default \ 1>> build.out 2>&1 && $MAKE 1>> build.out 2>&1
if [ ! -f "$TARGET_DIR/bitcoin/src/bitcoind" ]; then print_error "Build failed. See $TARGET_DIR/bitcoin/build.out" exit 1 fi }
install_bitcoin_core() { cd $TARGET_DIR
print_info "\nInstalling Bitcoin Core $VERSION"
if [ ! -d "$TARGET_DIR/bin" ]; then mkdir -p $TARGET_DIR/bin fi
if [ ! -d "$TARGET_DIR/.bitcoin" ]; then mkdir -p $TARGET_DIR/.bitcoin fi
if [ "$SYSTEM" = "Darwin" ]; then if [ ! -e "$HOME/Library/Application Support/Bitcoin" ]; then ln -s $TARGET_DIR/.bitcoin "$HOME/Library/Application Support/Bitcoin" fi else if [ ! -e "$HOME/.bitcoin" ]; then ln -s $TARGET_DIR/.bitcoin $HOME/.bitcoin fi fi
cp "$TARGET_DIR/bitcoin/src/bitcoind" "$TARGET_DIR/bin/" && cp "$TARGET_DIR/bitcoin/src/bitcoin-cli" "$TARGET_DIR/bin/" && print_success "Bitcoin Core $VERSION installed successfully!"
cat > $TARGET_DIR/.bitcoin/bitcoin.conf <<EOF listen=1 bind=0.0.0.0 port=$PORT maxconnections=64
dbcache=64 par=2 checkblocks=24 checklevel=0
disablewallet=1
rpcbind=127.0.0.1 rpcport=8332 rpcallowip=127.0.0.1 rpcuser=rpcuser rpcpassword=$(LC_CTYPE=C tr -dc '[:alnum:]' < /dev/urandom | dd bs=4 count=16 2> /dev/null) EOF chmod go-rw $TARGET_DIR/.bitcoin/bitcoin.conf
cat > $TARGET_DIR/bin/start.sh <<EOF #!/bin/sh if [ -f $TARGET_DIR/bin/bitcoind ]; then $TARGET_DIR/bin/bitcoind -conf=$TARGET_DIR/.bitcoin/bitcoin.conf -datadir=$TARGET_DIR/.bitcoin -daemon fi EOF chmod ugo+x $TARGET_DIR/bin/start.sh
cat > $TARGET_DIR/bin/stop.sh <<EOF #!/bin/sh if [ -f $TARGET_DIR/.bitcoin/bitcoind.pid ]; then kill \$(cat $TARGET_DIR/.bitcoin/bitcoind.pid) fi EOF chmod ugo+x $TARGET_DIR/bin/stop.sh }
start_bitcoin_core() { if [ ! -f $TARGET_DIR/.bitcoin/bitcoind.pid ]; then print_info "\nStarting Bitcoin Core.." cd $TARGET_DIR/bin && ./start.sh
timer=0 until [ -f $TARGET_DIR/.bitcoin/bitcoind.pid ] || [ $timer -eq 5 ]; do timer=$((timer + 1)) sleep $timer done
if [ -f $TARGET_DIR/.bitcoin/bitcoind.pid ]; then print_success "Bitcoin Core is running!" else print_error "Failed to start Bitcoin Core." fi fi }
stop_bitcoin_core() { if [ -f $TARGET_DIR/.bitcoin/bitcoind.pid ]; then print_info "\nStopping Bitcoin Core.." cd $TARGET_DIR/bin && ./stop.sh
timer=0 until [ ! -f $TARGET_DIR/.bitcoin/bitcoind.pid ] || [ $timer -eq 120 ]; do timer=$((timer + 1)) sleep $timer done
if [ ! -f $TARGET_DIR/.bitcoin/bitcoind.pid ]; then print_success "Bitcoin Core stopped." fi fi }
check_bitcoin_core() { if [ -f $TARGET_DIR/.bitcoin/bitcoind.pid ]; then if [ -f $TARGET_DIR/bin/bitcoin-cli ]; then print_info "\nChecking Bitcoin Core.." sleep 5 $TARGET_DIR/bin/bitcoin-cli -conf=$TARGET_DIR/.bitcoin/bitcoin.conf getinfo fi
reachable=$(curl -I https://bitnodes.21.co/api/v1/nodes/me-$PORT/ 2> /dev/null | head -n 1 | cut -d ' ' -f2) if [ $reachable -eq 200 ]; then print_success "Bitcoin Core is accepting incoming connections at port $PORT!" else print_warning "Bitcoin Core is not accepting incoming connections at port $PORT. You may need to configure port forwarding on your router." fi fi }
uninstall_bitcoin_core() { stop_bitcoin_core
if [ -d "$TARGET_DIR" ]; then print_info "\nUninstalling Bitcoin Core.." rm -rf $TARGET_DIR
# Remove stale symlink. if [ "$SYSTEM" = "Darwin" ]; then if [ -L "$HOME/Library/Application Support/Bitcoin" ] && [ ! -d "$HOME/Library/Application Support/Bitcoin" ]; then rm "$HOME/Library/Application Support/Bitcoin" fi else if [ -L $HOME/.bitcoin ] && [ ! -d $HOME/.bitcoin ]; then rm $HOME/.bitcoin fi fi
if [ ! -d "$TARGET_DIR" ]; then print_success "Bitcoin Core uninstalled successfully!" else print_error "Uninstallation failed. Is Bitcoin Core still running?" exit 1 fi else print_error "Bitcoin Core not installed." fi }
while getopts ":v:t:p:u" opt do case "$opt" in v) VERSION=${OPTARG} ;; t) TARGET_DIR=${OPTARG} ;; p) PORT=${OPTARG} ;; u) UNINSTALL=1 ;; h) usage exit 0 ;; ?) usage >& 2 exit 1 ;; esac done
WELCOME_TEXT=$(cat <<EOF
Welcome!
You are about to install a Bitcoin full node based on Bitcoin Core $VERSION.
All files will be installed under $TARGET_DIR directory.
Your node will be configured to accept incoming connections from other nodes in the Bitcoin network by using uPnP feature on your router.
For security reason, wallet functionality is not enabled by default.
After the installation, it may take several hours for your node to download a full copy of the blockchain.
If you wish to uninstall Bitcoin Core later, you can download this script and run "sh install-full-node.sh -u".
EOF )
print_start
if [ $UNINSTALL -eq 1 ]; then echo read -p "WARNING: This will stop Bitcoin Core and uninstall it from your system. Uninstall? (y/n) " answer if [ "$answer" = "y" ]; then uninstall_bitcoin_core fi else echo "$WELCOME_TEXT" if [ -t 0 ]; then # Prompt for confirmation when invoked in tty. echo read -p "Install? (y/n) " answer else # Continue installation when invoked via pipe, e.g. curl .. | sh answer="y" echo echo "Starting installation in 10 seconds.." sleep 10 fi if [ "$answer" = "y" ]; then install_dependencies create_target_dir stop_bitcoin_core build_bitcoin_core install_bitcoin_core start_bitcoin_core check_bitcoin_core print_readme > $TARGET_DIR/README.md cat $TARGET_DIR/README.md print_success "If this your first install, Bitcoin Core may take several hours to download a full copy of the blockchain." print_success "\nInstallation completed!" fi fi
print_end
|
|
|
can confim my account was hacked.. all resolved now
i don't trade here anyways:)
to prove that you already original owner you must sign with old staked address, only your word not enough. how do i do that?? How did you get the account back? Can you sign a message with an old address? i mean i just trade buy and mine, all my post prove this i am not involv in BS.. my accounts get hacked in bitcointalk and i must prove myself?, when are they gonna implement good security here?
Would you rather we did nothing and let the hacker get away with it? -snip- very simple, just sign message with following address:
1GGzBQXnouv2LvSvBLcT9vR8CZ3X1sQi6y
just strange, that if you trade here why the only in one place posted address?!
Read the posts following the one where the address was posted, it looks like the hacker tried to get the loan.
|
|
|
-snip- We could easily go to 8MB today without causing technical damage.
What would qualify as technical damage? How would you do a hardfork today (or tomorrow if thats easier) if you think 95% on a softfork is out of the question?
|
|
|
I am not the only one, lots of people have already given up. Very fucking stupid mismanagement is the result. At least TCP-IP and Linux had some means to make sensible adjustments in the early days. Bitcoin has no means to fix things that need a fixin'. "Consensus" is just a very stupid concept. 95% consensus will never be reached for any issue. Bitcoin is fucked. Doesn't scale. Everyone already left.
k, bye. You sound like you made up your mind, yet you create a topic to discuss this. So, lets discuss. For one TCP-IP is heavily(!) flawed. It has fundamental design flaws because when it was created people had a very different kind of internet in mind. Same for Linux, it has its place, but you might have noticed that its not the only perfect operation system. Neither on servers, offices or home computers. It has its strength and its weaknesses same as most things. One of the strong points of bitcoin is the difficulty to change what bitcoin actually is. Its not a bug, its a feature. Blocks are full, yes, but you cant just crank it up to 11 and still have the same distributed network of nodes to support it. Satoshi once said - to someone suggesting to support Wikileaks when they were dropped by PayPal etc. - bitcoin needs to grow slowly or it will get destroyed. I still think this is true in a sense, that it has to evolve slowly exploring its options before a decision is made.
|
|
|
Hi, Having read what is written here and on other similar threads, I assume that the issue I am facing is also a false positive. I am posting it in case there is a chance it can be something else ... So, when dowloading the blockchain for Bitcoin core 0.13.1, on Windows 10 64 bits, Avast alerts me that a virus has been found and that it will be deleting it. Here is what it logs/deletes: C:\Users\<me>\AppData\Roaming\Bitcoin\blocks\blk00129.dat [L] Frodo (4k, 200 years) (0) C:\Users\<me>\AppData\Roaming\Bitcoin\blocks\blk00129.dat [L] Leprosy (0) C:\Users\<me>\AppData\Roaming\Bitcoin\blocks\blk00129.dat [L] Syslock (0) C:\Users\<me>\AppData\Roaming\Bitcoin\blocks\blk00129.dat [L] Murphy (0) C:\Users\<me>\AppData\Roaming\Bitcoin\blocks\blk00129.dat [L] AntiCad-4096 (0) C:\Users\<me>\AppData\Roaming\Bitcoin\blocks\blk00129.dat [L] BV:Akuma-A (0) I'll be configuring Avast to ignore the blocks directory in order to move on. If anyone have an(other) advice, please don't be shy . Thank you. Write them a mail, at the very least they should ask and not just delete the files.
|
|
|
No, thats bullshit. I could understand the reasoning if the quality of your posts would drop due to the high amount. I havent checked your history, but from what I read from you that should not be the case. If you have the time on your hand you should be allowed to post as much as you want (you are according to the forums rules anyway). If the campaign (manager) does not wants to pay as much, they can put a limit on what they are willing to pay.
|
|
|
Komm grad nich drauf, was meint nochmal Related etc?
Ich bin mir nicht 100% sicher, aber es kann sein das Bitcoin Verbindungen über andere Ports öffnet. Wie z.B. FTP und torrent(?) auch, dafür gibts den ctstate related[1]. Ansonten würde ich auch immer "established" durchlassen bzw. weiterleiten. Also z.B. iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
als erste Regel und erst danach die anderen. [1] https://linux.die.net/man/8/iptables unter conntrack
|
|
|
Who locked the "Let's talk about how hot Asian girls are" thread? That thread used to be my first point of call on the forum I know this is a bitcoin forum and it may have been a little out of place even in off-topic but it was needed, with all the drama that goes on here sometimes it was good to just take 5 and check out some pussy, Bring back the Asian girls thread campaign anyone? https://www.google.de/search?q=hot+asian+girlsnot everything must come from a single page, dont you think?
|
|
|
Wie gesagt läuft auch der andere P2P-Client (Filesharing) problemlos übers VPN-Netz, so groß is der Unterschied zu Bitcoin da ja nich (praktisch nur n anderer Port). Auch Tor, Thunderbird, Firefox, etc nehmen alle den Weg über den VPN.
Ne Bitcoin-spezifische Einstellung hab ich in der VPN-Config ja garnicht eingestellt, das sollte ja eigentlich die Port-Weiterleitung (iptables auf dem Server) erledigen. Im Fall des Filesharing-Clients tut sie das ja auch, nur bei Bitcoin eben nicht.
Related etc. werden weitergeleitet nehm ich an? Egal, was solls, jetzt läuft die Sache halt erst über den Tor-Proxy und von da dann zum VPN. Das klappt soweit, hab momentan ~30 Connections, ganz ok'en up-/download, alles gut, muss halt nur immer dran denken, erst Tor anzuwerfen, bevor ich Bitcoin starte, aber in der Regel laufen beide 24/7.
Hab auch gleich mal n Bitcoin-HiddenService gestartet, wenn Tor eh schon laufen muss, weiß aber nich, ob das auch funktioniert. Also falls zufällig jemand seinen Bitcoin-Client über Tor laufen lässt, ich wär dankbar für nen Test: d6wubsdtr46dd5ki.onion
|
|
|
Ist ja Waaahnsig was los hier. Fällt Januar wieder aus wegen Congress?
|
|
|
|