build(deps): bump actions/checkout from 3 to 5

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,51 @@
+# Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes
+* Focusing on what is best for the community
+
+Examples of unacceptable behavior:
+
+* The use of sexualized language or imagery
+* Trolling, insulting or derogatory comments
+* Personal or political attacks
+* Public or private harassment
+* Publishing others' private information without permission
+
+## Enforcement Responsibilities
+
+Project maintainers are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+[@Tru3B1iss](https://t.me/Tru3B1iss).
+All complaints will be reviewed and investigated promptly and fairly.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org). 

.github/DISCUSSION_TEMPLATE.md

@@ -0,0 +1,61 @@
+# Discussion Guidelines
+
+## Categories
+
+### General
+- General questions about the project
+- Community updates
+- Project announcements
+
+### Q&A
+- Technical questions
+- Implementation help
+- Best practices
+
+### Show and Tell
+- Share your implementations
+- Show off your projects
+- Share success stories
+
+### Ideas
+- Feature suggestions
+- Improvement proposals
+- Future roadmap
+
+## Guidelines
+
+1. **Be Respectful**
+   - Follow our Code of Conduct
+   - Be kind to others
+   - Help when you can
+
+2. **Stay On Topic**
+   - Keep discussions relevant
+   - Use appropriate categories
+   - Don't spam
+
+3. **Provide Context**
+   - Include relevant details
+   - Share code snippets when needed
+   - Explain your questions clearly
+
+4. **Use Markdown**
+   - Format your posts properly
+   - Use code blocks for code
+   - Include links when relevant
+
+## Getting Started
+
+1. Choose the right category
+2. Create a new discussion
+3. Follow the template
+4. Engage with others
+
+## Need Help?
+
+- Check our [Support Policy](.github/SUPPORT.md)
+- Read our [Code of Conduct](.github/CODE_OF_CONDUCT.md)
+- Contact us on:
+  - Telegram: [@Tru3B1iss](https://t.me/Tru3B1iss)
+  - Twitter: [@XTruebliss](https://x.com/XTruebliss)
+  - Discord: [@trueb1iss](https://discord.com/users/1274339638668038187) 

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,38 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: '[BUG] '
+labels: bug
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Environment:**
+ - OS: [e.g. Windows 10]
+ - Solana Version: [e.g. 1.17.0]
+ - Anchor Version: [e.g. 0.28.0]
+ - Node Version: [e.g. 18.17.0]
+
+**Additional context**
+Add any other context about the problem here.
+
+**Contact Information**
+- Telegram: [@Tru3B1iss](https://t.me/Tru3B1iss)
+- Twitter: [@XTruebliss](https://x.com/XTruebliss)
+- Discord: [@trueb1iss](https://discord.com/users/1274339638668038187) 

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,31 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: '[FEATURE] '
+labels: enhancement
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.
+
+**Implementation Details**
+- Technical approach
+- Required dependencies
+- Potential challenges
+- Estimated timeline
+
+**Contact Information**
+- Telegram: [@Tru3B1iss](https://t.me/Tru3B1iss)
+- Twitter: [@XTruebliss](https://x.com/XTruebliss)
+- Discord: [@trueb1iss](https://discord.com/users/1274339638668038187) 

.github/PROJECT_TEMPLATE.md

@@ -0,0 +1,76 @@
+# Pumpfun Development Roadmap
+
+## Project Overview
+Track the development progress of the Pumpfun Smart Contract with Raydium & Meteora DEX Integration.
+
+## Project Structure
+
+### Backlog
+- [ ] Initial project setup
+- [ ] Basic documentation
+- [ ] Development environment setup
+- [ ] Testing framework setup
+
+### In Progress
+- [ ] Core smart contract development
+- [ ] Raydium integration
+- [ ] Meteora integration
+- [ ] Testing implementation
+
+### Review
+- [ ] Code review
+- [ ] Security audit
+- [ ] Performance optimization
+- [ ] Documentation review
+
+### Done
+- [x] Repository setup
+- [x] Community guidelines
+- [x] Security policy
+- [x] Support policy
+
+## Milestones
+
+### Phase 1: Foundation
+- [ ] Project initialization
+- [ ] Basic architecture
+- [ ] Core functionality
+
+### Phase 2: DEX Integration
+- [ ] Raydium integration
+- [ ] Meteora integration
+- [ ] Cross-DEX functionality
+
+### Phase 3: Advanced Features
+- [ ] Virtual pools
+- [ ] Token management
+- [ ] Migration capabilities
+
+### Phase 4: Testing & Security
+- [ ] Unit tests
+- [ ] Integration tests
+- [ ] Security audits
+- [ ] Performance testing
+
+## Sprint Planning
+
+### Current Sprint
+- Priority tasks
+- Bug fixes
+- Feature implementations
+
+### Next Sprint
+- Upcoming features
+- Planned improvements
+- Technical debt
+
+## Resources
+- [Documentation](README.md)
+- [Contributing Guidelines](CONTRIBUTING.md)
+- [Security Policy](.github/SECURITY.md)
+- [Support Policy](.github/SUPPORT.md)
+
+## Contact
+- Telegram: [@Tru3B1iss](https://t.me/Tru3B1iss)
+- Twitter: [@XTruebliss](https://x.com/XTruebliss)
+- Discord: [@trueb1iss](https://discord.com/users/1274339638668038187) 

.github/SECURITY.md

@@ -0,0 +1,42 @@
+# Security Policy
+
+## Supported Versions
+
+| Version | Supported          |
+| ------- | ------------------ |
+| 1.0.x   | :white_check_mark: |
+
+## Reporting a Vulnerability
+
+We take the security of our smart contracts seriously. If you discover a security vulnerability, please follow these steps:
+
+1. **DO NOT** disclose the vulnerability publicly until it has been addressed
+2. Email your findings to [@Tru3B1iss](https://t.me/Tru3B1iss)
+3. Provide detailed information about the vulnerability
+4. Include steps to reproduce the issue
+5. Wait for our response before taking any further action
+
+## Security Best Practices
+
+When using our smart contracts:
+
+1. Always verify contract addresses
+2. Use official deployment methods
+3. Keep your private keys secure
+4. Never share sensitive information
+5. Use hardware wallets for large transactions
+
+## Security Updates
+
+We regularly:
+- Audit our smart contracts
+- Update dependencies
+- Review security best practices
+- Monitor for potential vulnerabilities
+
+## Contact
+
+For security-related issues, contact:
+- Telegram: [@Tru3B1iss](https://t.me/Tru3B1iss)
+- Twitter: [@XTruebliss](https://x.com/XTruebliss)
+- Discord: [@trueb1iss](https://discord.com/users/1274339638668038187) 

.github/SUPPORT.md

@@ -0,0 +1,67 @@
+# Support Policy
+
+## Getting Help
+
+We provide support through multiple channels to ensure you get the help you need.
+
+### Support Channels
+
+1. **Telegram**
+   - Primary support channel: [@Tru3B1iss](https://t.me/Tru3B1iss)
+   - Response time: Within 24 hours
+
+2. **Twitter**
+   - Follow us: [@XTruebliss](https://x.com/XTruebliss)
+   - DM for support
+
+3. **Discord**
+   - Join our server: [@trueb1iss](https://discord.com/users/1274339638668038187)
+   - Use the support channel
+
+### What We Support
+
+- Smart contract deployment
+- DEX integration issues
+- Token management
+- Migration assistance
+- Technical questions
+- Bug reports
+
+### What We Don't Support
+
+- Personal wallet issues
+- Third-party platform problems
+- Investment advice
+- Price predictions
+- Trading strategies
+
+## Issue Reporting
+
+When reporting issues:
+
+1. Use the issue templates
+2. Provide detailed information
+3. Include error messages
+4. Share relevant logs
+5. Describe steps to reproduce
+
+## Documentation
+
+- Check our README.md first
+- Review existing issues
+- Search closed issues
+- Check our documentation
+
+## Community Support
+
+- Join our community channels
+- Help other users
+- Share knowledge
+- Report bugs
+
+## Response Time
+
+- Critical issues: Within 12 hours
+- Regular issues: Within 24 hours
+- Feature requests: Within 48 hours
+- General questions: Within 72 hours