Giter Club home page Giter Club logo

stark-anatomy's People

Contributors

a00012025 avatar andrewmilson avatar aszepieniec avatar einar-triton avatar etan-k avatar hidenori-shinohara avatar jan-ferdinand avatar jsign avatar jun-hee-lee avatar jzuiddam avatar l-as avatar samlaf avatar sword-smith avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

stark-anatomy's Issues

The generator and primitive _nth_root

I have a question about the generator and primitive _nth_root, it says the code also needs to supply the user with a generator for the entire multiplicative group, What is the entire multiplicative group, is it Fp*?
If the root is the generator of Fp*, how to derive the primitive_nth_root? why is the 407 omitted in the primitive_nth_root function? Can you tell me, thanks

  def generator( self ):
        assert(self.p == 1 + 407 * ( 1 << 119 )), "Do not know generator for other fields beyond 1+407*2^119"
        return FieldElement(85408008396924667383611388730472331217, self)
        
    def primitive_nth_root( self, n ):
        if self.p == 1 + 407 * ( 1 << 119 ):
            assert(n <= 1 << 119 and (n & (n-1)) == 0), "Field does not have nth root of unity where n > 2^119 or not power of two."
            root = FieldElement(85408008396924667383611388730472331217, self)
            order = 1 << 119
            while order != n:
                root = root^2
                order = order/2
            return root
        else:
            assert(False), "Unknown field, can't return root of unity."

[Question] Minor questions about this tutorial

Thank you very much for writing this series of tutorials. It's a great study material for me. In the process of learning I had some small questions:

In Part 1: STARK Overview, here's what got me wondering:

Interpolation and Polynomial IOPs: …… At this point the AIR constraints give rise to operations polynomials that send low-degree polynomials to low-degree polynomials only if the constraints are satisfied. The verifier simulates these operations and can thus derive new polynomials whose low degree certifies the satisfiability of the constraint system, and thus the integrity of the computation.

  1. what do 'operations polynomials' stand for ? Or maybe I got something wrong with my sentence break...?
  2. 'send low-degree polynomials to low-degree polynomials' means what ? After having the AIR constraints, I think it's the time for getting 'quotients' , what do the two 'low-degree polynomials' here refer to respectively?

I would appreciate it if you could answer my questions above.

Explain how to use ZK-STARKs

For example, can I create transaction and make proof and check proof?
And how to use Your code in blockchain protocol?

Incorrect size of signature?

Hi, I noticed that in the code/test_rpsss.py it has following line

print("size of signature:", len(sig), "bytes, or ", len(sig) / (2**13), "kB")

Which outputs

size of signature: 1309136 bytes, or  159.806640625 kB

Should it be divided by 2**10 because sig is an array of bytes? If so, the signature sizes in rescue-prime.md and faster.md would need to be updated.

Besides, thanks for the great tutorial!

omicron variables are not assigned at all?

Hey I am confused about these lines in stark.py in prove() function

# symbolically evaluate transition constraints
point = [Polynomial([self.field.zero(), self.field.one()])] + trace_polynomials + [tp.scale(self.omicron) for tp in trace_polynomials]
transition_polynomials = [a.evaluate_symbolic(point) for a in transition_constraints]

Isn't the point bigger array than transition_constraints have variables? And thus these omicron variables are not being assigned at all?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.