Contract Factories
Has there been any research into how a contract factory might be made in Michelson/Liquidity?
To elaborate, in Solidity a contract factory might look like:
pragma solidity ^0.4.8;
contract Bakery {
// index of created contracts
address public contracts;
// useful to know the row count in contracts index
function getContractCount()
public
constant
returns(uint contractCount)
{
return contracts.length;
}
// deploy a new contract
function newCookie()
public
returns(address newContract)
{
Cookie c = new Cookie();
contracts.push(c);
return c;
}
}
contract Cookie {
// suppose the deployed contract has a purpose
function getFlavor()
public
constant
returns (string flavor)
{
return "mmm ... chocolate chip";
}
}
(referenced from https://ethereum.stackexchange.com/questions/13415/deploy-contract-from-contract-in-solidity)
This is a powerful feature in DAPP development, as it allows you to build an object oriented structure for your DAPP where requests can create new contracts. It is a well established design pattern, so what would the equivalent be in the Tezos ecosystem?
michelson
asked 3 hours ago
RobRob
2885
add a comment |
Has there been any research into how a contract factory might be made in Michelson/Liquidity?
To elaborate, in Solidity a contract factory might look like:
pragma solidity ^0.4.8;
contract Bakery {
// index of created contracts
address public contracts;
// useful to know the row count in contracts index
function getContractCount()
public
constant
returns(uint contractCount)
{
return contracts.length;
}
// deploy a new contract
function newCookie()
public
returns(address newContract)
{
Cookie c = new Cookie();
contracts.push(c);
return c;
}
}
contract Cookie {
// suppose the deployed contract has a purpose
function getFlavor()
public
constant
returns (string flavor)
{
return "mmm ... chocolate chip";
}
}
(referenced from https://ethereum.stackexchange.com/questions/13415/deploy-contract-from-contract-in-solidity)
This is a powerful feature in DAPP development, as it allows you to build an object oriented structure for your DAPP where requests can create new contracts. It is a well established design pattern, so what would the equivalent be in the Tezos ecosystem?
michelson
asked 3 hours ago
RobRob
2885
It appears likeCREATE_CONTRACT { storage 'g ; parameter 'p ; code ... }would work, but this will bloat the size of a contract a bit, and it feels like there should be a way to handle this gracefully like in Solidity's Java style class instantiation.
– Rob
3 hours ago
If not, a clean example in Michelson would be nice.
– Rob
3 hours ago
ok cool, probably a ways out then.
– Rob
3 hours ago
1
I put a comment that I deleted to convert it into an answer. I missed your comment that was added afterwards. My apologies for this.
– FFF
3 hours ago
add a comment |
Has there been any research into how a contract factory might be made in Michelson/Liquidity?
To elaborate, in Solidity a contract factory might look like:
pragma solidity ^0.4.8;
contract Bakery {
// index of created contracts
address public contracts;
// useful to know the row count in contracts index
function getContractCount()
public
constant
returns(uint contractCount)
{
return contracts.length;
}
// deploy a new contract
function newCookie()
public
returns(address newContract)
{
Cookie c = new Cookie();
contracts.push(c);
return c;
}
}
contract Cookie {
// suppose the deployed contract has a purpose
function getFlavor()
public
constant
returns (string flavor)
{
return "mmm ... chocolate chip";
}
}
(referenced from https://ethereum.stackexchange.com/questions/13415/deploy-contract-from-contract-in-solidity)
This is a powerful feature in DAPP development, as it allows you to build an object oriented structure for your DAPP where requests can create new contracts. It is a well established design pattern, so what would the equivalent be in the Tezos ecosystem?
michelson
asked 3 hours ago
RobRob
2885
Has there been any research into how a contract factory might be made in Michelson/Liquidity?
To elaborate, in Solidity a contract factory might look like:
pragma solidity ^0.4.8;
contract Bakery {
// index of created contracts
address public contracts;
// useful to know the row count in contracts index
function getContractCount()
public
constant
returns(uint contractCount)
{
return contracts.length;
}
// deploy a new contract
function newCookie()
public
returns(address newContract)
{
Cookie c = new Cookie();
contracts.push(c);
return c;
}
}
contract Cookie {
// suppose the deployed contract has a purpose
function getFlavor()
public
constant
returns (string flavor)
{
return "mmm ... chocolate chip";
}
}
(referenced from https://ethereum.stackexchange.com/questions/13415/deploy-contract-from-contract-in-solidity)
This is a powerful feature in DAPP development, as it allows you to build an object oriented structure for your DAPP where requests can create new contracts. It is a well established design pattern, so what would the equivalent be in the Tezos ecosystem?
michelson
michelson
asked 3 hours ago
RobRob
2885
asked 3 hours ago
RobRob
2885
asked 3 hours ago
RobRob
2885
asked 3 hours ago
RobRob
2885
asked 3 hours ago
RobRob
2885
2885
It appears likeCREATE_CONTRACT { storage 'g ; parameter 'p ; code ... }would work, but this will bloat the size of a contract a bit, and it feels like there should be a way to handle this gracefully like in Solidity's Java style class instantiation.
– Rob
3 hours ago
If not, a clean example in Michelson would be nice.
– Rob
3 hours ago
ok cool, probably a ways out then.
– Rob
3 hours ago
1
I put a comment that I deleted to convert it into an answer. I missed your comment that was added afterwards. My apologies for this.
– FFF
3 hours ago
add a comment |
It appears likeCREATE_CONTRACT { storage 'g ; parameter 'p ; code ... }would work, but this will bloat the size of a contract a bit, and it feels like there should be a way to handle this gracefully like in Solidity's Java style class instantiation.
– Rob
3 hours ago
If not, a clean example in Michelson would be nice.
– Rob
3 hours ago
ok cool, probably a ways out then.
– Rob
3 hours ago
1
I put a comment that I deleted to convert it into an answer. I missed your comment that was added afterwards. My apologies for this.
– FFF
3 hours ago
It appears like
CREATE_CONTRACT { storage 'g ; parameter 'p ; code ... } would work, but this will bloat the size of a contract a bit, and it feels like there should be a way to handle this gracefully like in Solidity's Java style class instantiation.– Rob
3 hours ago
It appears like
CREATE_CONTRACT { storage 'g ; parameter 'p ; code ... } would work, but this will bloat the size of a contract a bit, and it feels like there should be a way to handle this gracefully like in Solidity's Java style class instantiation.– Rob
3 hours ago
If not, a clean example in Michelson would be nice.
– Rob
3 hours ago
If not, a clean example in Michelson would be nice.
– Rob
3 hours ago
ok cool, probably a ways out then.
– Rob
3 hours ago
ok cool, probably a ways out then.
– Rob
3 hours ago
1
1
I put a comment that I deleted to convert it into an answer. I missed your comment that was added afterwards. My apologies for this.
– FFF
3 hours ago
I put a comment that I deleted to convert it into an answer. I missed your comment that was added afterwards. My apologies for this.
– FFF
3 hours ago
add a comment |
1 Answer
1
active
oldest
votes
There is a very succinct discussion in the announcement for SmartPy https://medium.com/@SmartPy_io/introducing-smartpy-and-smartpy-io-d4013bee7d4e#15ee.
The idea is to have a contract that holds a big_map and each element of the big_map represents a contract.
This is absolutely not restricted to SmartPy and it is directly doable in Michelson, Liquidity or Fi.
This subject also appeared here:
What is the BigMap container and why does it matter?
answered 3 hours ago
FFFFFF
636212
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "698"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftezos.stackexchange.com%2fquestions%2f745%2fcontract-factories%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
There is a very succinct discussion in the announcement for SmartPy https://medium.com/@SmartPy_io/introducing-smartpy-and-smartpy-io-d4013bee7d4e#15ee.
The idea is to have a contract that holds a big_map and each element of the big_map represents a contract.
This is absolutely not restricted to SmartPy and it is directly doable in Michelson, Liquidity or Fi.
This subject also appeared here:
What is the BigMap container and why does it matter?
answered 3 hours ago
FFFFFF
636212
add a comment |
There is a very succinct discussion in the announcement for SmartPy https://medium.com/@SmartPy_io/introducing-smartpy-and-smartpy-io-d4013bee7d4e#15ee.
The idea is to have a contract that holds a big_map and each element of the big_map represents a contract.
This is absolutely not restricted to SmartPy and it is directly doable in Michelson, Liquidity or Fi.
This subject also appeared here:
What is the BigMap container and why does it matter?
answered 3 hours ago
FFFFFF
636212
add a comment |
There is a very succinct discussion in the announcement for SmartPy https://medium.com/@SmartPy_io/introducing-smartpy-and-smartpy-io-d4013bee7d4e#15ee.
The idea is to have a contract that holds a big_map and each element of the big_map represents a contract.
This is absolutely not restricted to SmartPy and it is directly doable in Michelson, Liquidity or Fi.
This subject also appeared here:
What is the BigMap container and why does it matter?
answered 3 hours ago
FFFFFF
636212
There is a very succinct discussion in the announcement for SmartPy https://medium.com/@SmartPy_io/introducing-smartpy-and-smartpy-io-d4013bee7d4e#15ee.
The idea is to have a contract that holds a big_map and each element of the big_map represents a contract.
This is absolutely not restricted to SmartPy and it is directly doable in Michelson, Liquidity or Fi.
This subject also appeared here:
What is the BigMap container and why does it matter?
answered 3 hours ago
FFFFFF
636212
edited 2 hours ago
answered 3 hours ago
FFFFFF
636212
answered 3 hours ago
FFFFFF
636212
answered 3 hours ago
FFFFFF
636212
636212
add a comment |
add a comment |
Thanks for contributing an answer to Tezos Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftezos.stackexchange.com%2fquestions%2f745%2fcontract-factories%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
It appears like
CREATE_CONTRACT { storage 'g ; parameter 'p ; code ... }would work, but this will bloat the size of a contract a bit, and it feels like there should be a way to handle this gracefully like in Solidity's Java style class instantiation.– Rob
3 hours ago
If not, a clean example in Michelson would be nice.
– Rob
3 hours ago
ok cool, probably a ways out then.
– Rob
3 hours ago
1
I put a comment that I deleted to convert it into an answer. I missed your comment that was added afterwards. My apologies for this.
– FFF
3 hours ago