Bitcoin Forum
November 18, 2018, 07:09:07 AM *
News: Latest Bitcoin Core release: 0.17.0 [Torrent].
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Should this officially be implemented ? [Look Inside]  (Read 694 times)
Patatas
Legendary
*
Offline Offline

Activity: 1358
Merit: 1032


Crypto-Games.net: Multiple coins, multiple games


View Profile
November 11, 2017, 09:45:26 AM
 #1

Today while waiting for one of my transaction to get confirmed ,I wasted too much of my time figuring out how to rebroadcast the transaction with higher fees or speed up the existing one.Excuse me for not checking the network fees for that time before sending it.

Now my question is,should a broadcasted transaction be automatically dropped if it doesn't get confirmed in 'n' amount of time ? Right now,I don't know if my tx will ever get confirmed or it will be dropped off.I can't do much but wait and watch.Maybe there was a way in Core that the algo drops transactions if they don't get confirmed in certain amount of time ? 


▄▄▄████████▄▄▄
▄██████████████████▄
▄██████████████████████▄
██████████████████████████
████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
██████████████████████████████
████████████████████████████
██████████████████████████
▀██████████████████████▀
▀██████████████████▀
▀▀▀████████▀▀▀
   ███████
██████████
██████████
██████████
██████████
██████████
██████████
██████████
██████████
██████████
██████████
██████████
███████
BTC  ◉PLAY  ◉XMR  ◉DOGE  ◉BCH  ◉STRAT  ◉ETH  ◉GAS  ◉LTC  ◉DASH  ◉PPC
     ▄▄██████████████▄▄
  ▄██████████████████████▄        █████
▄██████████████████████████▄      █████
████ ▄▄▄▄▄ ▄▄▄▄▄▄ ▄▄▄▄▄ ████     ▄██▀
████ █████ ██████ █████ ████    ▄██▀
████ █████ ██████ █████ ████    ██▀
████ █████ ██████ █████ ████    ██
████ ▀▀▀▀▀ ▀▀▀▀▀▀ ▀▀▀▀▀ ████ ▄██████▄
████████████████████████████ ████████
███████▀            ▀███████ ▀██████▀
█████▀                ▀█████
▀██████████████████████████▀
  ▀▀████████████████████▀▀ 
✔️DICE           
✔️BLACKJACK
✔️PLINKO
✔️VIDEO POKER
✔️ROULETTE     
✔️LOTTO
1542524947
Hero Member
*
Offline Offline

Posts: 1542524947

View Profile Personal Message (Offline)

Ignore
1542524947
Reply with quote  #2

1542524947
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1542524947
Hero Member
*
Offline Offline

Posts: 1542524947

View Profile Personal Message (Offline)

Ignore
1542524947
Reply with quote  #2

1542524947
Report to moderator
DannyHamilton
Legendary
*
Offline Offline

Activity: 2198
Merit: 1385



View Profile
November 11, 2017, 10:42:26 AM
 #2

Now my question is,should a broadcasted transaction be automatically dropped if it doesn't get confirmed in 'n' amount of time?

This is not possible in a decentralized system.

Maybe there was a way in Core that the algo drops transactions if they don't get confirmed in certain amount of time ? 

No.

ranochigo
Legendary
*
Offline Offline

Activity: 1568
Merit: 1094

Somewhat inactive.


View Profile WWW
November 11, 2017, 10:49:50 AM
 #3

Today while waiting for one of my transaction to get confirmed ,I wasted too much of my time figuring out how to rebroadcast the transaction with higher fees or speed up the existing one.Excuse me for not checking the network fees for that time before sending it.
Its pretty easy to be honest.
Now my question is,should a broadcasted transaction be automatically dropped if it doesn't get confirmed in 'n' amount of time ? Right now,I don't know if my tx will ever get confirmed or it will be dropped off.I can't do much but wait and watch.Maybe there was a way in Core that the algo drops transactions if they don't get confirmed in certain amount of time ? 
Transactions do not have a timestamp to it neither do the nodes have a synchronized time with each other. Since every node sees the transaction at a different time, they will not drop the transaction at the same time. In addition, if the transaction gets rebroadcast, the nodes wouldn't drop it at all. Its not up to you, anyone can do it.

ETFbitcoin
Legendary
*
Offline Offline

Activity: 1498
Merit: 1261


Make winning bets on sports with Sportsbet.io!


View Profile WWW
November 11, 2017, 05:54:39 PM
 #4

