Skip to content
Snippets Groups Projects

Change tx sandbox size

    • Open Issue created by Éloïs @librelois

    https://forum.duniter.org/t/gbot-feeback-on-g1-test/3400/5?u=elois

    Edited
    To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information

    Child items ...

    • Activity

    • Éloïs
      Éloïs @librelois ·
      Author Owner

      To sum up:

      • For non-member issuer, cut the sandbox into slices according to the amount in UD, for example: ]0;10 UD]: max. 2 tx per issuer ]10 UD; 50 UD]: max. 3 tx per issuer ]50 UD; 100 UD]: max. 4 tx per issuer ]100 UD; +inf]: max. 5 tx per issuer Each slice also has a maximum total size of : MAX (200;countTxLastBlock)

      • For member issuer : limit to X pending transactions per member (for example 5)

    • inso
      inso @Insoleet ·
      Contributor

      I suggest to start having good habits when introducing new things to Duniter. I suggest the following check list of things to do :

      • Document this behaviour somewhere in the specifications
      • Development & unit tests
      • Testing on GT network
    • Cédric Moreau
      Cédric Moreau @c-geek ·
      Owner

      I would also suggest that from now on, any new feature = new branch.

    • Cédric Moreau
      Cédric Moreau @c-geek ·
      Owner

      About documentation, I tried to do it for some potential feature (that will probably be abandoned now): https://github.com/duniter/duniter/issues/840

    • Cédric Moreau changed milestone to %1.9

      changed milestone to %1.9

    • Éloïs changed the description

      changed the description

    • Éloïs changed milestone to %1.10

      changed milestone to %1.10

    Please register or sign in to reply