 Show Posts
|
|
Pages: [1] 2 3 4 5 »
|
|
@darklonj
Sent 1 tBtc b075bb00ac79f8b495ed42fde7446103735939a7805093bd2abd3932c43042bd
|
|
|
|
Are you sending testnet3 BTC or testnet4?
testnet3 BTC |
|
|
|
tb1qy92g4xe505jywdjhmlsutymculkpunm34pgng8 - I would be grateful. Thank you.
Sent 1 tBTC e5e38a1708ceca83d2c758780e6037e49932df3700c1b343cc7cae5082cbae06 |
|
|
|
Working on my project please I sent me some here's my tbtc address - tb1qjnje0swc63ps2g6rg9ke9hjgtqj6cuqhfg6nlj
Sent 1 tBTC 12fc0ba55da98192d18b26955d81ceebd4902d3d9f1d0d8dcaaf00d4f48c2663 @abdulazizkhatamovSent 1 tBTC b96e3379e26ffbd5248c01ce4af7563b3ec205f730792e3346f86655332febd5 |
|
|
|
Here's my tbtc address - tb1q29ufjpdz6382r3hffteldjdt6hgdfq8kcmernm
Sent 1 tBTC c1e97d1595be1119a16c508f1731217437b0853648c023eee6e0b73b9fac28b3 |
|
|
|
My tbtc address - 0xd3C6008eA3146e555bE4176B7a13aa31a8609F6F
It is not a tBTC address |
|
|
|
If this is still open I would like to request tBTC: tb1ql90yh97qdmqyq8tfk0hgvz5zr4e9l864s0vxa5
Thanks in advance.
Open and working. Sent 1 tBTC eb50b2112e9aa3bde8bf6118df7667f09976aa6456f99f325bfb22b71d2eecb0 |
|
|
|
Sorry guys, i haven't traced my thread because seen low activity. Anyway i'm back and decided to send 1 (one) tBTC for each request. Your 1tBTC transaction tb1qpykg8pcfn3m45zqtvuujg5zd3k3x446mm67y48 015c9c0176a46583b81b69899ac5821b6faa3522bfffc353526b303f8cec5e31
My address thanks: tb1q4fpjt2jpxwjj806wwfehrndstr9g589gz53r2m
1 tBTC sent a91b5f2f9cf7c6c306071c08651f3d3ac2f555b7e14b05ac717c4cb64df51845
Are you still sending? I would need very much... Address: bc1qpykg8pcfn3m45zqtvuujg5zd3k3x446m3u9hw5
This is Mainnet address (real value btc), you have to obtain testnet address starting from m or tb1 [moderator's note: consecutive posts merged] |
|
|
|
I looked at my old Model X and it says on the back that it was made in France - does yours say the same? I don't know about those older models, but I think I read a few years ago that their devices are manufactured in China, and only partially assembled in France - and by some strange law, you can declare any such product as being made in France or the EU.
I am surprised that Trezor does not support all possible altcoins like Ledger, but it is obvious that there are so many new coins that it is not possible to add them all/create an app for them.
My stick says it made in France too.  Regarding the coins i found no way to add Algorand and Polkadot in Trezor, and Ledger natively supports them without installing 3-rd party apps. |
|
|
|
~snip~
I also googled that not charging problem and found that so many other issues exists, so my case is not something special. For now i'm thinking to grab nano s plus which has no battery at all and I hope to get rid this issue in future.
After buying such a defective device, do you still have confidence in the company that manufactured it? For most people, this would be a sign to look in another direction, but as far as I can see, you are good with electronics, so maybe you need new challenges? I blame Ledger company because they can't make proper reliable battery contact, and why they wouldn't just hire normal engineers to do that. So i only disappointed of quality of Ledger X not all Ledger product lineup, therefore i might buy Nano S Plus. BTW i got Trezor Model T, i bought both devices to compare them. Trezor lacks some coins i need in Ledger, so i need to use them both. |
|
|
|
I never thought that so called "secure" device might be such engineering crap. I bought a brand new nano X and it died in first day of use! I was able to set it up and put some assets via Ledger Live. The first suspicious call was when i saw a low battery warning and device won't charging while connected to PC. Then it just died without any signs of life whilst still connected, Ledger Live reported i need reconnect device again. I tried pressing both buttons, holding them - no effect, screen blank. I have found similar issue on youtube https://www.youtube.com/watch?v=wxpth47Le0c but that guy had problem with "not charging message" anyway i have opened device and measured battery voltage directly on terminals before BMS and it was 3.1 volts, then i charged it till 4.2 volts which corresponds to full charged li-ion cell, assembled back and tried to on device - not working. That's how i charged battery using direct connection  I also googled that not charging problem and found that so many other issues exists, so my case is not something special. For now i'm thinking to grab nano s plus which has no battery at all and I hope to get rid this issue in future. UPD. Well, not over... I managed to back Ledger's X corp back to life! I found that bms gone to locked state therefore power was removed from output terminals, actually that's expected behavior, because battery had very low charge. So i have short applied 4.2 volts to bms terminals those marked as P+ and P- and bms then returned to active state supplying power.  However, after assembling device back still no battery charging while connected to USB.It is definitely no charging contact with pcb. |
|
|
|
I dont think 20 minutes would be enough to accurately calculate the miners true avg hashrate, you need 24-48hour+ at a place like antpool
Nice, my question about Antminer S9 Solo tbtc mining now having separate thread. Actually all works good, since my miner already seen many days of mining before now it's not suitable for mining real btc because having many unstable chips, however it's enough for mining tbtc if miner power reduced. For everyone, just short clarificationsBasically you need to follow original thread - Solo mine testnet bitcoins with cgminer, Bitcoin Core, and a Compac F https://bitcointalk.org/index.php?topic=5415335.60 but you dont need to setup cgminer, because Antminer has its own, which should be configured via antminer web interface. Then you need to setup own pool with https://github.com/benjamin-wilson/public-pool |
|
|
|
Do you have more tBTC?
Yes i do. Sent 0.05 tbtc 96ff5b4a33780d959d979f6f726e6e4bf272221d16b42a5a0d1275be1a5a1f9a |
|
|
|
Thanks in advance been looking for a good faucet, now i stumbled upon this. pls be real!! Here's my address -tb1pn7eq9ytfnh9975tg42k7zxq3uc70zd9p2lrhd6kkf56rh4m5wh4qxhstys
Sent 0.05 tbtc 6063aee06f30db3d6356b2362191e8e0d44cc4df02647e334fd06b3ab5c003a3 |
|
|
|
Since I've already mined enough tbtc for my development work, I have created this thread to help bitcointalk users with tbtc for any tests and development purposes. If you tired from getting small tbtc from public faucets and/or don't want to setup own mining rig, then just drop your tbtc address here in this topic and i will send 0.05 tbtcUPD. 23.02.2025 Now i'm sending 1 tBTC.  TERMSFree? Sure!!! one person = one transaction i may stop sending at any time |
|
|
|
--snip--
I have disabled restart function and so far the miner running for 10 mins without restarts keeping approx. 9th/s hashrate.
It's a not a big deal, but why it cant reach at least 13 th/s which it has on antpool?
--snip--
I was thinking about low power enchanted mode being enabled, but you also mentioned you get 13 TH/s on Antpool. So at this point, i suggest you to create new thread on Mining support section. Yes, i had 13 th/s on antpool for about 20 mins of testing. I further investigated miner chips and found that many already yellow and red, therefore asic runs unstable and reducing hashrate. Considering above i have reduced mining speed at the lowest possible profile 8 th/s and 600 watt power which is more than enough for mining tbtc. At that point i've mined more than i need tbtc for my development work, and i'm going to share the rest with other developers in separate thread. |
|
|
|
--snip-- Miner status page showing that pool alive and it accepts blocks, but public pool log shows that antminer connects and disconnects. getblocktemplate tx count: 3519
new block
getblocktemplate tx count: 3522
getblocktemplate tx count: 3525
getblocktemplate tx count: 3525
Killing dead clients
getblocktemplate tx count: 3527
Client d7cddb19 disconnected, hadError?:false
block height change
block height change
block height change
New client ID: : ae04772d, ::ffff:192.168.1.170:43403
getblocktemplate tx count: 3520
getblocktemplate tx count: 3522
getblocktemplate tx count: 3523
Killing dead clients
getblocktemplate tx count: 3525
getblocktemplate tx count: 3525
getblocktemplate tx count: 3526
Client ae04772d disconnected, hadError?:false
New client ID: : 5dffbf71, ::ffff:192.168.1.170:43643
getblocktemplate tx count: 3527
getblocktemplate tx count: 3529
Killing dead clients
getblocktemplate tx count: 3530
getblocktemplate tx count: 3530
getblocktemplate tx count: 3533
getblocktemplate tx count: 3535
Client 5dffbf71 disconnected, hadError?:false
Killing dead clients
New client ID: : 822fc25b, ::ffff:192.168.1.170:43965
getblocktemplate tx count: 3536
I guess it some problem with public pool config again. Previously i tested this Antminer S9 on real btc pool (antpool) and it was working fine without disconnects. All i can suggest is to also check your S9 log, either from it's webpage[1] or SSH (if you already use custom firmware which allow that) in order to see whether S9 mention reason of the disconnection. [1] https://support.bitmain.com/hc/en-us/articles/360025531034--For-S9series-Common-Problems-Indicated-by-Miner-s-Kernel-Log-and-Ways-to-Resolve-themThanks for suggestions, indeed it was related to to miner settings, i found theses messages in its watchdog logs Sun Nov 3 08:27:36 2024 Total hashrate 9609.871 is less than 90 percents of 13115.70, stopping miner
Sun Nov 3 08:34:18 2024 Total hashrate 9653.626 is less than 90 percents of 13115.70, stopping miner
Sun Nov 3 08:41:00 2024 Total hashrate 9631.782 is less than 90 percents of 13115.70, stopping miner
Sun Nov 3 08:47:42 2024 Total hashrate 9607.137 is less than 90 percents of 13115.70, stopping miner
Sun Nov 3 08:54:24 2024 Total hashrate 9470.335 is less than 90 percents of 13115.70, stopping miner
Sun Nov 3 09:08:08 2024 Total hashrate 9635.339 is less than 90 percents of 13115.70, stopping miner
Sun Nov 3 09:14:29 2024 Total hashrate 9790.512 is less than 90 percents of 13115.70, stopping miner
Sun Nov 3 09:21:11 2024 Total hashrate 9694.529 is less than 90 percents of 13115.70, stopping miner
Sun Nov 3 09:27:53 2024 Total hashrate 9782.224 is less than 90 percents of 13115.70, stopping miner
It means miner was stopping because of hashrate threshold drop, and further i found setting which adjust this  Restart if hashrate us below given number of percents of ideal hashrateI have disabled restart function and so far the miner running for 10 mins without restarts keeping approx. 9th/s hashrate. It's a not a big deal, but why it cant reach at least 13 th/s which it has on antpool?  |
|
|
|
Okay, i left miner running while i was sleeping and despite his disconnects it mined 5 btc. But i don't understand why balance showing as unmatured and on-chain separately, these small transactions in october i got from btc faucets.  |
|
|
|
At a glance, your config seems to be right. Have you tried checking debug.log file created by Bitcoin Core? It may give some hints why public-pool unable connect to Bitcoin Core.
I'm back, had some home issues. So, i found problem in my .env config file, BITCOIN_RPC_URL was defined in wrong way. I've added port number to it, but it should be ommited. instead BITCOIN_RPC_URL=http://192.168.1.181:5000 should be BITCOIN_RPC_URL=http://192.168.1.181 And pool log now says it connected to bitcoind. [Nest] 6983 - 11/02/2024, 11:23:17 PM LOG [RouterExplorer] Mapped {/api/client/:address/:workerName/:sessionId, GET} route +1ms
[Nest] 6983 - 11/02/2024, 11:23:17 PM LOG [RoutesResolver] AddressController {/api/address}: +0ms
[Nest] 6983 - 11/02/2024, 11:23:17 PM LOG [RouterExplorer] Mapped {/api/address/settings, PATCH} route +1ms
[Nest] 6983 - 11/02/2024, 11:23:17 PM LOG [NestApplication] Nest application successfully started +20ms
API listening on http://0.0.0.0:3334
Bitcoin RPC connected
block height change
Stratum server is listening on port 3333
Then i have configured Antminer S9 pool config as pool: stratum+tcp://192.168.1.15:3333 Worker: mrYpN6imcBNkmsceuw5C7JjtFa9AyasEBL password: x Miner status page showing that pool alive and it accepts blocks, but public pool log shows that antminer connects and disconnects. getblocktemplate tx count: 3519
new block
getblocktemplate tx count: 3522
getblocktemplate tx count: 3525
getblocktemplate tx count: 3525
Killing dead clients
getblocktemplate tx count: 3527
Client d7cddb19 disconnected, hadError?:false
block height change
block height change
block height change
New client ID: : ae04772d, ::ffff:192.168.1.170:43403
getblocktemplate tx count: 3520
getblocktemplate tx count: 3522
getblocktemplate tx count: 3523
Killing dead clients
getblocktemplate tx count: 3525
getblocktemplate tx count: 3525
getblocktemplate tx count: 3526
Client ae04772d disconnected, hadError?:false
New client ID: : 5dffbf71, ::ffff:192.168.1.170:43643
getblocktemplate tx count: 3527
getblocktemplate tx count: 3529
Killing dead clients
getblocktemplate tx count: 3530
getblocktemplate tx count: 3530
getblocktemplate tx count: 3533
getblocktemplate tx count: 3535
Client 5dffbf71 disconnected, hadError?:false
Killing dead clients
New client ID: : 822fc25b, ::ffff:192.168.1.170:43965
getblocktemplate tx count: 3536
I guess it some problem with public pool config again. Previously i tested this Antminer S9 on real btc pool (antpool) and it was working fine without disconnects. |
|
|
|
Earlier i forget to mention you could connect S9 directly to Bitcoin Core since GBT protocol is very outdated. You may want to try that since you've failed to run public-pool.
I was able to run public pool after i match node and npm version used in docker container, but got "Error getmininginfo 404 - undefined " error. Probably it's some issue with my configs. bitcoin_testnet.conf testnet=1
txindex=1
server=1
[test]
rpcport=5000
rpcallowip=192.168.1.0/24
rpcuser=dem
rpcpassword=mypassword
rpcbind=0.0.0.0
.env # bitcoin node running in your private network 192.168.1.0/24
BITCOIN_RPC_URL=http://192.168.1.181:5000
# bitcoin node running undockered on the same PC
# needs to add rpcallowip=172.16.0.0/12 to your bitcoin.conf
#BITCOIN_RPC_URL=http://host.docker.internal
BITCOIN_RPC_USER=dem
BITCOIN_RPC_PASSWORD=mypassword
BITCOIN_RPC_PORT=5000
BITCOIN_RPC_TIMEOUT=10000
# You can use this instead of BITCOIN_RPC_USER and BITCOIN_RPC_PASSWORD
BITCOIN_RPC_COOKIEFILE=
# Enable in bitcoin.conf with
# zmqpubrawblock=tcp://*:3000
# BITCOIN_ZMQ_HOST="tcp://192.168.1.100:3000"
API_PORT=3334
STRATUM_PORT=3333
#optional telegram bot
#TELEGRAM_BOT_TOKEN=
#optional discord bot
#DISCORD_BOT_CLIENTID=
#DISCORD_BOT_GUILD_ID=
#DISCORD_BOT_CHANNEL_ID=
#optional
DEV_FEE_ADDRESS=
# mainnet | testnet
NETWORK=testnet
API_SECURE=false
# Default is "public-pool", you can change it to any string it will be removed if it will make the block or coinbase script too big
POOL_IDENTIFIER="public-pool"
And actual error after starting public pool $ npm run start
> public-pool@0.0.1 start
> nest start
[Nest] 13117 - 10/22/2024, 10:43:11 PM LOG [NestFactory] Starting Nest application...
[Nest] 13117 - 10/22/2024, 10:43:11 PM LOG [InstanceLoader] TypeOrmModule dependencies initialized +117ms
[Nest] 13117 - 10/22/2024, 10:43:11 PM LOG [InstanceLoader] HttpModule dependencies initialized +1ms
[Nest] 13117 - 10/22/2024, 10:43:11 PM LOG [InstanceLoader] CacheModule dependencies initialized +0ms
[Nest] 13117 - 10/22/2024, 10:43:11 PM LOG [InstanceLoader] ConfigHostModule dependencies initialized +0ms
[Nest] 13117 - 10/22/2024, 10:43:11 PM LOG [InstanceLoader] DiscoveryModule dependencies initialized +0ms
[Nest] 13117 - 10/22/2024, 10:43:11 PM LOG [InstanceLoader] ConfigModule dependencies initialized +1ms
[Nest] 13117 - 10/22/2024, 10:43:11 PM LOG [InstanceLoader] ScheduleModule dependencies initialized +1ms
[Nest] 13117 - 10/22/2024, 10:43:11 PM LOG [InstanceLoader] TypeOrmCoreModule dependencies initialized +37ms
[Nest] 13117 - 10/22/2024, 10:43:11 PM LOG [InstanceLoader] TypeOrmModule dependencies initialized +1ms
[Nest] 13117 - 10/22/2024, 10:43:11 PM LOG [InstanceLoader] TypeOrmModule dependencies initialized +0ms
[Nest] 13117 - 10/22/2024, 10:43:11 PM LOG [InstanceLoader] TypeOrmModule dependencies initialized +0ms
[Nest] 13117 - 10/22/2024, 10:43:11 PM LOG [InstanceLoader] TypeOrmModule dependencies initialized +0ms
[Nest] 13117 - 10/22/2024, 10:43:11 PM LOG [InstanceLoader] TypeOrmModule dependencies initialized +0ms
[Nest] 13117 - 10/22/2024, 10:43:11 PM LOG [InstanceLoader] TypeOrmModule dependencies initialized +0ms
[Nest] 13117 - 10/22/2024, 10:43:11 PM LOG [InstanceLoader] ClientStatisticsModule dependencies initialized +1ms
[Nest] 13117 - 10/22/2024, 10:43:11 PM LOG [InstanceLoader] ClientModule dependencies initialized +0ms
[Nest] 13117 - 10/22/2024, 10:43:11 PM LOG [InstanceLoader] AddressSettingsModule dependencies initialized +0ms
[Nest] 13117 - 10/22/2024, 10:43:11 PM LOG [InstanceLoader] TelegramSubscriptionsModule dependencies initialized +0ms
[Nest] 13117 - 10/22/2024, 10:43:11 PM LOG [InstanceLoader] BlocksModule dependencies initialized +0ms
[Nest] 13117 - 10/22/2024, 10:43:11 PM LOG [InstanceLoader] RpcBlocksModule dependencies initialized +0ms
[Nest] 13117 - 10/22/2024, 10:43:11 PM LOG [InstanceLoader] AppModule dependencies initialized +4ms
[Nest] 13117 - 10/22/2024, 10:43:11 PM LOG [RoutesResolver] AppController {/api}: +32ms
[Nest] 13117 - 10/22/2024, 10:43:11 PM LOG [RouterExplorer] Mapped {/api/info, GET} route +5ms
[Nest] 13117 - 10/22/2024, 10:43:11 PM LOG [RouterExplorer] Mapped {/api/pool, GET} route +1ms
[Nest] 13117 - 10/22/2024, 10:43:11 PM LOG [RouterExplorer] Mapped {/api/network, GET} route +1ms
[Nest] 13117 - 10/22/2024, 10:43:11 PM LOG [RouterExplorer] Mapped {/api/info/chart, GET} route +1ms
[Nest] 13117 - 10/22/2024, 10:43:11 PM LOG [RoutesResolver] ClientController {/api/client}: +0ms
[Nest] 13117 - 10/22/2024, 10:43:11 PM LOG [RouterExplorer] Mapped {/api/client/:address, GET} route +1ms
[Nest] 13117 - 10/22/2024, 10:43:11 PM LOG [RouterExplorer] Mapped {/api/client/:address/chart, GET} route +1ms
[Nest] 13117 - 10/22/2024, 10:43:11 PM LOG [RouterExplorer] Mapped {/api/client/:address/:workerName, GET} route +1ms
[Nest] 13117 - 10/22/2024, 10:43:11 PM LOG [RouterExplorer] Mapped {/api/client/:address/:workerName/:sessionId, GET} route +1ms
[Nest] 13117 - 10/22/2024, 10:43:11 PM LOG [RoutesResolver] AddressController {/api/address}: +0ms
[Nest] 13117 - 10/22/2024, 10:43:11 PM LOG [RouterExplorer] Mapped {/api/address/settings, PATCH} route +1ms
[Nest] 13117 - 10/22/2024, 10:43:11 PM LOG [NestApplication] Nest application successfully started +24ms
API listening on http://0.0.0.0:3334
Could not reach RPC host
Error getmininginfo 404 - undefined
Error getmininginfo 404 - undefined
Error getmininginfo 404 - undefined
Error getmininginfo 404 - undefined
Error getmininginfo 404 - undefined
Error getmininginfo 404 - undefined
Error getmininginfo 404 - undefined
Error getmininginfo 404 - undefined
Error getmininginfo 404 - undefined
Error getmininginfo 404 - undefined
Error getmininginfo 404 - undefined
Error getmininginfo 404 - undefined
Error getmininginfo 404 - undefined
Error getmininginfo 404 - undefined
Error getmininginfo 404 - undefined
Error getmininginfo 404 - undefined
Error getmininginfo 404 - undefined
Error getmininginfo 404 - undefined
Error getmininginfo 404 - undefined
Stratum server is listening on port 3333
Error getmininginfo 404 - undefined
2. Ignore step 2 of tutorial on this thread. You need to configure your S9 connect to your Bitcoin Core directly using RPC url, user and password (which use GBT protocol) or your own mining pool (which use stratum protocol). I can't get how to set bitcoin testnet address and rpc username and password in asic config.  I tried to set as: URL: http://dem:mypassword@192.168.1.181:5000Worker: bitcoin_testnet_address Password: x but it does not work, miner reports Dead pool |
|
|
|
|
