AltLayer Documentation
  • 👋Welcome
    • Overview
  • Restaked Rollups
    • VITAL for Decentralised Verification
      • Tier-1 Finality
      • Tier-2 Finality
      • Tier-3 Finality
    • MACH for Faster Finality
      • Interoperability via MACH
    • SQUAD for Decentralised Sequencing
    • Staking of dApp Token
  • Wizard
    • Introduction
    • Technical overview
    • Create AVS
    • Manage AVS
    • Operator management
    • Hosted operator API (BLS based)
    • Custom AVS specification
      • Constructor specification requirements
      • Import Externally-Deployed AVS
    • Report bug or submit a feature request
  • Autonome
    • Deploy AI Agent
    • Autonome API guide
    • Uploading your own agent framework
    • Twitter/X login troubleshooting guide
  • ♾️AltLayer-Facilitated Actively Validated Services
    • Overview
    • AltLayer MACH AVS
      • Operator Guide
      • User Delegation Guide
    • Cyber MACH AVS for Cyber L2
      • Operator Guide
      • User Delegation Guide
    • DODOchain MACH AVS for DODO Chain
      • Operator Guide
      • User Delegation Guide
    • Fast Finality Layer for Soneium
      • Operator Guide
      • User Delegation Guide
    • Xterio MACH AVS for Xterio Chain
      • Operator Guide
      • User Delegation Guide
  • Upgrade Guide
  • 🥩ALT Restaking
    • Staking Info & Parameters
    • Restake ALT
    • Delegating reALT
    • Check and Claim Staking Rewards
    • Unstake ALT
    • Migration from Xterio (Legacy) ALT Pool to Xterio Restaked ALT Pool
    • Testnet reALT faucet
  • Rollup-as-a-Service
    • What is Rollup-as-a-Service (RaaS)?
    • AltLayer's RaaS Offering
    • RaaS Onboarding Guide
      • Optimism Rollup FAQ
      • Arbitrum Rollup FAQ
    • AltLayer Ecosystem
    • Clients in the Spotlight
    • Pricing Model
  • External Integrations
    • Account Abstraction using Biconomy
    • Enabling permissionless interoperability on AltLayer Rollup with Hyperlane
      • Deplying Hyperlane Warp Routes for ERC20 Token Bridging
      • Running Off-chain Agents
      • Setting up the bridging UI
    • Cross-chain Interoperability using Celer
      • Fungible Token Bridging
      • Non-fungible Token Bridging
      • Generic Message Passing
      • cBridge SDK
  • AltLayer's In-House Rollup Stack in Depth
    • How does AltLayer's in-house rollup stack work?
    • Decentralized Sequencer Set
    • Security via Fraud Proof
  • Rollup Types
    • Flash Layer Rollups
      • Example Use cases
        • NFT Mint Events
        • Games
        • Event Ticketing
    • Persistent Rollups
  • Core Features of AltLayer's In-House Rollup Stack
    • Modular
    • Elastic
    • Multi-VM Support
    • Fraud Proofs
    • Decentralized Sequencers
    • Tiered-Finality
  • FlashLayer Showcase
    • AltLayer's POAP NFTs Collection Mint
      • Performance Test in the Wild
    • Dark Forest Community Round
    • Oh Ottie! NFT Collection Mint
    • Dark Forest Community Round for Jump Crypto's Pit Event
    • Ottie 2048
    • Other demos
      • Fraud Proof Demo
      • Flash Layer Demo
      • Rollup Launchpad Demo
      • FlashGPT Demo
  • Implementation Status
    • Roadmap
    • Development Status
  • Community & Support
    • Community
    • Support
Powered by GitBook
On this page
  • X/Twitter flagging the account as inauthentic
  • AI agent Unable to log in to X/Twitter account
  1. Autonome

Twitter/X login troubleshooting guide

X/Twitter flagging the account as inauthentic

To avoid being flagged as inauthentic on X/Twitter, enabling the "Automated" label on your account can help. Here's how to do it:

  1. Navigate to "More" in the menu.

  2. Select "Your account."

  3. Go to "Account information."

  4. Choose "Automation" and follow the prompts to enable the label.

AI agent Unable to log in to X/Twitter account

If your AI agent is unable to log in to your X/Twitter account, it could be due to several reasons, such as two-factor authentication (2FA) or suspicious login activity. Here’s how to troubleshoot the issue:

  • Disable 2FA. The Eliza framework does not support accounts with 2FA enabled. To turn off 2FA:

    1. Navigate to "More" in the menu.

    2. Go to "Settings and Privacy > Security and account access > Security > Two-factor authentication.

    3. Uncheck all 2FA authentication modes.

  • Check for Suspicious Login Emails: If X/Twitter detects an unusual login attempt, they may send an email requesting a "single-use code" for verification. Since agents launched via Autonome are hosted in the US East region on our cloud provider, X/Twitter might flag this as suspicious, especially if your previous logins were from a different location. As a workaround, you can try the following steps:

    1. Connect to a VPN provider and set your location to a region near US East.

    2. Log in to your X/Twitter account using your browser.

    3. Check your email for the suspicious login notification containing the "single-use code."

    4. Enter the "single-use code" to complete the login process successfully.

    5. Re-launch or restart the agent to ensure it functions properly.

    This approach can help resolve login issues caused by location-based security measures.

PreviousUploading your own agent frameworkNextOverview

Last updated 2 months ago