Which wallet do you use? I'm sure most wallet these days let use increase your transaction fees easily (with Replace-by-Fee), unless you use outdated wallet. Additionally, you could ask the receiver to spend the unconfirmed input (CPFP or Child-pay-for-parent) to make your transaction can get confirmed faster.
Also, i think it's not needed to implant your idea since some nodes automatically delete unconfirmed transaction from their mempool after few days to few weeks Roll Eyes

   ▄▄██████▄▄
  ████████████
███▄▄
 ██████████████▀▀▀██▄
████████████████   ▀██▄
████████████████     ▀██
██████████████       ██▌
██████████████        ▐██
██▌▀▀██████▀▀         ▐██
▐██                   ██▌
 ██▄                 ▄██
  ▀██▄             ▄██▀
    ▀██▄▄▄     ▄▄▄██▀
      ▀▀█████████▀▀





███████████████████████████
███████████▀▀         ▀▀███
████████▀   ▄▄██▄  ▀█▄  ▀██
██████▀  ▄████████▄  ▀█  ██
████▀  ▄██████▄▀  ██▄    ██
███▀  ██████▄▀  ▄▀████▄  ██
██▀  █████▄▀  ▄▀██████  ▄██
██  ▀███▄▀  ▄▀███████  ▄███
██    ▀██▄▄▀███████▀  ▄████
██  █▄  ▀████████▀  ▄██████
██▄  ▀█▄  ▀██▀▀   ▄████████
███▄▄         ▄▄███████████
███████████████████████████
███████████████████████████
████████▀▀       ▀▀████████
█████▀   ▄ ▀███▀ ▄   ▀█████
████  ▄████▄ ▀ ▄████▄  ████
███  ▄ ▀███▀ ▄ ▀███▀ ▄  ███
██  ▄██ ▀▀ ▄███▄ ▀▀ ██▄  ██
██  █▀ ▄█ ███████ █▄ ▀█  ██
██   ▄███▄ █████ ▄███▄   ██
███  ████▀ ▄▄▄▄▄ ▀████  ███
████  ▀ ▄ ▀█████▀ ▄ ▀  ████
█████▄  ▀▀▄ ███ ▄▀▀  ▄█████
████████▄▄       ▄▄████████
███████████████████████████
████████     INDUSTRY LEADING BITCOIN SPORTSBOOK     ████████
LIVE
STREAMING
DAILY PRICE
BOOSTS
LIVE DEALER
CASINO
FAST & SECURE
PAYMENTS
███████████████████████████
████████▀▀       ▀▀████████
█████▀  ▄█▄  ▀  ▄▄   ▀█████
████  ▄  ▀    ▀█████▄  ████
███  ▀█▀   ▀█▄   ▀▀██▄  ███
██  ▄    █▄  ▀██▄▄  ▀█▄  ██
██  █▀ ▄  ▀█▄  ▀███▄  ▀  ██
██    ▄██  ▀██▄  ▀███▄   ██
███  ▀████  ▀███▄  ▀█▀  ███
████  ▀████  ▀████▄    ████
█████▄   ▀▀█▄  ▀▀▀   ▄█████
████████▄▄       ▄▄████████
███████████████████████████
███████████████████████████
████████▀▀ █████ ▀▀████████
█████▀    ▄█████▄    ▀█████
██████▄▄█▀▀ ▄▄▄ ▀▀█▄▄██████
███▀███▀ ▄███▀███▄ ▀███▀███
██   █ ▄██▀     ▀██▄ █   ██
██   █ ██         ██ █   ██
██   █ ▀██▄▄█ █▄▄██▀ █   ██
███▄███▄ ▀██▄▄▄██▀ ▄███▄███
██████▀▀█▄▄ ▀▀▀ ▄▄█▀▀██████
█████▄    ▀█████▀    ▄█████
████████▄▄ █████ ▄▄████████
███████████████████████████





..WIN WITH US!..
ivantosov
Newbie
*
Offline Offline

Activity: 20
Merit: 1


View Profile
November 11, 2017, 06:09:05 PM
 #5

Do you mean to write maximum block number for transaction?
suzanne5223
Sr. Member
****
Offline Offline

Activity: 616
Merit: 262



View Profile
November 11, 2017, 08:37:57 PM
 #6

Today while waiting for one of my transaction to get confirmed ,I wasted too much of my time figuring out how to rebroadcast the transaction with higher fees or speed up the existing one.Excuse me for not checking the network fees for that time before sending it.

Now my question is,should a broadcasted transaction be automatically dropped if it doesn't get confirmed in 'n' amount of time ? Right now,I don't know if my tx will ever get confirmed or it will be dropped off.I can't do much but wait and watch.Maybe there was a way in Core that the algo drops transactions if they don't get confirmed in certain amount of time ? 
There is no way for you to drop transaction which has been sent but waiting for confirmation and I think it will be better for you to check the transaction predicting site https://bitcoinfees.earn.com/ next time before sending out  bitcoin in other to avoid this kind of situation. However, on this thread https://bitcointalk.org/index.php?topic=2204426.msg24415596#new you'll the person who'll fast the transaction for you.

