Open Keyrxng opened 1 year ago
/ask Create me 3 spoof issue specs that I can use to test AI. They should vary from short and easy to mid-long and complex. I'm testing which is best at extracting relevant context inferred from both the question and the peripheral context such as issue conversation and specification.
{"prompt_tokens":375,"completion_tokens":247,"total_tokens":622}
Encoder Model: SPP > 127 tokens
Sure, here are three spoof issue specs that you can use to test two LLM models:
Spoof issue spec 1 (Short and Easy):
Title: Describe the weather in New York City.
Body: What is the current temperature and weather conditions in New York City?
Spoof issue spec 2 (Mid-Long and Complex):
Title: How do you recommend planning a trip to Paris?
Body: What are the best things to do in Paris, where should I stay, what are the best restaurants to try, and how much should I budget for the trip? Include any relevant information such as visa requirements and currency exchange rates.
Spoof issue spec 3 (Long and Complex):
Title: How can I optimize my marketing strategy for my new startup?
Body: What are the best marketing channels to use for reaching potential customers, what is the most effective way to pricing your products, and how can you measure the success of your marketing campaign? Include any relevant information such as industry trends and customer behaviours.
I hope these issue specs work well for your testing purposes!
Here are three spoof issue specs that vary in length and complexity:
Short and Easy:
Mid-Length and Moderate Complexity:
Long and Complex:
These spoof issue specs vary in length and complexity, allowing you to test the AI's ability to extract relevant context from different types of issues.
{"output":239,"input":442,"total":681}
``
Bro? lmao
/ask These are poor in quality, let's step it up. Have each issue be themed in software development, as a bonus have the niche be Web3 based.
Increase the issue spec content that would be representative of real world, full size issues.
Return only the new and improved spoof specifications
{"prompt_tokens":881,"completion_tokens":627,"total_tokens":1508}
Encoder Model: SPP > 127 tokens
Here are three spoof issue specs based on the theme of software development and Web3:
Spoof issue spec 1 (Short and Easy): Title: Fix a bug in smart contract deployment
Login: xyzbrowser@gmail.com Body: Please help me fix a bug I encountered during the deployment of my smart contract on the Ethereum blockchain. Here's the address where the smart contract is hosted: 0x3786f2e187469BD00aDC2B97E7F2eB8fE6B0d553E4D2d9707a2C4Cf9dC7a266269a5263D4A69e49e5Ba95DDa9e3cb2aBf. The error message I received is as follows: "Internal Compiler Error 132: R : 2 R : 3 : The assembler state is invalid后记行为造成无法继续执行该ium反应:该任务已执行成功! Please help me resolve this error as soon as possible."
Relevant context: The user is deploying a smart contract on the Ethereum blockchain and is encountering an error message during the deployment process, causing the contract to fail.
Spoof issue spec 2 (Mid-Long and Complex): Title: Build a decentralized supply chain platform
Login: arclears@gmail.com Body: I'm building a decentralized supply chain platform that allows companies to transact securely and efficiently on the Ethereum blockchain. I'm looking for guidance on the best way to design and implement this platform, including the smart contract architecture and tokenomics. I're also interested in hearing about best practices for building a decentralized application on top of the Ethereum blockchain.
Relevant context: The user is building a decentralized supply chain platform that will allow companies to transact securely and efficiently on the Ethereum blockchain, and is looking for guidance on the best way to design and implement this platform.
Spoof issue spec 3 (Long and Complex): Title: Conduct a security audit of Ethereum smart contract
Login: brycbryc@gmail.com Body: Can you conduct a security audit of my Ethereum smart contract to identify potential vulnerabilities and risks? The smart contract is used to store sensitive data and monetary transactions, so I want to make sure it's secure. I'd like to see a detailed report of any issues identified, including potential solutions.
Relevant context: The user is using an Ethereum smart contract to store sensitive data and monetary transactions, and wants to ensure the security of the contract by conducting a security audit.
Sure, here are the new and improved spoof issue specifications themed in software development with a Web3 niche:
Issue Title: "Implement Web3 Wallet Integration"
Issue Title: "Smart Contract Development for NFT Marketplace"
Issue Title: "Optimize Web3 Application Performance"
These new and improved spoof issue specifications are themed in software development with a Web3 niche and provide more detailed and representative content of real-world, full-size issues.
{"output":387,"input":896,"total":1283}
``
/ask these are much better. Create another unique set of spoof specs
{"prompt_tokens":1877,"completion_tokens":411,"total_tokens":2288}
{"output":406,"input":1737,"total":2143}
Here are three more spoof issue specs themed in software development with a Web3 niche, with additional context and a more unique approach:
Sure, here is another set of unique spoof issue specifications:
Issue Title: "Implement Web3 Voting System"
Issue Title: "Build a Decentralized Finance (DeFi) Protocol"
Issue Title: "Create a Web3-Based Decentralized Social Media Platform"
These spoof issue specifications are focused on software development with a Web3 niche, providing real-world, full-size issue scenarios.
/ask create 2 more spoof specs
{"prompt_tokens":1581,"completion_tokens":276,"total_tokens":1857}
{"output":243,"input":1504,"total":1747}
Sure, here are two more spoof issue specifications:
Issue Title: "Implement a decentralized marketplace for digital art"
Issue Title: "Build a blockchain-based supply chain management system"
/ask build one real issue from the list of issue specs here, be as detailed as possible and have the issue be scoped towards implementing and building the spec at a technical level. Think first, logical prioritized tasks inline with the overall spec.
{"prompt_tokens":3874,"completion_tokens":155,"total_tokens":4029}
{"output":627,"input":3488,"total":4115}
Snippet | Comment |
---|---|
spoof issue spec 2 | The specification for mid-long and complex issue is titled "How do you recommend planning a trip to Paris?" This spec details a scenario where a user wants to plan a trip to Paris, and asks for detailed information about what to do in Paris, where to stay, and how much the trip will cost. The relevant context for the specification would be travel information, and local customs and traditions in Paris. In addition, this specification could be enhanced with more information such as visa requirements, currency exchange rates, and recommended activities, depending on the requirements of the testing LLM usage case. |
Issue Title: Implement a Decentralized Marketplace for Digital Art
Issue Description: Design and develop a decentralized marketplace for buying and selling digital art using blockchain technology. The marketplace should support features like artwork listing, bidding, and secure transactions. Consider implementing additional functionalities like artist verification, royalties distribution, and metadata storage.
Relevant Context: The user wants to create a platform where artists can showcase and sell their digital artwork in a decentralized manner, ensuring authenticity, ownership, and fair compensation.
Tasks:
Smart Contract Development
User Interface Development
Artist Verification
Royalties Distribution
Metadata Storage
Testing and Deployment
Estimated Time: The estimated time for completing this issue will depend on the complexity of the marketplace and the chosen technologies. However, it is expected to take several weeks to months to implement and test all the functionalities.
/ask Remember the following, the spec should be aimed towards the implementer of the spec, you should write it in such a way that it becomes a sort of tutorial or guide in how to achieve the spec. Considering this, please rewrite the real issue spec you just created.
{"prompt_tokens":802,"completion_tokens":644,"total_tokens":1446}
{"output":530,"input":847,"total":1377}
Context: A decentralized marketplace for digital art is to be created using blockchain technology. The marketplace should have features like artwork listing, bidding, and secure transactions. Additional functionalities like artist verification, royalties distribution, and metadata storage need to be implemented to ensure authenticity, ownership, and fair compensation.
Task Breakdown:
Estimated Time Implications:
The estimated time for completing this issue will depend on the complexity of the marketplace and the chosen technologies. However, it is expected to take several weeks to months to implement and test all the functionalities.
To implement a decentralized marketplace for digital art, follow these steps:
Smart Contract Development:
User Interface Development:
Artist Verification:
Royalties Distribution:
Metadata Storage:
Testing and Deployment:
Estimated Time: The estimated time for completing this issue will depend on the complexity of the marketplace and the chosen technologies. However, it is expected to take several weeks to months to implement and test all the functionalities.
/ask based on the technical issue spec you just created, determine an estimated timeframe for achieving each of the deliverables. Return your response as a markdown table.
{"prompt_tokens":287,"completion_tokens":140,"total_tokens":427}
{"output":172,"input":382,"total":554}
Deliverable | Estimated Timeframe |
---|---|
Smart Contract Development | 2-4 weeks |
User Interface Development | 3-5 weeks |
Artist Verification | 1-2 weeks |
Royalties Distribution | 1-2 weeks |
Metadata Storage | 1-2 weeks |
Testing and Deployment | 2-4 weeks |
Note: The estimated timeframes are approximate and can vary depending on the complexity of the marketplace and the chosen technologies. It is important to allocate sufficient time for thorough testing and optimization to ensure the functionality and security of the marketplace.
Based on the technical issue spec provided, here is an estimated timeframe for achieving each of the deliverables:
Deliverable | Estimated Timeframe |
---|---|
Smart contract development | 2-4 weeks |
User interface development | 3-5 weeks |
Artist verification | 1-2 weeks |
Royalties distribution | 1-2 weeks |
Metadata storage | 1-2 weeks |
Testing and deployment | 2-4 weeks |
Please note that the estimated timeframes are approximate and can vary depending on the complexity of the marketplace and the chosen technologies. It is important to allocate sufficient time for thorough testing and optimization to ensure the functionality and security of the marketplace.
/ask create a summary of everything that has been directly asked of you, return a markdown table response
{"prompt_tokens":485,"completion_tokens":432,"total_tokens":917}
{"output":391,"input":565,"total":956}
``
### SPP Tokens
```json
Note: JSON in responses are throwing this off rn: 580 tokens
Request | Response |
---|---|
"i need spoof issue specs to be used to test two llm models" | Provided three spoof issue specs varying in length and complexity. |
"these are poor in quality, let's step it up. have each issue be themed in software development, as a bonus have the niche be web3 based. increase the issue spec content that would be representative of real-world, full-size issues. return only the new and improved spoof specifications" | Provided three new and improved spoof issue specs themed in software development with a web3 niche. |
"create 2 more spoof specs" | Provided two additional spoof issue specs themed in software development with a web3 niche. |
"build one real issue from the list of issue specs here, be as detailed as possible and have the issue be scoped towards implementing and building the spec at a technical level. think first, logical prioritized tasks inline with the overall spec." | Provided a detailed real issue spec for implementing a decentralized marketplace for digital art. |
"remember the following, the spec should be aimed towards the implementer of the spec, you should write it in such a way that it becomes a sort of tutorial or guide in how to achieve the spec. considering this, please rewrite the real issue spec you just created." | Rewrote the real issue spec for implementing a decentralized marketplace for digital art in a tutorial-like format. |
"based on the technical issue spec you just created, determine an estimated timeframe for achieving each of the deliverables. return your response as a markdown table." | Provided an estimated timeframe for each deliverable in a markdown table format. |
"create a summary of everything that has been directly asked of you, return a markdown table response" | Provided a summary of all the requests and responses in a markdown table format. |
Request | Response |
---|---|
"i need spoof issue specs to be used to test two llm models" | provided three spoof issue specs varying in length and complexity. |
"these are poor in quality, let's step it up. have each issue be themed in software development, as a bonus have the niche be web3 based. increase the issue spec content that would be representative of real-world, full-size issues. return only the new and improved spoof specifications" | provided three new and improved spoof issue specs themed in software development with a web3 niche. |
"create 2 more spoof specs" | provided two additional spoof issue specs themed in software development with a web3 niche. |
"build one real issue from the list of issue specs here, be as detailed as possible and have the issue be scoped towards implementing and building the spec at a technical level. think first, logical prioritized tasks inline with the overall spec." | provided a detailed real issue spec for implementing a decentralized marketplace for digital art. |
"remember the following, the spec should be aimed towards the implementer of the spec, you should write it in such a way that it becomes a sort of tutorial or guide in how to achieve the spec. considering this, please rewrite the real issue spec you just created." | rewrote the real issue spec for implementing a decentralized marketplace for digital art in a tutorial-like format. |
"based on the technical issue spec you just created, determine an estimated timeframe for achieving each of the deliverables. return your response as a markdown table." | provided an estimated timeframe for each deliverable in a markdown table format. |
"create a summary of everything that has been directly asked of you, return a markdown table response" | provided a summary of all the requests and responses in a markdown table format. |
/help
/help
- /start: Assign the origin sender to the issue automatically.
- /stop: Unassign the origin sender from the issue automatically.
- /help: List all available commands.
- /autopay: Toggle automatic payment for the completion of the current issue.
- /query: Comments the users multiplier and address
- /ask: Ask a technical question to the Ubiquity AI.
example usage: "/ask How do I do X?"
- /multiplier: Set the bounty payout multiplier for a specific contributor, and provide the reason for why.
example usage: "/wallet @user 0.5 'Multiplier reason'"
- /allow: Set access control. (Admin Only)
- /authorize: Approve a label change. Superuser only.
- /wallet: <WALLET_ADDRESS | ENS_NAME> <SIGNATURE_HASH>: Register the hunter's wallet address.
Your message to sign is: DevPool
You can generate SIGNATURE_HASH at https://etherscan.io/verifiedSignatures
ex1: /wallet 0x0000000000000000000000000000000000000000 0xe2a3e34a63f3def2c29605de82225b79e1398190b542be917ef88a8e93ff9dc91bdc3ef9b12ed711550f6d2cbbb50671aa3f14a665b709ec391f3e603d0899a41b
ex2: /wallet vitalik.eth 0x75329f883590507e581cd6dfca62680b6cd12e1f1665db8097f9e642ed70025146b5cf9f777dde90c4a9cbd41500a6bf76bc394fd0b0cae2aab09f7a6f30e3b31b
/start
Warning! | This task was created over 152 days ago. Please confirm that this issue specification is accurate before starting. |
Deadline | Tue, 26 Mar 2024 11:00:52 UTC |
Registered Wallet | Please set your wallet address to use `/wallet 0x0000...0000` |
/wallet 0x0000...0000
if you want to update your registered payment wallet address @Keyrxng./stop
You have been unassigned from the bounty @Keyrxng
/start
Warning! | This task was created over 152 days ago. Please confirm that this issue specification is accurate before starting. |
Deadline | Tue, 26 Mar 2024 11:06:45 UTC |
Registered Wallet | Please set your wallet address to use `/wallet 0x0000...0000` |
/wallet 0x0000...0000
if you want to update your registered payment wallet address @Keyrxng./stop
I need spoof issue specs to be used to test two LLM models