Bitcoin Forum
May 06, 2024, 08:47:11 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Economy / Micro Earnings / Re: Bitcoin, Bitcoin Cash, Groestlcoin testnet faucet (coinfaucet.eu) on: May 28, 2023, 11:56:06 AM
Thank for the faucet.

Unfortunately it doesn't accept bitcoin script addresses which are 66 characters long. Like this one: bc1qlfg8dx3k06dwugkg9l73jfjh7qyr8x40catjwlaraav3vy7r3hjqn0908l

Could you pelase update it to accept longer addresses?
2  Alternate cryptocurrencies / Mining (Altcoins) / Re: Installing NOMP. on: October 23, 2018, 10:36:22 PM
I am running cpuminer (please see above the configuration files):

Code:
./minerd --url=stratum+tcp://127.0.0.1:17117  --userpass=3KFHKvFjjfcNYsWRJz8Bt8TtWSrLsC7Neh:yyy  -a sha256d -D -P

And I get this error:

Code:
[2018-10-24 00:34:35] > {"id": 1, "method": "mining.subscribe", "params": ["cpuminer/2.5.0"]}
* Failed to get recent socket
[2018-10-24 00:34:35] stratum_recv_line failed
[2018-10-24 00:34:35] ...retry after 30 seconds

No idea if the port is 17117, or 3333 or 3008.

Sometimes I get this error in the terminal running "node init.js":

Code:
/home/vader/.bitcoin/nomp/libs/poolWorker.js:278
                            pools[currentPool].getStratumServer().handleNewClient(socket);
                                                                 ^

TypeError: Cannot read property 'handleNewClient' of undefined

Please help me.

3  Alternate cryptocurrencies / Mining (Altcoins) / Re: Installing NOMP. on: October 23, 2018, 09:33:54 PM
Hi.

Thanks for answering.
The bitcoin network is private. Mining souldn't be a problem at all.

The thing is that I installed a mining server but I haven't seen an explanation of how to use it.
It seems that most documentation assumes some kind of magic learning by readers.

How do i mine?
4  Alternate cryptocurrencies / Mining (Altcoins) / Re: Installing NOMP. on: October 23, 2018, 07:31:13 PM
Update.

I found this thread: https://stackoverflow.com/questions/9164915/node-js-eacces-error-when-listening-on-most-ports

The solution is to allow, somehow, port 80 for non-root users:

Code:
sudo apt-get install libcap2-bin
sudo setcap cap_net_bind_service=+ep `readlink -f \`which node\``

But now I get this:

Code:
2018-10-23 21:29:43 [Pool]	[bitcoin] (Thread 1) Downloaded NaN% of blockchain from 2 peers
2018-10-23 21:29:48 [Pool] [bitcoin] (Thread 1) Downloaded NaN% of blockchain from 2 peers
2018-10-23 21:29:53 [Pool] [bitcoin] (Thread 1) Downloaded NaN% of blockchain from 2 peers
2018-10-23 21:29:58 [Pool] [bitcoin] (Thread 1) Downloaded NaN% of blockchain from 2 peers
2018-10-23 21:30:03 [Payments] [bitcoin] Finished interval - time spent: 3ms total, 1ms redis, 2ms daemon RPC
2018-10-23 21:30:03 [Pool] [bitcoin] (Thread 1) Downloaded NaN% of blockchain from 2 peers
2018-10-23 21:30:08 [Pool] [bitcoin] (Thread 1) Downloaded NaN% of blockchain from 2 peers

I have two bitcoins nodes connected among themselves (a private mainnet) and I want to start mining.

How do I know the pool is mining?

Thanks.
5  Alternate cryptocurrencies / Mining (Altcoins) / Re: Installing NOMP. on: October 23, 2018, 07:24:26 PM
Thanks.

this is config.json

Code:
{
    "logLevel": "debug",
    "logColors": true,

    "cliPort": 17117,

    "clustering": {
        "enabled": true,
        "forks": "auto"
    },

    "defaultPoolConfigs": {
        "blockRefreshInterval": 1000,
        "jobRebroadcastTimeout": 55,
        "connectionTimeout": 600,
        "emitInvalidBlockHashes": false,
        "validateWorkerUsername": true,
        "tcpProxyProtocol": false,
        "banning": {
            "enabled": true,
            "time": 600,
            "invalidPercent": 50,
            "checkThreshold": 500,
            "purgeInterval": 300
        },
        "redis": {
            "host": "127.0.0.1",
            "port": 6379
        }
    },

    "website": {
        "enabled": true,
        "host": "0.0.0.0",
        "port": 80,
        "stratumHost": "cryppit.com",
        "stats": {
            "updateInterval": 60,
            "historicalRetention": 43200,
            "hashrateWindow": 300
        },
        "adminCenter": {
            "enabled": true,
            "password": "password"
        }
    },

    "redis": {
        "host": "127.0.0.1",
        "port": 6379
    },

    "switching": {
        "switch1": {
            "enabled": false,
            "algorithm": "sha256",
            "ports": {
                "3333": {
                    "diff": 10,
                    "varDiff": {
                        "minDiff": 16,
                        "maxDiff": 512,
                        "targetTime": 15,
                        "retargetTime": 90,
                        "variancePercent": 30
                    }
                }
            }
        },
        "switch2": {
            "enabled": false,
            "algorithm": "scrypt",
            "ports": {
                "4444": {
                    "diff": 10,
                    "varDiff": {
                        "minDiff": 16,
                        "maxDiff": 512,
                        "targetTime": 15,
                        "retargetTime": 90,
                        "variancePercent": 30
                    }
                }
            }
        },
        "switch3": {
            "enabled": false,
            "algorithm": "x11",
            "ports": {
                "5555": {
                    "diff": 0.001,
                    "varDiff": {
                        "minDiff": 0.001,
                        "maxDiff": 1,
                        "targetTime": 15,
                        "retargetTime": 60,
                        "variancePercent": 30
                    }
                }
            }
        }
    },

    "profitSwitch": {
        "enabled": false,
        "updateInterval": 600,
        "depth": 0.90,
        "usePoloniex": true,
        "useCryptsy": true,
        "useMintpal": true,
        "useBittrex": true
    }
}

This is pool_settings/bitcoin.json

Code:
{
    "enabled": true,
    "coin": "bitcoin.json",

    "address": "3KFHKvFjjfcNYsWRJz8Bt8TtWSrLsC7Neh",

    "paymentProcessing": {
        "enabled": true,
        "paymentInterval": 20,
        "minimumPayment": 5,
        "daemon": {
            "host": "127.0.0.1",
            "port": 8332,
            "user": "xxx",
            "password": "yyy"
        }
    },

    "ports": {
        "3008": {
            "diff": 8
        },
        "3032": {
            "diff": 32,
            "varDiff": {
                "minDiff": 8,
                "maxDiff": 4096,
                "targetTime": 15,
                "retargetTime": 90,
                "variancePercent": 30
            }
        },
        "3256": {
            "diff": 256
        }
    },

    "daemons": [
        {
            "host": "127.0.0.1",
            "port": 8332,
            "user": "xxx",
            "password": "yyy"
        }
    ],

    "p2p": {
        "enabled": true,
        "host": "127.0.0.1",
        "port": 8333,
        "disableTransactions": true
    },

    "mposMode": {
        "enabled": false,
        "host": "127.0.0.1",
        "port": 3306,
        "user": "me",
        "password": "mypass",
        "database": "ltc",
        "checkPassword": true,
        "autoCreateWorker": false
    }

}

Thanks.
6  Alternate cryptocurrencies / Mining (Altcoins) / Installing NOMP. on: October 23, 2018, 06:16:27 PM
Hello,

I have a private bitcoin network (2 nodes connected among themselves)

I am installing NOMP according to this guide: https://github.com/zone117x/node-open-mining-portal

When running "node init.js" I get these errors:

Code:
2018-10-23 20:02:54 [POSIX]	[Connection Limit] (Safe to ignore) POSIX module not installed and resource (connection) limit was not raised
2018-10-23 20:02:54 [Master] [CLI] CLI listening on port 17117
2018-10-23 20:02:55 [Master] [PoolSpawner] Spawned 1 pool(s) on 1 thread(s)
2018-10-23 20:02:55 [Payments] [bitcoin] Payment processing setup to run every 20 second(s) with daemon (xxx@127.0.0.1:8332) and redis (127.0.0.1:6379)
events.js:183
      throw er; // Unhandled 'error' event
      ^