MartPlatform
Jr. Member
*
Offline Offline

Activity: 37
Merit: 1


View Profile
November 13, 2017, 04:59:00 AM
 #7

No, I think you should not do it officially. Bad effect to your coin.  Sad
Quickseller
Copper Member
Legendary
*
Offline Offline

Activity: 1596
Merit: 1210

in 2 min-groin injury, dildo on field, & 6-9 score


View Profile WWW
November 13, 2017, 05:27:08 AM
 #8

The only way this would be possible if transactions were only valid up until a maximum block number. This could be implemented and enforced via a soft fork.

The problem with this is that it could result in situations in which the miners are given incentives to orphan blocks.

3PjXm2XYDKLV5mN3oiKzNTyVvSkqP3ujeq <-- tipping address Advertise here
Thirdspace
Hero Member
*****
Offline Offline

Activity: 798
Merit: 609


Mixing reinvented for your privacy | chipmixer.com


View Profile
November 15, 2017, 01:16:07 PM
 #9

The only way this would be possible if transactions were only valid up until a maximum block number. This could be implemented and enforced via a soft fork.

The problem with this is that it could result in situations in which the miners are given incentives to orphan blocks.
yes exactly based on block numbers,
we have a way to lock fund by using lock_time
why not introducing drop_time for option to drop unconfirmed transaction?
this would be similar to TTL time to live of an unconfirmed transaction up to certain block number

Transactions do not have a timestamp but the 'n' amount of time here can be based on the block number
so eventhough all nodes not synchronized in time but they do synchronized in block numbers
would this against the principle of bitcoin as a digital currency
I don't quite get the second part, what/why given incentives to orphan blocks?

Carlton Banks
Legendary
*
Offline Offline

Activity: 2184
Merit: 1405



View Profile
November 15, 2017, 01:35:13 PM
 #10

This feature already exists in Bitcoin, since version 0.12.0 I believe (i.e. nearly 18 months ago).

Transactions unconfirmed after a configurable time limit are kicked out of the local mempool. Default time limit is 1 week. Of course, the mempools of other nodes may retain transactions for a length of time that is not 1 week, because the option is configurable.

Vires in numeris
Coding Enthusiast
Sr. Member
****
Offline Offline

Activity: 517
Merit: 400


Novice C♯ Coder


View Profile WWW
November 15, 2017, 02:43:35 PM
 #11

Just a little correction
This feature already exists in Bitcoin, since version 0.12.0 I believe (i.e. nearly 18 months ago).
Oct 3, 2015

Default time limit is 1 week.
2 weeks, still not changed.

Projects List+Suggestion box
Donation link using BIP21
Bech32 Donation link!
BitcoinTransactionTool (0.9.2):  Ann - Source Code
Watch Only Bitcoin Wallet (supporting SegWit) (3.1.0):  Ann - Source Code
SharpPusher (broadcast transactions) (0.10.0): Ann - Source Code

Carlton Banks
Legendary
*
Offline Offline

Activity: 2184
Merit: 1405



View Profile
November 15, 2017, 03:24:08 PM
 #12

Default time limit is 1 week.
2 weeks, still not changed.

Indeed, thanks Coding Enthusiast

Vires in numeris
Thirdspace
Hero Member
*****
Offline Offline

Activity: 798
Merit: 609


Mixing reinvented for your privacy | chipmixer.com


View Profile
November 15, 2017, 08:29:12 PM
 #13

Just a little correction
This feature already exists in Bitcoin, since version 0.12.0 I believe (i.e. nearly 18 months ago).
Oct 3, 2015

Default time limit is 1 week.
2 weeks, still not changed.
Transactions do not have a timestamp to it neither do the nodes have a synchronized time with each other. Since every node sees the transaction at a different time, they will not drop the transaction at the same time. In addition, if the transaction gets rebroadcast, the nodes wouldn't drop it at all. Its not up to you, anyone can do it.

but it works locally (dropping on local mempool) and other nodes may (re)broadcast it again (read ranochigo post)
thus the unconfirmed transaction goes back into (local) mempool again as new unconf.tx
it would create never ending loop which only breakable by RBF or successful double spend transaction
but by setting certain synchronized time based on block number similar to lock_time,
the unconf.tx will be dropped completely by all nodes and never be re-broadcasted again past specified block number
or I misunderstood the way that protocol works?  Huh

Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!