Peeps by @mokens
Showing page 4 of 5 (226 peeps total)
Replying to @abcoathup (0x13ebd3443fa5575f0eb173e323d8419f7452cfb1)
I don’t know if I like it but I love it more than no logo. Yay for branding. Suggest that you split your Peepeth into a mokens Peepeth and a Nick Mudge account.
I have another branding idea and I want to know what you think about it. Mokens are a real thing in the physical world. They are a sea-nomadic people known as the sea-gypsies living among islands off the coast of Thailand. Well I like to think of mokens as sea gypsies too but ...
Replying to @abcoathup (0x13ebd3443fa5575f0eb173e323d8419f7452cfb1)
I don’t know if I like it but I love it more than no logo. Yay for branding. Suggest that you split your Peepeth into a mokens Peepeth and a Nick Mudge account.
Thanks @abcoathup. I have a lot to learn. So I can learn more, can you tell me why you suggest I have a Nick Mudge account and a separate mokens account?
Replying to @pluma (0xd9fb1d684627a890347a4f6a7fe32e993617b6d8)
really like the new branding, nick! am keeping an eye on the development of mokens. 👀
@pluma I am glad you really like it and are keeping an eye on the development! Thanks for telling me and I look forward to sharing with you more interesting news soon.
Replying to @abcoathup (0x13ebd3443fa5575f0eb173e323d8419f7452cfb1)
Mokens based on avatars with attributes based on badges and achievements.
@abcoathup I like it!
Replying to @doodlemania (0xa3ffa423140b730c0c2e1cc412a80cc49f125c01)
Very cool looking service! Why the need for a different net in Metamask?
Hi @doodlemania, mokens.io is in beta. It will come out of beta mode and get launched on the main ethereum network after the bug bounty is complete next week: https://github.com/mudgen/mokens-bug-bounty
1 Enso
mokens has a new logo: https://mokens.io/img/logo_only.svg
The mokens bug bounty program got its first bug report: https://github.com/mudgen/mokens-bug-bounty/issues/1
I would like to integrate mokens with peepeth somehow. @NateStipe, @abcoathup, @Bevan
mokens is designed to work with other ethereum based systems and contracts.
ERC721-based bug bounty program: https://github.com/mudgen/mokens-bug-bounty
Replying to @Bevan (0x30755d3e65c0cf46c35b72d11e52d941c5fc3a3e)
That's true. Peepeth is using Infura's nodes right now (a great convenience), but others are replicating / pinning the data thanks to @sponnet's "Peepeth pinner": https://medium.com/@sponnet/peepeth-now-always-available-b1a43f382058
Great!
Replying to @mokens (0x0b22380b7c423470979ac3ed7d3c07696773dea1)
@Bevan, @abcoathup, do you think there will come a time when it costs money to store data on ipfs?
Well I learned more about ipfs, and it seems it won't be necessary to cost money because you can host the files yourselves. Does peepeth host its own ipfs data?
@Bevan, @abcoathup, do you think there will come a time when it costs money to store data on ipfs?
Replying to @Bevan (0x30755d3e65c0cf46c35b72d11e52d941c5fc3a3e)
I recommend @abcoathup's writeup (he came up with the idea). Also, check out https://peepeth.com/help/signing. Basically, actions are now signed, guaranteeing authorship. Peepeth then batches those actions periodically, and saves them to the blockchain.
I just finished reading https://medium.com/@abcoathup/evolution-of-decentralised-social-media-dfe567d23e54
It is really cool how you are making peepeth work!
The mokens ethereum contract bug bounty program starts today! Check it out: https://github.com/mudgen/mokens-bug-bounty
I make more improvements to https://mokens.io/about
Replying to @NateStipe (0xd5d560b2e9faddd6796ac777963dd59c42babae2)
I was clicking on the link in your original post and didn't see all of them listed. I see them now, so perhaps it was user error?
I see what you mean. It seems I have to view a moken with a direct link in OpenSea before it is displayed in the mokens category. Thanks for noticing and telling me.
Replying to @NateStipe (0xd5d560b2e9faddd6796ac777963dd59c42babae2)
Nick - Doesn't look like this impacted all of the mokens (excluding the banned ones). Didn't see Moken 3, 5 or 13 out there?
Replying to @NateStipe (0xd5d560b2e9faddd6796ac777963dd59c42babae2)
Nick - Doesn't look like this impacted all of the mokens (excluding the banned ones). Didn't see Moken 3, 5 or 13 out there?
Where are you not seeing it?
Here's the links:
https://rinkeby.opensea.io/assets/0xdCF4e7edFAcCC3E9529a8dD7D4A6F5fe0C3b4Ba3/3
https://rinkeby.opensea.io/assets/0xdCF4e7edFAcCC3E9529a8dD7D4A6F5fe0C3b4Ba3/5
Replying to @abcoathup (0x13ebd3443fa5575f0eb173e323d8419f7452cfb1)
Which then means that mokens you own automagically show in #Trust wallet thanks to @vikmeup
Awesome!
Today I implemented the API to make mokens display on OpenSea.io. Check out @abcoathup on OpenSea: https://rinkeby.opensea.io/assets/0xdCF4e7edFAcCC3E9529a8dD7D4A6F5fe0C3b4Ba3/4
Today I did a lot of work making the About webpage for mokens better and more specific. I'd love any feedback: https://mokens.io/about
Replying to @jimbob (0x0f48669b1681d41357eac232f516b77d0c10f0f1)
Also we are also working on enhancements to the authenticity side, ideally driven from the artists themselves #watchthisspace
Are you a founder of cryptogoods.co?
I updated https://mokens.io/about with the latest changes.
Replying to @NateStipe (0xd5d560b2e9faddd6796ac777963dd59c42babae2)
What are you using to determine this, the Description input? If so, are you using keywords or a word for word comparison to flag as a forgery?
Right now the forgery system is not automated. It is done by a human. In the future I want to create a contract that people use to vote on what is a forgery. But at the beginning it is done by a human.
Replying to @NateStipe (0xd5d560b2e9faddd6796ac777963dd59c42babae2)
I think you have the basis of a good idea and hope you develop it to be successful. Is there anything stopping someone else from using your idea and creating their own version doing the same thing? If there isn't, I would think the one with the best qualities will win out
Thanks Nate! I don't think there is anything stopping anyone else. I am working on this full time. I hope that it moves fast enough and that I get a funding source before people start to copy me
Replying to @NateStipe (0xd5d560b2e9faddd6796ac777963dd59c42babae2)
Could you build into the logic something that would reject a name if it has already been created (bump up against a ref table). So "Thor" moken and "Thor God of Thunder' are both okay, But a second Thor moken would not be allowed to be created.
Mokens also has a forgery system. So if a moken is created called "Thor God of Thunder" and then another moken is created called "Thor" but they are both about the god of thunder, then the second Thor would be marked and displayed as a forgery.
Replying to @NateStipe (0xd5d560b2e9faddd6796ac777963dd59c42babae2)
Could you build into the logic something that would reject a name if it has already been created (bump up against a ref table). So "Thor" moken and "Thor God of Thunder' are both okay, But a second Thor moken would not be allowed to be created.
This is already done! The ethereum contract makes it impossible to have two mokens with the same name, and this is case insensitive! The contract also disallows nonprinting characters and disallows spaces at the beginning and end of moken names.
Mokens are fully compliant with the ERC721 standard. They are generic unique assets that are designed to be used in ethereum games and systems.
I want mokens to be a generic cryptocollectible designed and created by people and that are incorporated into other people's ethereum games and systems.
Replying to @NateStipe (0xd5d560b2e9faddd6796ac777963dd59c42babae2)
I assume you make something out of each moken created? Could a majority of users collude and vote on a crazy low price? If so, I would recommend you set a minimum creation price.
I want ethereum game developers to use mokens in their games and attached valuable metrics to them that are used in their games. So if someone makes a race car moken and increases its speed value in the game, then that make it more valuable and so can sell for a higher price.
Replying to @NateStipe (0xd5d560b2e9faddd6796ac777963dd59c42babae2)
I assume you make something out of each moken created? Could a majority of users collude and vote on a crazy low price? If so, I would recommend you set a minimum creation price.
This brings up an interesting question? Why would someone want to buy an existing moken? Well there may be multiple reasons. But here is an interesting one to consider: The mokens contract is designed to be used by other contracts. I want ethereum game developers to use mokens
Replying to @NateStipe (0xd5d560b2e9faddd6796ac777963dd59c42babae2)
I assume you make something out of each moken created? Could a majority of users collude and vote on a crazy low price? If so, I would recommend you set a minimum creation price.
Yes, perhaps that is a good idea. But it is to the users' advantage to not have the mint price too low, because it will make it harder for them to sell their mokens. I think there will be a correlation between the mint price and the price users can sell their mokens.
Currently mokens can be labeled a forgery on the website. I am removing forgery information from the ethereum contract because I want to remove as much centralized control as possible. In the future the community will decide which mokens are forgeries by voting with their mokens.
Replying to @abcoathup (0x13ebd3443fa5575f0eb173e323d8419f7452cfb1)
Reduce the gas used is good. Though do you want to be able to change everything once a mokens is created?
If someone else created a second "Thor" then it would be labeled a forgery. In the future I want to create a contract that enables people to vote with the mokens about which mokens are forgeries and the website can use that as the source of forgery info.
Replying to @abcoathup (0x13ebd3443fa5575f0eb173e323d8419f7452cfb1)
Reduce the gas used is good. Though do you want to be able to change everything once a mokens is created?
For example if someone chooses to create the moken named "Thor, God of Thunder" then that moken will only ever be about Thor. The description and the attributes and the image can be changed, but the moken will always be about Thor. Each moken is a unique identity.
Replying to @abcoathup (0x13ebd3443fa5575f0eb173e323d8419f7452cfb1)
Reduce the gas used is good. Though do you want to be able to change everything once a mokens is created?
Users can change the image and the description and attributes of a moken. But they cannot change the moken id and cannot change the moken name. Essentially users can change the display and description of a moken but not what a moken is about.
Replying to @chid (0xa5460b48dce526b8646e5c283fa9bdc1b7930e79)
Interesting idea. What about a voting mechanism for deciding whether a moken should be banned, or a market for determining cost of publishing a moken which considers the content? There might be ways to protect the network from harmful content without centralisation
Interesting ideas. I decided not to ban mokens. Instead I can hide inappropriate mokens from my website. I am planning to allow the users of mokens vote for the price to mint new mokens. This gives users more control and I think will enhance quality of mokens.
Replying to @abcoathup (0x13ebd3443fa5575f0eb173e323d8419f7452cfb1)
Yes it should be removed from the contract. You should have moken owner destruction so you can delete what you own. If you or the front end cease to exist or someone else has control this shouldn’t impact mokens onchain. You will likely need a hide function on the front end
I have made minting mokens extremely efficient for what it does, down to below 112,000 gas.
Replying to @abcoathup (0x13ebd3443fa5575f0eb173e323d8419f7452cfb1)
Yes it should be removed from the contract. You should have moken owner destruction so you can delete what you own. If you or the front end cease to exist or someone else has control this shouldn’t impact mokens onchain. You will likely need a hide function on the front end
I just hate the thought of adding 20,000 gas to creating a moken plus more gas to other things. Because I don't think users will want to delete their mokens very often. What do you think?
Replying to @abcoathup (0x13ebd3443fa5575f0eb173e323d8419f7452cfb1)
Yes it should be removed from the contract. You should have moken owner destruction so you can delete what you own. If you or the front end cease to exist or someone else has control this shouldn’t impact mokens onchain. You will likely need a hide function on the front end
Instead I let users change the description, images and attributes, blanking them out if they want? If someone really doesn't want their moken they could blank out the description, image and attributes and send the moken to a different address.
Replying to @abcoathup (0x13ebd3443fa5575f0eb173e323d8419f7452cfb1)
Yes it should be removed from the contract. You should have moken owner destruction so you can delete what you own. If you or the front end cease to exist or someone else has control this shouldn’t impact mokens onchain. You will likely need a hide function on the front end
I have looked deeply into the matter of adding to the contract the functionality that enables people to delete their own mokens. Unfortunately to do this would add 20,000 gas to the mint function and add gas in other operations. What if instead I simply let users change the
Replying to @NateStipe (0xd5d560b2e9faddd6796ac777963dd59c42babae2)
I agree with both @abcoathup & @CallMeGwei . Wielding ultimate control is not progress
Yes, thanks @NateStipe
Replying to @abcoathup (0x13ebd3443fa5575f0eb173e323d8419f7452cfb1)
Yes it should be removed from the contract. You should have moken owner destruction so you can delete what you own. If you or the front end cease to exist or someone else has control this shouldn’t impact mokens onchain. You will likely need a hide function on the front end
Yes, makes sense. Thanks @abcoathup
Replying to @CallMeGwei (0x285bc660aa42b8effc6c60357cd4d8ca072be625)
If people have to trust you /not/ to ban (delete) their stuff, then why wouldn't they just trust you to handle transfers and ownership on your own database? If you give me the power to remove the middle man - but give that obsolete middle man a delete button... is that progress?
Right, this is very good to think about. Thank you. I think I am going to remove the ban/delete button.
Do you think I should remove the functionality to ban mokens? Info about that here: https://mokens.io/about @all @abcoathup @NateStipe
Replying to @abcoathup (0x13ebd3443fa5575f0eb173e323d8419f7452cfb1)
Depends on what your primary use case is for mokens. I created a vanity moken. Simple is good.
I think the primary use case will be determined by the users. There are definitely different use cases. I think vanity moken will definitely be one of the major use cases. I also hope mokens get used in ethereum games and other ethereum contracts. Yes, simple is good!
Replying to @abcoathup (0x13ebd3443fa5575f0eb173e323d8419f7452cfb1)
Mokens works fine on mobile, (apart from image upload where you have to close the dialog after uploading). Should have mobile (Trust due to Rinkeby) promoted as an option as well as MetaMask. I wasn’t clear on what the attributes were used for.
Yes, the attributes are unclear to me also. I am going to remove attributes. Makes things simpler and more clear.
I am thinking of removing attributes from mokens, because it is unclear to users what they are. Plus I am thinking that attributes could come from other contracts that use mokens in their games/systems. What do you think? @all @abcoathup
Replying to @jvck (0x49f7729c66b66cbf0a2e174ff4487be22027177c)
How long do you think it will take for main net?
About 2 or 3 weeks.