Error: bind EACCES 0.0.0.0:80
    at listenOnMasterHandle (net.js:1420:16)
    at rr (internal/cluster/child.js:121:12)
    at Worker.send (internal/cluster/child.js:88:7)
    at process.onInternalMessage (internal/cluster/utils.js:42:8)
    at emitTwo (events.js:131:20)
    at process.emit (events.js:214:7)
    at emit (internal/child_process.js:762:12)
    at _combinedTickCallback (internal/process/next_tick.js:142:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
2018-10-23 20:02:55 [Master] [Website] Website process died, spawning replacement...
2018-10-23 20:02:55 [Payments] [bitcoin] Finished interval - time spent: 4ms total, 2ms redis, 2ms daemon RPC
2018-10-23 20:02:55 [Switching] [Setup] (Thread 1) Loading last proxy state from redis
2018-10-23 20:02:55 [Pool] [bitcoin] (Thread 1) Share processing setup with redis (127.0.0.1:6379)
2018-10-23 20:02:55 [Pool] [bitcoin] (Thread 1) No rewardRecipients have been setup which means no fees will be taken
2018-10-23 20:02:55 [Pool] [bitcoin] (Thread 1) Daemon is still syncing with network (download blockchain) - server will be started once synced
2018-10-23 20:02:55 [Pool] [bitcoin] (Thread 1) Downloaded NaN% of blockchain from 2 peers
events.js:183

Any idea what is wrong?

Thanks.
7  Bitcoin / Development & Technical Discussion / Re: Bitcoin-core. Unhandled rejection RpcError: 404 Not Found when calling getBlockc on: September 15, 2018, 09:13:49 PM
The solution was to insert "rest=1" in bitcoin.conf.

8  Bitcoin / Development & Technical Discussion / Re: Bitcoin-core. Unhandled rejection RpcError: 404 Not Found when calling getBlockc on: September 15, 2018, 08:36:48 PM
Hi.

If you take a look at the library "doc" https://github.com/ruimarinho/bitcoin-core#getblockchaininformationcallback the function is
getBlockchainInformation
If I use getBlockchainInfo I get "TypeError: client.getblockchaininfo is not a function"
Using "bitcoin-cli getblockchaininfo" external command, works perfectly.

I am surprised not to find a single complete example using the client.

Using postman with url localhost:8332/rest/tx/b4dd08f32be15d96b7166fd77afd18aece7480f72af6c9c7f9c5cbeb01e686fe.json and body parameters: username=xxx & password=yyy I get the same: "404 Not Found"
9  Bitcoin / Development & Technical Discussion / Bitcoin-core. Unhandled rejection RpcError: 404 Not Found when calling getBlockc on: September 15, 2018, 10:00:00 AM
Please help me. I have lost a lot of time with this.

I am running a fully synchronized bitcoin-core mainnet node. I run this code to access the node:

Code:
import Client from 'bitcoin-core'
let client = new Client( { username: 'xxx', password: 'yyy', port: 8332})
client.getBlockchainInformation().then( res => console.log("res: ", res))

I have also tried without the port attribute and with port:8444. I get these errors:

Code:
W20180915-09:18:15.768(2)? (STDERR) Unhandled rejection RpcError: 404 Not Found
W20180915-09:18:15.768(2)? (STDERR)     at Client.rest (/home/r2d2/vue/txxx/node_modules/bitcoin-core/dist/src/parser.js:117:13)
W20180915-09:18:15.769(2)? (STDERR)     at apply (/home/r2d2/vue/txxx/node_modules/lodash/lodash.js:475:27)
W20180915-09:18:15.769(2)? (STDERR)     at Client.wrapper (/home/r2d2/vue/txxx/node_modules/lodash/lodash.js:5337:16)
W20180915-09:18:15.769(2)? (STDERR)     at Request.self.callback (/home/r2d2/vue/txxx/node_modules/request/request.js:185:22)
W20180915-09:18:15.769(2)? (STDERR)     at emitTwo (events.js:131:20)
W20180915-09:18:15.769(2)? (STDERR)     at Request.emit (events.js:214:7)
W20180915-09:18:15.769(2)? (STDERR)     at Request.<anonymous> (/home/r2d2/vue/txxx/node_modules/request/request.js:1161:10)
W20180915-09:18:15.769(2)? (STDERR)     at emitOne (events.js:116:13)
W20180915-09:18:15.769(2)? (STDERR)     at Request.emit (events.js:211:7)
W20180915-09:18:15.770(2)? (STDERR)     at IncomingMessage.<anonymous> (/home/r2d2/vue/txxx/node_modules/request/request.js:1083:12)
W20180915-09:18:15.770(2)? (STDERR)     at Object.onceWrapper (events.js:313:30)
W20180915-09:18:15.770(2)? (STDERR)     at emitNone (events.js:111:20)
W20180915-09:18:15.770(2)? (STDERR)     at IncomingMessage.emit (events.js:208:7)
W20180915-09:18:15.770(2)? (STDERR)     at endReadableNT (_stream_readable.js:1064:12)
W20180915-09:18:15.770(2)? (STDERR)     at _combinedTickCallback (internal/process/next_tick.js:138:11)
W20180915-09:18:15.770(2)? (STDERR) From previous event:
W20180915-09:18:15.770(2)? (STDERR)     at Client.getBlockchainInformation (/home/r2d2/vue/txxx/node_modules/bitcoin-core/dist/src/index.js:238:69)
W20180915-09:18:15.770(2)? (STDERR)     at Promise.asyncApply (server/jobs.js:24:10)
W20180915-09:18:15.771(2)? (STDERR)     at /home/r2d2/.meteor/packages/promise/.0.11.1.1vczms8.mxi5++os+web.browser+web.browser.legacy+web.cordova/npm/node_modules/meteor-promise/fiber_pool.js:43:40

Receiving rawTx and rawBlock notifications via zmq works ok cause, for a change, I found proper doc: Streaming transactions from bitcoind via ZeroMQ.

My bitcoin.conf file is:

Code:
##
## bitcoin.conf configuration file. Lines beginning with # are comments.
##

# Network-related settings:

# Run on the test network instead of the real bitcoin network.
#testnet=0

# Run a regression test network
#regtest=1
# when we don't need it to run as a daemon.
daemon=1

# Connect via a SOCKS5 proxy
#proxy=127.0.0.1:9050

# Bind to given address and always listen on it. Use [host]:port notation for IPv6
#bind=<addr>

# Bind to given address and whitelist peers connecting to it. Use [host]:port notation for IPv6
#whitebind=<addr>

txindex = 1

# Use as many addnode= settings as you like to connect to specific peers
#addnode=69.164.218.197
#addnode=10.0.0.2:8333

# Alternatively use as many connect= settings as you like to connect ONLY to specific peers
#connect=69.164.218.197
#connect=10.0.0.1:8333

# Listening mode, enabled by default except when 'connect' is being used
#listen=1

# Maximum number of inbound+outbound connections.
#maxconnections=

#
# JSON-RPC options (for controlling a running Bitcoin/bitcoind process)
#

# server=1 tells Bitcoin-Qt and bitcoind to accept JSON-RPC commands
server=1

# Bind to given address to listen for JSON-RPC connections. Use [host]:port notation for IPv6.
# This option can be specified multiple times (default: bind to all interfaces)
#rpcbind=<addr>
rpcbind=127.0.0.1

# If no rpcpassword is set, rpc cookie auth is sought. The default `-rpccookiefile` name
# is .cookie and found in the `-datadir` being used for bitcoind. This option is typically used
# when the server and client are run as the same user.
#
# If not, you must set rpcuser and rpcpassword to secure the JSON-RPC api. The first
# method(DEPRECATED) is to set this pair for the server and client:
rpcuser=xxx
rpcpassword=yyy
#
# The second method `rpcauth` can be added to server startup argument. It is set at intialization time
# using the output from the script in share/rpcuser/rpcuser.py after providing a username:
#
# ./share/rpcuser/rpcuser.py alice
# String to be appended to bitcoin.conf:
# rpcauth=alice:f7efda5c189b999524f151318c0c86$d5b51b3beffbc02b724e5d095828e0bc8b2456e9ac8757ae3211a5d9b16a22ae
# Your password:
# DONT_USE_THIS_YOU_WILL_GET_ROBBED_8ak1gI25KFTvjovL3gAM967mies3E=
#
# On client-side, you add the normal user/password pair to send commands:
#rpcuser=alice
#rpcpassword=DONT_USE_THIS_YOU_WILL_GET_ROBBED_8ak1gI25KFTvjovL3gAM967mies3E=
#
# You can even add multiple entries of these to the server conf file, and client can use any of them:
# rpcauth=bob:b2dd077cb54591a2f3139e69a897ac$4e71f08d48b4347cf8eff3815c0e25ae2e9a4340474079f55705f40574f4ec99

# How many seconds bitcoin will wait for a complete RPC HTTP request.
# after the HTTP connection is established.
#rpcclienttimeout=30

# By default, only RPC connections from localhost are allowed.
# Specify as many rpcallowip= settings as you like to allow connections from other hosts,
# either as a single IPv4/IPv6 or with a subnet specification.

# NOTE: opening up the RPC port to hosts outside your local trusted network is NOT RECOMMENDED,
# because the rpcpassword is transmitted over the network unencrypted.

# server=1 tells Bitcoin-Qt to accept JSON-RPC commands.
# it is also read by bitcoind to determine if RPC should be enabled
#rpcallowip=10.1.1.34/255.255.255.0
#rpcallowip=1.2.3.4/24
#rpcallowip=2001:db8:85a3:0:0:8a2e:370:7334/96
rpcallowip=127.0.0.1

# as seen in https://bitcoin.stackexchange.com/questions/71800/bitcoin-rpc-econnrefused:
port=8444

# Listen for RPC connections on this TCP port:
rpcport=8332

# You can use Bitcoin or bitcoind to send commands to Bitcoin/bitcoind
# running on another host using this option:
#rpcconnect=127.0.0.1

# Create transactions that have enough fees so they are likely to begin confirmation within n blocks (default: 6).
# This setting is over-ridden by the -paytxfee option.
#txconfirmtarget=n

# Miscellaneous options

# Pre-generate this many public/private key pairs, so wallet backups will be valid for
# both prior transactions and several dozen future transactions.
#keypool=100

# Pay an optional transaction fee every time you send bitcoins.  Transactions with fees
# are more likely than free transactions to be included in generated blocks, so may
# be validated sooner.
#paytxfee=0.00

# Enable pruning to reduce storage requirements by deleting old blocks.
# This mode is incompatible with -txindex and -rescan.
# 0 = default (no pruning).
# 1 = allows manual pruning via RPC.
# >=550 = target to stay under in MiB.
#prune=550

# User interface options

# Start Bitcoin minimized
#min=1

# Minimize to the system tray
#minimizetotray=1

# receiving raw transactions.
zmqpubrawblock=tcp://127.0.0.1:28332
zmqpubrawtx=tcp://127.0.0.1:28333

Thanks.
10  Economy / Scam Accusations / Re: CEX stole my deposit. Over two weeks waiting. on: December 15, 2017, 03:42:27 PM
cex is a SCAM.

I deposited 800€ over two weeks ago and my money is nowhere to be seen.

There is no customer support. Nobody answer my tickets.

Money stolen by cex.

They pretend to be an exchange but they are thieves.

Not just you either but a lot of other people have similar issues with cex.io.

I actually wouldn't really hesitate calling them a scam right now. I see their ads every single day on youtube, which shows that they are still willing to spend money on advertising their business. Yet they don't seem to have spent any effort in maintaining the accounts of their customers which really sucks because i remember they were one of the best places to exchange fiat to BTC before, with cloud mining as well.

Keep contacting support and hope to see a response. That's pretty much all you can do.

If you look at the scam accusations every exchange is a scam. I can't seem to find any exchange without scam accusations. I personally have used CEX.io and everything went fine. It's also true that most of the times is the user's fault. Did your bank process the deposit OP?
They acknowledged recieving my deposit and told me they needed 3 days of processing. Then they told me it could take up to 14 days and from then just automated answers.
Money stolen.
CEX IS A SCAM.
11  Economy / Scam Accusations / CEX stole my deposit. Over two weeks waiting. on: December 14, 2017, 07:57:36 AM
cex is a SCAM.

I deposited 800€ over two weeks ago and my money is nowhere to be seen.

There is no customer support. Nobody answer my tickets.

Money stolen by cex.

They pretend to be an exchange but they are thieves.
12  Alternate cryptocurrencies / Bounties (Altcoins) / Re: [BOUNTY GIVE AWAY] free 100 DAT Token for every friends you refer [ICO] on: December 12, 2017, 05:20:35 PM
I don't get it.

I got 12 entries but received no DAT token.

Only the winner got tokens?
13  Economy / Exchanges / Let's demand Kraken our bitcoin gold on: November 14, 2017, 08:25:52 AM
Hi all.

Yesterday I opened a support ticket in kraken demanding my bitcoins gold. (No answer yet)

I encourage everybody in the same situation to pressure those thieves to give us our bitcoins gold.
Pages: [1]
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!