Server contest creation #34
Comments
nathanielhourt
added a commit
to nathanielhourt/StakeWeightedVoting
that referenced
this issue
Mar 31, 2016
…k on evaluator for vote operations
nathanielhourt
added a commit
to nathanielhourt/StakeWeightedVoting
that referenced
this issue
Mar 31, 2016
nathanielhourt
added a commit
to nathanielhourt/StakeWeightedVoting
that referenced
this issue
Apr 8, 2016
nathanielhourt
added a commit
to nathanielhourt/StakeWeightedVoting
that referenced
this issue
May 9, 2016
… available If the contest creator chooses not to be anonymous, his signature on the contest will be validated and he will be set as the contest creator now. Remaining work: implement the backend call for purchasing a contest, which will broadcast a transaction creating the contest.
nathanielhourt
added a commit
that referenced
this issue
May 9, 2016
…113) If the contest creator chooses not to be anonymous, his signature on the contest will be validated and he will be set as the contest creator now. Remaining work: implement the backend call for purchasing a contest, which will broadcast a transaction creating the contest.
nathanielhourt
added a commit
that referenced
this issue
May 10, 2016
* Progress #34: Set contest creator on created contests, if available If the contest creator chooses not to be anonymous, his signature on the contest will be validated and he will be set as the contest creator now. Remaining work: implement the backend call for purchasing a contest, which will broadcast a transaction creating the contest. * Cleanup: Make contest datagram key a well-defined type Previously, the key on the contest datagram as a Data field containing an FC-serialized std::pair. This is super dirty, so I've changed it to contain a capnp-serialized struct, which is defined in datagram.capnp. This is much cleaner. Also, a minor cleanup in CustomEvaluator: create BlobMessageReader, which makes creating a MessageReader from a Data::Reader a single-line affair. * Progress #33: Groundwork A little infrastructure necessary to start #33 in earnest. * Progress #33: UNTESTED: Implement contest feed
|
Resolved by 0af3325 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add support for creating a contest and publishing it to the blockchain. Related: #19 (client-side equivalent), #40 (transaction creation). This is triggered by a call to
ContestCreator->purchaseContest()inshared/capnp/contestcreator.capnp.The server will calculate the final price for the contest, and return a purchase API to the client along with a list of price adjustments due to coupons or extra fees. When the purchase is complete, the transaction creating the contest should be created, signed and broadcast.
The text was updated successfully, but these errors were encountered: