you have shit aftermarket firmware on it from nice hash. you need to get rid of it as I am not sure why it says you have a bad fan. alternative method you could buy 2 new fans. and swap them in. here is a good use seller if you are in usa https://vmssecuritycloud.com/product/120mm-antminer-fan/a decent price for 5 used fans free shipping to usa |
|
|
|
I found old antminer s9 and I tried to connected it to binance pool in instruction is in must happens in 10 minutes but it wasn't so I don't know what to do also I add pictures from asic admin panel if you know why all parameters = 0 please explain me if you know why what to do, please tell me I also get WARNING! FAN ERROR! But I don't know what does it mean. I also add kernel logs
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 3.14.0-xilinx-gb190cb0-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #57 SMP PREEMPT Fri Dec 9 14:49:22 CST 2016
[ 0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine model: Xilinx Zynq
[ 0.000000] cma: CMA: reserved 128 MiB at 27800000
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] On node 0 totalpages: 258048
[ 0.000000] free_area_init_node: node 0, pgdat c0740a40, node_mem_map e6fd8000
[ 0.000000] Normal zone: 1520 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 194560 pages, LIFO batch:31
[ 0.000000] HighMem zone: 496 pages used for memmap
[ 0.000000] HighMem zone: 63488 pages, LIFO batch:15
[ 0.000000] PERCPU: Embedded 8 pages/cpu @e6fc0000 s9088 r8192 d15488 u32768
[ 0.000000] pcpu-alloc: s9088 r8192 d15488 u32768 alloc=8*4096
[ 0.000000] pcpu-alloc: [0] 0 [0] 1
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 256528
[ 0.000000] Kernel command line: noinitrd mem=1008M console=ttyPS0,115200 root=ubi0:rootfs ubi.mtd=1 rootfstype=ubifs rw rootwait
[ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Memory: 884148K/1032192K available (5032K kernel code, 283K rwdata, 1916K rodata, 204K init, 258K bss, 148044K reserved, 253952K highmem)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
[ 0.000000] vmalloc : 0xf0000000 - 0xff000000 ( 240 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xef800000 ( 760 MB)
[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
[ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
[ 0.000000] .text : 0xc0008000 - 0xc06d1374 (6949 kB)
[ 0.000000] .init : 0xc06d2000 - 0xc0705380 ( 205 kB)
[ 0.000000] .data : 0xc0706000 - 0xc074cf78 ( 284 kB)
[ 0.000000] .bss : 0xc074cf84 - 0xc078d9fc ( 259 kB)
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] Dump stacks of tasks blocking RCU-preempt GP.
[ 0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[ 0.000000] NR_IRQS:16 nr_irqs:16 16
[ 0.000000] ps7-slcr mapped to f0004000
[ 0.000000] zynq_clock_init: clkc starts at f0004100
[ 0.000000] Zynq clock init
[ 0.000014] sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 3298534883328ns
[ 0.000287] ps7-ttc #0 at f0006000, irq=43
[ 0.000583] Console: colour dummy device 80x30
[ 0.000618] Calibrating delay loop... 1325.46 BogoMIPS (lpj=6627328)
[ 0.040194] pid_max: default: 32768 minimum: 301
[ 0.040407] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.040429] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.042528] CPU: Testing write buffer coherency: ok
[ 0.042848] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.042905] Setting up static identity map for 0x4c4af8 - 0x4c4b50
[ 0.043123] L310 cache controller enabled
[ 0.043142] l2x0: 8 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x72760000, Cache size: 512 kB
[ 0.120986] CPU1: Booted secondary processor
[ 0.210217] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[ 0.210345] Brought up 2 CPUs
[ 0.210364] SMP: Total of 2 processors activated.
[ 0.210372] CPU: All CPU(s) started in SVC mode.
[ 0.211010] devtmpfs: initialized
[ 0.213408] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[ 0.214584] regulator-dummy: no parameters
[ 0.221953] NET: Registered protocol family 16
[ 0.224169] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.226419] cpuidle: using governor ladder
[ 0.226431] cpuidle: using governor menu
[ 0.233730] syscon f8000000.ps7-slcr: regmap [mem 0xf8000000-0xf8000fff] registered
[ 0.235218] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[ 0.235231] hw-breakpoint: maximum watchpoint size is 4 bytes.
[ 0.235339] zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xf0080000
[ 0.256805] bio: create slab <bio-0> at 0
[ 0.258174] vgaarb: loaded
[ 0.258853] SCSI subsystem initialized
[ 0.259713] usbcore: registered new interface driver usbfs
[ 0.259888] usbcore: registered new interface driver hub
[ 0.260115] usbcore: registered new device driver usb
[ 0.260773] media: Linux media interface: v0.10
[ 0.260930] Linux video capture interface: v2.00
[ 0.261193] pps_core: LinuxPPS API ver. 1 registered
[ 0.261206] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 0.261332] PTP clock support registered
[ 0.261677] EDAC MC: Ver: 3.0.0
[ 0.262716] Advanced Linux Sound Architecture Driver Initialized.
[ 0.265437] DMA-API: preallocated 4096 debug entries
[ 0.265450] DMA-API: debugging enabled by kernel config
[ 0.265522] Switched to clocksource arm_global_timer
[ 0.285819] NET: Registered protocol family 2
[ 0.286461] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.286556] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[ 0.286714] TCP: Hash tables configured (established 8192 bind 8192)
[ 0.286773] TCP: reno registered
[ 0.286791] UDP hash table entries: 512 (order: 2, 16384 bytes)
[ 0.286841] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[ 0.287100] NET: Registered protocol family 1
[ 0.287446] RPC: Registered named UNIX socket transport module.
[ 0.287458] RPC: Registered udp transport module.
[ 0.287466] RPC: Registered tcp transport module.
[ 0.287474] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.287487] PCI: CLS 0 bytes, default 64
[ 0.287909] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
[ 0.289875] futex hash table entries: 512 (order: 3, 32768 bytes)
[ 0.291211] bounce pool size: 64 pages
[ 0.292078] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[ 0.292277] msgmni has been set to 1486
[ 0.293037] io scheduler noop registered
[ 0.293051] io scheduler deadline registered
[ 0.293090] io scheduler cfq registered (default)
[ 0.304928] dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-2364208
[ 0.304948] dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[ 0.426370] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 82, base_baud = 3124999) is a xuartps
[ 0.998840] console [ttyPS0] enabled
[ 1.003095] xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to f0068000
[ 1.010719] [drm] Initialized drm 1.1.0 20060810
[ 1.027606] brd: module loaded
[ 1.036888] loop: module loaded
[ 1.046627] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
[ 1.052379] e1000e: Copyright(c) 1999 - 2013 Intel Corporation.
[ 1.060297] libphy: XEMACPS mii bus: probed
[ 1.064662] ------------- phy_id = 0x3625e62
[ 1.069416] xemacps e000b000.ps7-ethernet: pdev->id -1, baseaddr 0xe000b000, irq 54
[ 1.078013] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.084637] ehci-pci: EHCI PCI platform driver
[ 1.091891] zynq-dr e0002000.ps7-usb: Unable to init USB phy, missing?
[ 1.098732] usbcore: registered new interface driver usb-storage
[ 1.105645] mousedev: PS/2 mouse device common for all mice
[ 1.111723] i2c /dev entries driver
[ 1.118639] zynq-edac f8006000.ps7-ddrc: ecc not enabled
[ 1.124132] cpufreq_cpu0: failed to get cpu0 regulator: -19
[ 1.130082] Xilinx Zynq CpuIdle Driver started
[ 1.134914] sdhci: Secure Digital Host Controller Interface driver
[ 1.141109] sdhci: Copyright(c) Pierre Ossman
[ 1.145377] sdhci-pltfm: SDHCI platform and OF driver helper
[ 1.152197] mmc0: no vqmmc regulator found
[ 1.156242] mmc0: no vmmc regulator found
[ 1.195541] mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
[ 1.204209] usbcore: registered new interface driver usbhid
[ 1.209715] usbhid: USB HID core driver
[ 1.214419] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[ 1.220721] nand: Micron MT29F2G08ABAEAWP
[ 1.224680] nand: 256MiB, SLC, page size: 2048, OOB size: 64
[ 1.230618] Bad block table found at page 131008, version 0x01
[ 1.236841] Bad block table found at page 130944, version 0x01
[ 1.242891] 3 ofpart partitions found on MTD device pl353-nand
[ 1.248672] Creating 3 MTD partitions on "pl353-nand":
[ 1.253761] 0x000000000000-0x000002000000 : "BOOT.bin-env-dts-kernel"
[ 1.261801] 0x000002000000-0x00000b000000 : "angstram-rootfs"
[ 1.269101] 0x00000b000000-0x000010000000 : "upgrade-rootfs"
[ 1.277989] TCP: cubic registered
[ 1.281223] NET: Registered protocol family 17
[ 1.285931] Registering SWP/SWPB emulation handler
[ 1.291801] regulator-dummy: disabling
[ 1.296105] UBI: attaching mtd1 to ubi0
[ 1.823051] UBI: scanning is finished
[ 1.834571] UBI: attached mtd1 (name "angstram-rootfs", size 144 MiB) to ubi0
[ 1.841654] UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 1.848417] UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 1.855082] UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
[ 1.861960] UBI: good PEBs: 1152, bad PEBs: 0, corrupted PEBs: 0
[ 1.867940] UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
[ 1.875047] UBI: max/mean erase counter: 29/16, WL threshold: 4096, image sequence number: 200056553
[ 1.884176] UBI: available PEBs: 0, total reserved PEBs: 1152, PEBs reserved for bad PEB handling: 40
[ 1.893392] UBI: background thread "ubi_bgt0d" started, PID 1080
[ 1.893398] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[ 1.897287] ALSA device list:
[ 1.897290] No soundcards found.
[ 1.913693] UBIFS: background thread "ubifs_bgt0_0" started, PID 1082
[ 1.942666] UBIFS: recovery needed
[ 2.009612] UBIFS: recovery completed
[ 2.013277] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[ 2.019251] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 2.028328] UBIFS: FS size: 128626688 bytes (122 MiB, 1013 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
[ 2.038214] UBIFS: reserved for root: 0 bytes (0 KiB)
[ 2.043244] UBIFS: media format: w4/r0 (latest is w4/r0), UUID C4D8A166-736F-4D68-8DC1-9B94F2C9EB77, small LPT model
[ 2.054539] VFS: Mounted root (ubifs filesystem) on device 0:11.
[ 2.061723] devtmpfs: mounted
[ 2.064829] Freeing unused kernel memory: 204K (c06d2000 - c0705000)
[ 2.859208] random: dd urandom read with 0 bits of entropy available
[ 3.105562]
[ 3.105562] bcm54xx_config_init
[ 3.705572]
[ 3.705572] bcm54xx_config_init
[ 6.706398] xemacps e000b000.ps7-ethernet: Set clk to 24999999 Hz
[ 6.712492] xemacps e000b000.ps7-ethernet: link up (100/FULL)
[ 19.745422] In axi fpga driver!
[ 19.748487] request_mem_region OK!
[ 19.751878] AXI fpga dev virtual address is 0xf01fe000
[ 19.757012] *base_vir_addr = 0xc51a
[ 19.766827] In fpga mem driver!
[ 19.772159] request_mem_region OK!
[ 19.775768] fpga mem virtual address is 0xf3000000
[ 20.484918]
[ 20.484918] bcm54xx_config_init
[ 21.084879]
[ 21.084879] bcm54xx_config_init
[ 24.085432] xemacps e000b000.ps7-ethernet: Set clk to 24999999 Hz
[ 24.091454] xemacps e000b000.ps7-ethernet: link up (100/FULL)
[ 914.880858] random: nonblocking pool is initialized
Detect 1GB control board of XILINX
Miner Type = S9
Miner compile time: Fri May 8 15:27:59 CST 2020 type: Antminer S9 (vnish 3.8.6)
set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x00000000
set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x0000ffff
Checking fans!
1 fan ok [/pre] it's a link to imgs https://ibb.co/8YGHkq9https://ibb.co/wzJ37Hdhttps://ibb.co/2yZMnzjhttps://ibb.co/ctvWfY9https://ibb.co/YWZdF7thttps://ibb.co/B3L1q5K |
|
|
|
Satoshi is more valuable than merit, assuming it is implemented on a forum as great as bitcointalk then anyone wants to pursue it. One will have unlimited hopes of getting postal incentives as all members here may have satoshis, and that just encourages more spam and also basically everyone breaks this forum rule. Specifically, you are not allowed to give people any incentive to post substantial posts in your threads. good point and his reason is he wants the multi tier system for signature campaigns to work as it does. (yes we all know it gets abused) I still can not find any place like bitcoin talk with its unique way of earning money. |
|
|
|
|
yeah all of the above about slow deliberate attacks against the early blocks makes sense if the attacker was a business trying to make money.
If the attacker is a government looking to wipe out BTC and 256bit crypto safety. They would do a few of satoshi's just to see how fast it takes them to do a single address.
Only need do a few.
Then do nothing except crack all of satoshi's addresses. Once they do that simply pull out every coin on them in under an hour. This would crash BTC out and terrify all companies using 256 bit encryption.
If I live long enough to see this happen I would be very surprised as I think this is 50 years away at best.
256 bit encryption would be wise to to stay ahead of this by becoming 512 bit.
I also think it would happen until we develop cold fusion which would enable easy power for a very big pc.
|
|
|
|
|
buddy be below 27k
hey buddy you do you.
|
|
|
|
I was thinking that a new feature might be interesting for the forum. Is it possible to implement zapping (with lightning) on topics, comments and profiles' bio?
I met with this idea on stacker.news . I found it very useful. Let me know you thoughts.
Best regards,
Signature earning along with free speech 🎤 are two of the forums strongest points. Zapping is cool but not needed here. The whole idea here is old school style. apprentice journeyman master newbie jr member full member hero legendary all earn a little more as you go up the ladder. zapping would take away from ranking up 🆙 ranking up is slow as time is needed. |
|
|
|
|
watching sherri shepard with my wife. sherri is talking about her breast reduction. she is funny 😁
|
|
|
|
Waste of money.
1) For a desktop PC all you have to do is pop the top and add in a USB card.
2) They are still plastic, with time and effort you can pull one out.
3) For the determined person it's get laptop, take off cover, un-solder the port (only 4 wires on USB 2) and solder in a new one. But at that point you might as well just pull the drive out
Most if not all PCs can disable the USB ports in BIOS and you can also set a BIOS password so that cannot be changed without the password.
-Dave
yeah bios and password lock would be best way and cost is zero. |
|
|
|
According to the cointelegraph, the trustee Nobuaki Kobayashi has changed the repayment date by 1 year. I mean directly from Oct 31, 20 23, to Oct 31, 20 24. That was so unpredictable and honestly I don't know on what basis they are delaying the repayment. Even though they have funds in their hands. It would be good if they had repaid the amount to the creditors so that they would use them according to the market's current condition. I mean according to the upcoming halving event. To be honest, I almost thought that, they would increase the repayment date. But did not think that they would put an increment of 1 year. That's so long for the waiters. But if they have waited this long then I think they can wait for another year too. Plus I have a question, is this a good factor for the market or not? I do know that, if they would pay the amount then we will see some selling of BTC, BCH and Yuan, etc. Which would cause a dump in the market. But what else I am missing other than this? This gives them a way to crash market in fall of 2024. If coins take off and are 75k in oct they release these and the market slumps. They must feel owners of the coins would sell them all. |
|
|
|
|
ahh semi retirement wake up at 920 am post on the wo. then make some breakfast 🍳 with a cup of coffee.
|
|
|
|
I'm sure the new forum software will still be expected any time soon in half a century  We had so many SMF patches recently, thanks to PowerGlove, that I am starting to think that is not science fiction anymore. If he can patch forum than he can surely do something with new software, and he already has attention of theymos. I would be more than happy with improved Personal Messages and better Trust System if possible. Oh man do I want private message improvements. I still have 800 pages and to simply be able to make a page 200 messages vs 20 would make it easier to down load the info I want and just delete the ones I don't want. |
|
|
|
I suppose one could argue that with 2020 halving, a new ATH was reached earlier than 1.5 years after the event if you consider the time of peaking above the previous ATH point and not the eventual total peak before the bear market. But it's possible to look at it from your point of view and see this pattern as well. Of course, just 3 times isn't enough to say it's a regularity, but since we've got nothing left apart from a pretty short Bitcoin history, it makes sense to try to base our guesses on that data. But if the new ATH is reached around a year and a half after halving, that doesn't mean that Bitcoin won't recover earlier because it can reach a bit over the previous ATH significantly earlier even based on historical data, as it did only 7 months after halving of 2020.
And china tore the heart out of the 2021 April move by shutting down 50% of the worlds hash. So I would argue like you may 2020 to April 2021 is 11 months and that the cycle was broken by outside forces (China). BTC seems to get ½ ing price shock in about 4 year cycle based on the ½ ing So I would say dec 2012 ½ ing nov 2013 ath may 2016 ½ ing dec 2017 ath may 2020 ½ ing April 2021 ath which does not match the op but does match reality closer |
|
|
|
well its free and I want a winner. This allows 30 free picks and should give us a winner. I will open it at block 600 and close it at block 1000. we are at block 241 https://newhedge.io/terminal/bitcoin/difficulty-estimatorLatest Block: 808656 (21 minutes ago) Current Pace: 95.4390% (241 / 252.52 expected, 11.52 behind) Previous Difficulty: 54150142369480 Current Difficulty: 57119871304635.31 Next Difficulty: between 54682813361213 and 56553289468814 Next Difficulty Change: between -4.2666% and -0.9919% Previous Retarget: Yesterday at 4:59 AM (+5.4842%) Next Retarget (earliest): October 3, 2023 at 8:35 AM (in 12d 9h 31m 24s) Next Retarget (latest): October 3, 2023 at 9:02 PM (in 12d 21h 58m 16s) Projected Epoch Length: between 14d 3h 36m 34s and 14d 16h 3m 26s getting ready to setup a retro contest. 01) -4.99 to - 4.50 02) -4.49 to - 4.00 03) -3.99 to - 3.50 04) -3.49 to - 3.00 05) -2.99 to - 2.50 06) -2.49 to - 2.00 07) -1.99 to - 1.50 08 ) -1.49 to -1.00 09) -0.99 to -0.50 10) -0.49 to -0.00 11) 0.01 to 0.50% put your name next to your pick. philipma1957 12) 0.51 to 1.00% 13) 1.01 to 1.50% 14) 1.51 to 2.00% 15) 2.01 to 2.50% 16) 2.51 to 3.00% 17) 3.01 to 3.50% 18) 3.51 to 4.00% 19) 4.01 to 4.50% 20) 4.51 to 5.00% 21) 5.01 to 5.50% 22) 5.51 to 6.00% 23) 6.01 to 6.50% 24) 6.51 to 7.00% 25) 7.01 to 7.50% 26) 7.51 to 8.00% 27) 8.01 to 8.50% 28) 8.51 to 9.00% 29) 9.01 to 9.50% 30) 9.51 to 10.00% If my pick wins I am giving it to: joker_josue to help support the talk image website. my pick will be 11) + 0.01 to 0.50% my game my rules rule 1. it is free shot to get 0.001 btc rule 2. I get to pick first and if my pick wins I give it to joker_josue rule 3. no newbies must have 10 merits and 90 days on the website. rule 4. no alts giving you a 2x or 3x shot rule 5. you can pick at blocks 600-1000 rule 6. new hedge numbers are used for deciding winner rule 7. if a tie happens due to a round issue I will give 2 prices. this happened 1 time years ago. rule 8. if BTC moons like a mother fucker I will cap prize of 0.001 btc to be 100 usd or less rule 9. my game my rules so if I think you are a sleaze and say do to your answer just accept it rule 10. if I missed something I will rule on it and you will accept the rule. start picking at block 600 |
|
|
|
That's a different scenario. We will have agreed on a price in advance, so it is clear what you sent was a mistake. If I pay 100 sats/vbyte in fees, is that clearly a mistake? What about 200? 500? The last block contained two transactions paying over 1,000 sats/vbyte in fees, when 40 sats/vbyte would have been sufficient. Should the miner refund those transactions? Or indeed, should they refund every transaction which paid more than what was necessary? What's stopping me from making all my transactions pay 1,000 sats/vbyte and then demand that the miner return my fee? These are excuses and you know it. You ignored the parts where I mentioned: "If you know that someone paid you too much in error, and it's practical and possible to refund them". No one is talking about anyone demanding a refund, but whether it would be a moral thing to do from the recipient's perspective. Just because it's judgmental of what the "refundable" amount would be, it doesn't mean it's the right thing to keep any amount sent in error (even if you have a legal right to do so). Somehow nobody in this thread had any trouble recognising that 20btc was not a normal fee and it was likely sent in error. If you send all your coins to the wrong address, no one can get them back for you.
Recipient could. If I sent all my bitcoins to your address by some weird accident, I'd like to think you would return them. Not because you have to, but because it's the right thing to do. I don't see why we should expect any different if you pay too much in fees. You might get lucky and the miner in question might be feeling generous, but you definitely shouldn't work on the assumption that they will refund your fee nor that you would have any legal recourse in such a situation.
Nobody is saying anything about any "expectations" or about introducing any rules that miners must refund such fees. As for legal recourse - you don't know that. I could easily imagine miner being ordered to return it in some jurisdictions. Yeah I am sure some judges in some countries would force a refund. I am also pretty sure if you are USA based there is no precedent on refunding so you would need to be very careful about taxes with a refund. |
|
|
|
|
My wife had 1 job from 22 to 55 she retired then 2012.
I do IT and sales. I have a btc,ltc,doge, gpu mining business. Since 2012 I have been mining.
I will likely work till 2030. But my work is not 9 to 5 in an office five days a week.
So I don’t mind working limited days and hours.
|
|
|
|
We just have to see what will happen throughout this year and next year.
And if BitQuant's prediction really comes true, it means we will see bitcoin's all-time high again after its last ATH and that would be a fantastic price jump for bitcoin.
I believe it could happen next year, either before or after the halving but unfortunately, we don't know when it will come and can only guess.
But if the price of bitcoin can reach $170000 before the halving, that means we will see a peak in the price of bitcoin, which could be above $250000, which is in line with BitQuant's predictions.
But we know that anything can happen to bitcoin and people have released many predictions about how high bitcoin will rise before the next halving.
you do understand that a price of 70k in march of 2024 would be an all-time high. We could get to 50k in march of 2024. and drop to 30-32 after April ½ ing more likely than 70k in march 2024. with a drop to 50-52k in April 2024 |
|
|
|
|
just setup safe pal
my a53 samsung was able to scan the QR code with ease
|
|
|
|
Did the rates news drop or something?
frozen for this time may go up a notch in NOV also less cuts next year then originally planned . They claim some success in inflation and job market balance.. Yeah and 2 hamburgers a milkshake and an ice tea at 5-guys today cost me $39.55 |
|
|
|
This is so obvious to people who actually know the situation but that doesn't mean that we are going to end up with a result like that at all. We need to realize that bitcoin is still not known in detail by so many people, even the ones who has heard the name bitcoin, do not know much information regarding it, and when a news station talks about how much it uses, they believe them because they do not have the better judgement to research it themselves.
This is why the ones who know, like you and me, we know that it is tiny compared to most other stuff and mostly clean, whereas the ones who do not know would fall victim to fake news and misinformation because they do not care enough to go do their research on the subject.
That's why people say that media is the king because whatever media says people blindly trust that and even if they promote fake news people will trust that news. Most of the people these days don't really do their own research and they accept whatever they hear from those media sources, and the worst thing is that the same people promote the things they heard from those media channels to other people and promote such misinformation. We Bitcoin users know that Bitcoin mining does require energy and we also know that most of the miners and mining farms are using clean energy for the purpose of Bitcoin mining but who listen to us? They listen to only media channels and believe trust words without question. Surely, the ones who do their own research are well aware of the fact that Bitcoin mining consumes not so much energy out of global electricity production, and it's actually consuming the energy from clean energy sources mostly. we have over 1000 solar panels in our mining locations. we generate close to 2 megawatts daily in solar energy. we are New Jersey based and are always looking for new and better mining locations here in NJ,USA or even in PA,USA |
|
|
|
|
Show Posts
