« previous next »
Pages: [1]   Go Down

Author Topic: BitShares 2.0 - Why are transactions pending for 25 plus blocks?  (Read 1795 times)

0 Members and 1 Guest are viewing this topic.

October 14, 2015, 03:36:29 am Reply #8

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
Re: BitShares 2.0 - Why are transactions pending for 25 plus blocks?
yup .. checkpoint fits perfectly here!
Logged
October 14, 2015, 03:28:49 am Reply #7

Tuck Fheman

  • Guest
Re: BitShares 2.0 - Why are transactions pending for 25 plus blocks?
Quote from: Troglodactyl on October 14, 2015, 03:08:38 am
You can't.  It's a worst case scenario thing.  If someone smashed the internet and thus separated the witnesses so they couldn't communicate, the last irreversible block would be the safe place to resume when global communication was restored.

So, it's a hardcoded checkpoint?
Logged
October 14, 2015, 03:14:05 am Reply #6

Offline puppies

  • Hero Member
  • *****
  • Posts: 1659
    • View Profile
  • BitShares: puppies
Re: BitShares 2.0 - Why are transactions pending for 25 plus blocks?
Quote from: Troglodactyl on October 14, 2015, 03:08:38 am
Quote from: Tuck Fheman on October 14, 2015, 02:54:20 am
Quote from: xeroc on October 14, 2015, 02:46:59 am
Yup ... 7 blocks pending means they will be IRREVERSIBLE after 7 blocks

You can reverse transactions? If so, why only some?

Very good way of explaining it.

You can't.  It's a worst case scenario thing.  If someone smashed the internet and thus separated the witnesses so they couldn't communicate, the last irreversible block would be the safe place to resume when global communication was restored.
Logged
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads
October 14, 2015, 03:13:48 am Reply #5

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
Re: BitShares 2.0 - Why are transactions pending for 25 plus blocks?
it compares to the 6 blocks waiting time of bitcoin ... in contrast to bitcoin .. after the tx confirmed by 2/3 of all witnesse .. the transaction is ABSOLUTELY irreversible .. while bitcoin only has like a 99.9999% :D .. basically a cosmetic difference :)

anyway .. a single confirmation in bts could be considered more "certain" than a single confirmation in btc
Logged
October 14, 2015, 03:08:38 am Reply #4

Offline Troglodactyl

  • Hero Member
  • *****
  • Posts: 960
    • View Profile
Re: BitShares 2.0 - Why are transactions pending for 25 plus blocks?
Quote from: Tuck Fheman on October 14, 2015, 02:54:20 am
Quote from: xeroc on October 14, 2015, 02:46:59 am
Yup ... 7 blocks pending means they will be IRREVERSIBLE after 7 blocks

You can reverse transactions? If so, why only some?

You can't.  It's a worst case scenario thing.  If someone smashed the internet and thus separated the witnesses so they couldn't communicate, the last irreversible block would be the safe place to resume when global communication was restored.
Logged
October 14, 2015, 02:54:20 am Reply #3

Tuck Fheman

  • Guest
Re: BitShares 2.0 - Why are transactions pending for 25 plus blocks?
Quote from: xeroc on October 14, 2015, 02:46:59 am
Yup ... 7 blocks pending means they will be IRREVERSIBLE after 7 blocks

You can reverse transactions? If so, why only some?
Logged
October 14, 2015, 02:46:59 am Reply #2

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
Re: BitShares 2.0 - Why are transactions pending for 25 plus blocks?
Yup ... 7 blocks pending means they will be IRREVERSIBLE after 7 blocks
Logged
October 14, 2015, 02:03:01 am Reply #1

Tuck Fheman

  • Guest
BitShares 2.0 - Why are transactions pending for 25 plus blocks?


Is this normal or expected?
« Last Edit: October 14, 2015, 02:05:50 am by Tuck Fheman »
Logged
Pages: [1]   Go Up
« previous next »
 

Page created in 0.224 seconds with 28 queries.