Add security: CODEOWNERS and contributing guidelines

.github/CODEOWNERS

@@ -0,0 +1,8 @@
+# These owners will be the default owners for everything in the repo
+* @jagnd1
+
+# Specific file protections
+*.py @jagnd1
+*.js @jagnd1
+*.ts @jagnd1
+*.sol @jagnd1

.gitignore

@@ -67,4 +67,18 @@ Thumbs.db
 
 # Temporary files
 *.tmp
-*.temp
+*.temp
+
+# Node
+node_modules/
+npm-debug.log
+yarn-error.log
+
+# Environment
+.env.local
+*.key
+*.pem
+
+# Crypto sensitive
+private_keys/
+wallets/

CONTRIBUTING.md

@@ -0,0 +1,52 @@
+# Contributing to FM Crypto Service
+
+Thank you for your interest in contributing to this project!
+
+## How to Contribute
+
+### Reporting Issues
+
+If you find a bug or have a suggestion:
+1. Check if the issue already exists
+2. Open a new issue with a clear description
+3. Include steps to reproduce (for bugs)
+
+### Submitting Changes
+
+1. Fork the repository
+2. Create a new branch (`git checkout -b feature/your-feature-name`)
+3. Make your changes
+4. Test thoroughly
+5. Commit with clear messages
+6. Push to your fork
+7. Submit a Pull Request
+
+## Pull Request Guidelines
+
+- Describe what your PR does and why
+- Reference any related issues
+- Ensure code follows existing style
+- Update documentation if needed
+- Keep changes focused and atomic
+
+## Code Standards
+
+- Python code should follow PEP 8
+- JavaScript/TypeScript should follow ESLint rules
+- Add comments for complex logic
+- Update README.md for new features
+- Maintain compatibility with existing dependencies
+
+## Security
+
+- Never commit private keys or sensitive data
+- Follow secure coding practices for crypto operations
+- Report security vulnerabilities privately
+
+## License
+
+By contributing, you agree that your contributions will be licensed under the same license as this project.
+
+## Questions?
+
+Open an issue for discussion before starting major changes.